Tag Parser Save My Fingers!

I'm going a bit like Kevin Spacey in Seven - ends of fingers wearing a bit thin. One simple way to add a few hours to the effective life of my prints wd be if the Perlmonks tag parser would translate "<>" as "<code>" and "</>" as "</code>". Since it filters out "<" and ">" anyway, this is no loss, and it'd be pretty rare for someone to put in a "<>" meaning for it to be taken literally. Any takers?

§ George Sherston

Edit by tye

Comment on Tag Parser Save My Fingers! Select or Download Code

Replies are listed 'Best First'.
(jeffa) Re: Tag Parser Save My Fingers! by jeffa (Bishop) on May 01, 2002 at 14:12 UTC
I vote no. Why not create your own tag parser and upload script? Here are some possible requirements to help you get started: Read a text file and convert your special tags grab login info from the command line with Term::Readkey (for security on your own box - see Bulk Node Title Editor for more) or use HTTP::Cookies to grab the info from your cookie file Use LWP and HTTP::Request::Common to post Just be sure to do a LOT of testing first! If this sounds a bit scary (and it should), then simply write a Perl script that replaces the tags for you and paste the output of it into the post text area by 'hand'. jeffa We are programmers, not just merely users! >:)	[reply]
Re: Tag Parser Save My Fingers! by brianarn (Chaplain) on May 01, 2002 at 20:31 UTC
I vote no on this one - maybe have it accept <c> and </c> as alternate shortcuts, but having <> mean <code> and whatever the tag would be, either <> or </>, for this main reason. I've seen snips of code that look like this - having someone post code snips like these without wrapping proper code tags around it would have these snips show up incredibly funky. `print "How can I serve you, oh master? "; my $input = <>; while (<>) { # Stuff here }` [download] See what I mean? Bad stuff there, as it'd turn the rest of the post into a giant code tag. ~Brian	[reply] [d/l]
Re: Tag Parser Save My Fingers! by George_Sherston (Vicar) on May 01, 2002 at 11:49 UTC
I hasten to add that this was quite a dim moment at which to press the submit button instead of the preview button, particularly given the subject matter. Of course, what I meant to say was One simple way to add a few hours to the effective life of my prints wd be if the Perlmonks tag parser would translate "<>" as "<code>" and "</> as "</code>". § George Sherston	[reply]
Re: Tag Parser Save My Fingers! by belg4mit (Prior) on May 01, 2002 at 18:44 UTC
Still no closing tag in you're response/second post. The text is the same as the parent. In any event I would say nay, what about waka waka (for readline)? As it is the "parser" doesn't understand embdedded code tags. you cannot write: `<code><code></code></code>` and have it print `<code></code>`, instead it comes out as `<code>`</code>. `-- perl -pew "s/\b;([mnst])/'$1/g"`	[reply] [d/l]