Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I used to do it, but I think it's addressing the wrong issue. The problem is, questions and notes don't have to have unique names.

Imagine, if you will, that the same thing applied to domain names. I could set up perlmonks.org on firewheel or snafu. vroom could set it up on yoda, buddha, or yeti. All three, if he wants. Assuming reasonable competence on the part of NSI (gets you in trouble), maybe typing that in your browser will bring up lots of different possibilities.

In the same way, writeups and notes have one unique characteristic -- the IP address of Everything, node_id. As we can link to any specific node with the special [id://\d+] syntax, it's not as touchy an issue as it seems.

Adding more distinguishing information to searches is a good idea, though, and solves the other strong possible objection -- differentiating between posts by different authors. However, if I post twice to the same discussion with a namespaced title, or if I reply to a question in March and a question in August and both had the same title, the efficacy of the name-adding has actually decreased.

I will guarantee you, though, as the person who's written the most about the Everything Engine, if there are ever two different nodes with the same node_id, you will have bigger worries than search results.


In reply to Re: Automatically add name to replies by chromatic
in thread Automatically add name to replies by arturo

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 having a coffee break in the Monastery: (4)
As of 2024-04-12 22:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found