Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

[ Note that I am replying to this node after so long a delay because I had hoped that no reply would be necessary but recently received a request that I felt was best replied to here. ]

First, let me repeat that • was not a motivating factor behind this change. The main connection between this change and • was that • delayed this change. In the end, I decided to make this change despite it disabling • because I felt that • was considered obnoxious by many, including you.

I don't see any pallatable technical way to outlaw personalized reply indicators. I see a policy-only ban as being doomed to failure after a lot of time spent by editors and/or complaining and finger pointing. And I don't see a consensus supporting such a ban.

"Vanity tags" is a cute term for it, but (just to be clear) I don't include "(tye)" in the titles of my replies out of vanity. If that were the reason, then this thread would have started at "(tye) More HTML escaping". I've seen that a few people have stopped similar practices now that author information is reported in Search Results.

But making the author easier to determine was never even a big part of my motivation. I just find duplicate node titles to be a pain. And the easiest way for me to ensure that my replies have a unique title is to usually include "(tye)" because that is a short, simple string that I can be pretty sure will not be used in other node titles. Then I can just keep track of how many times I reply in a thread (w/o modifying the title for other reasons) and include a sequence number in replies other than the first one.

There are lots of cases where duplicate titles cause me problems. Recently I went back and added "(tye)" to (tye)Re: A question of style because I often refer to that node when questions about what difference & and () make when calling Perl subroutines. Depending on how I'm surfing, looking up the node ID for that item can be pretty easy or nearly impossible. But now I can link to it easily without having to memorize a node ID (I have a hard time remembering the node ID of tye and I actually end up using that quite a bit).

Now, I have other ideas of how to make node titles unique more often. For example, I kinda like the idea of prefixing reply titles with "Re2.1.3: " to indicate that this is the 3rd reply to the 1st reply to the 2nd reply to the root of this thread. It is a bit shorter than the current "Re: Re: Re: ". Or even "Re213: " with the "." only used around multi-digit parts. But I strongly suspect that such a change would be deemed "ulgy" by a great many of our members. After all, I've heard other proposals that I find pretty ugly. (: And even if we implemented a unique reply indicator, I'd probably still end up using "(tye)Re: " on at least some of my replies because I wouldn't want to have to remember whether my node was Re4: A question of style or Re6: A question of style.

Some related thoughts (and ones that I've mostly just repeated or refined above) can be found in (tye)Re: Dingbats in node titles: What's your opinion.

I'm not sure why you've continued this "protest" as long as you have. I haven't seen anyone express any support for your idea of banning all personalized reply indicators. Sure, I've seen people support the idea of banning "dingbat characters" in node titles and I've seen people express a dislike for "(tye)" in node titles. But noone saying we should try to ban them. Perhaps you have received support in private?

I would think that such a strong lack of public displays of support for your proposal would lead you to abandon your protest aimed at getting such a ban imposed. I think Macphisto was accurate in calling this "tilting at windmills". I don't foresee such a ban ever happening (because I don't see any practical way to implement it, even if there were support for it) and so I don't feel bad about having forced you to change your method of (futile) protest. Feel free to switch to · or stay with • if you wish to continue your protest.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: More HTML escaping by tye
in thread More HTML escaping by tye

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (6)
As of 2024-03-28 08:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found