comment on

I'd rather see them by (reverse) date, or better yet by threading

Ooh, good ideas. Although I imagine threading would be more difficult since this is coming out of a relational database..

And I'd rather see that as an option when searching for nodes by an author...

Fine by me, although I suspect it'll be the same engine behind it.

I'd like to not have all the perlman pages show up so often
As a configurable option. Sometimes that's just what you're looking for.

I meant that as a comment that they show up inexplicably. I had many man pages show up when I looked for running with scissors. Neither "running" nor "scissors" were there. (And I imagine that "with" is in a lot more posts that I got as returns.)

Of course, not all posts have a reputation (like perlman)--where would these fit into the rep sort?

If they are showing up as a result for good reason (see above), then I'd say they should be ranked first. The Perl man pages are great, as long as they have some relevance to what you seek.

In reply to RE: (kudra: features are fine as long as they aren't just matching one need) RE: Revisiting Super Search by swiftone
in thread Revisiting Super Search by swiftone

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.


No such thing as a small change
	PerlMonks