On Jan 6, 2006, at 1:22 PM, Rogue Marechal wrote:
Hi - I would definitely be interested in such a tool and more than
happy
to test.
To the occasional contributor (that would be me) the CLI is just
fine but there is that feeling of dabbling in unfamiliar territories,
permanently.
I rarely us
Chris Zubrzycki wrote:
I would love to see a vim setting file for .info, but I have no idea
how to make one.
I have made a nedit syntax highlighting file for .info files[1] It
selects the primary things that I personally found the most hard to keep
track of when looking at a non-highlighted
On Fri, 06 Jan 2006 13:48:01 -0500, Chris Zubrzycki wrote:
>> To the occasional contributor (that would be me) the CLI is just
>> fine but there is that feeling of dabbling in unfamiliar territories,
>> permanently.
> I would love to see a vim setting file for .info, but I have no idea
> how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 6, 2006, at 1:22 PM, Rogue Marechal wrote:
On Mon, 14 Nov 2005 21:12:08 -0500, Koen van der Drift wrote:
I am thinking about writing a simple Cocoa app to help with writing
info and patch files. Basically, it would be a texteditor with
opti
On Mon, 14 Nov 2005 21:12:08 -0500, Koen van der Drift wrote:
> I am thinking about writing a simple Cocoa app to help with writing
> info and patch files. Basically, it would be a texteditor with
> options for validation and cvs commits and even more. Very simple,
> but I think it might be
On Thu, 05 Jan 2006 10:40:09 -0800, Brendan Cully wrote:
>> * extract the original tarball
>> * (apply any prerequisite patches; doesn't sound like this applies)
>> * copy the tree to something.orig
>> * apply your patch
>> * do a quick sanity-check on the altered file (
>> * run 'diff -Naur' (or
