My impression is that you guys like the subject line to stay the same because you don't have a good way to display threading in your search results.
Yes, we could change every place that lists nodes (doom's writeups, super search, newest nodes, best nodes, worst nodes, etc.) to separately list: the title of the node, the depth of the node, the title of the parent to the node, and the title of the root of the thread so that 99.8% of nodes end up being displayed like:
(Re^4)Re^4: assosiating .pl files with perl on linux (re Re^3: assosiating .pl files with perl on linux in assosiating .pl files with perl on linux)
But I don't see how that would be "a good way to display threading". If only there were some better way to represent "the summary of the subject of this node and the context" that would combine that information into one compact string, like just "Re^4: associating .pl files with perl on linux" or, in the case of a significant subject change, something like "Re^2: subject line changing (was Re^4: blandness is the problem, not plagarism)". That would be ideal.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.