Ah, a very simple and clever "why didn't I think of that?" solution, thanks. If I were to go that route I'd probably use nano as it's more straightforward if you just do simple editing. It won't quite work for me though as I don't want the editor to take up the whole screen so user can compare/copy/paste other printed text above it (I'm not just writing an editor, but using it as a component of a specialized tool.) I could use vim/split screen, though this gets clumsy (back to vim modes/commands complexity, manually have to remember the filename to open in :split, yada yada) and I want the user to be able to simply answer a "do you want..." and immediately have the display I want. Anyway, not the UX I'm looking for.
Good simple suggestion though without knowing all the details of my needs.
And even academically, I would like to know the answer to the op using core perl.
-
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.
|