I use EditPad Classic, which so far I find has the right balance of features to complexity. The whole jgsoft stable might be a source of good ideas if you haven't seen it already. It looks as though you are going to implement some perl-specific features which I didn't know I needed, however, and it makes me think there are a few things that wd be useful. A template, for example, that popped up a blank file with a shebang line, use strict; and whatever else I found I always wanted. And wd it be possible to have a "Save as CHMOD 755" option? And making the tab button insert 4 spaces, rather than a tab, wd be nice... and indeed auto-indenting by n+4 any line following a "{" - where n is the indent of the preceding line... and indeed preserving the indenting from line to line. And how about building the logic of strict into it, so before I save I click on the "check strict" button and it goes through all the violations, highlighting each one for me to edit it?
Well, I applaud your enterprise and generosity, and I'll be very interested to see the result when it's done. § George Sherston
-
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.
|