I think this is dooable, useful even, but only through URL mangling (like lastnode_id=, well we can have lastsopwquery=ho%20ha, which would be the querystr before you left teh SOPW superdoc to view a SOPW post), which might not be soo good.

I no have time at the moment to even think about implementing this sadly (well I do,

my $sopw = CGI::Util::escape($ENV{QUERY_STRING});
$query->url(-relative =>1).'?node_id='.$nodeid.';'.$sopw
[download]

as soon as you start viewing SOPW using the "next" links). Well you get the picture (since the order the node appears in SOPW the superdoc is all relative, even this info will only be good for a short time ~at least a day~ which is good enough).

 

______crazyinsomniac_____________________________ Of all the things I've lost, I miss my mind the most. perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.