You just have to tell your browser to open the particular content type (text/plain with gvim, or a g?vim? in a terminal emulator egxterm -e vim. Opera will all you to do all manner of silly things with content types it doesn't know internally, such as passing the uri/downloaded version/filenames to another program etc...
I'm pretty sure the only thing you could do at PM's side to help this is by allowing the user to select the Content-Type header sent with code downloads, allowing the user to specify a header of text/x-vim, or perhaps a type perlish, so windows users get it going to their perl editor instead of their regular text editor (which most likely defaults to notepad)
@_=qw; ask f00li5h to appear and remain for a moment of pretend better than a lifetime;;s;;@_[map hex,split'',B204316D8C2A4516DE];;y/05/os/&print;
-
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.
|