On Mon, May 9, 2011 at 8:25 AM, Rogan Creswick wrote:
> Indeed :) The tag syntax is controlled by two command-line flags:
> --prefix=... and --suffix=...
>
> It can be difficult to get the desired strings past both the shell and
> the regular expression compiler (although that last bit is changin
On Sun, May 8, 2011 at 10:38 PM, wrote:
>
> This is a useful tool !
I'm glad you think so too!
> I would like to suggest allowing customization of the syntax to indicate a
> tag, e.g. {# #} instead of <<< >>> (You just knew someone was going to say
> that, right ? :-)
Indeed :) The tag synt
2011/5/9 :
> On Sun, 8 May 2011 16:23:59 -0700
> Rogan Creswick wrote:
>
>> Newt scans the input (either a file, directory or stdin) for tags
>> marked with "<<>>" [1], then replaces those entries with
>> values specified on the command line, producing either a new file,
>> modifying the input te
On Sun, 8 May 2011 16:23:59 -0700
Rogan Creswick wrote:
> Newt scans the input (either a file, directory or stdin) for tags
> marked with "<<>>" [1], then replaces those entries with
> values specified on the command line, producing either a new file,
> modifying the input template in place (--in
I'm happy to announce Newt: a trivial tool for creating boilerplate.
I frequently need to create projects with slight customizations -- I
have a particular layout for cabal projects, and make files for LaTeX
papers, etc... However, there are often fields that need to be
updated in many places. (
