Tante Grazie, Flavio!

You should consider polishing it a little and putting it at the tutorials.

• For example, using $ENV{HOME} instead of your home name ;) .
• Or naming the template with a .tpl extension (4 example) .

It is a good starting point for most 'well intentioned' perl programers. I am never sure of what is the standard way of presenting a finished script.

I will, also, copy your template at my .SciTE macros. I find it easier to fill-in data than to start a new script from cero.

After installing it as you said, I added this lazy way of using it at LINUX...

>SNAME=$(/usr/bin/Xdialog --stdout --title "(Path/)New Script's Name..
+." --inputbox "/full/script/path/newscript.pl" 0 0 "$HOME/program/scr
+ipts/newSname.pl");/usr/bin/perl $HOME/program/script/script-starter.
+pl $SNAME ; /usr/bin/scite $SNAME
[download]

This bash one-liner, asks the full new script's name with an Xdialog window. Then, it calls your template-copier and finally, it opens the new script with SCITE. Some day, it could become something better, but by now, it does just what I need.

Thanks, again!

alberto

---

---

• 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.