2011/7/18 Ted Unangst t...@tedunangst.com:
On Mon, Jul 18, 2011, Alexander Bluhm wrote:
On Sun, Jul 17, 2011 at 11:43:03AM -0400, Ted Unangst wrote:
I recently learned that our grep does not support the \\ syntax for
word boundaries, only the somewhat more difficult to use [[::]] format.
It's
If we start adding this to some tools, it would start to make sense to
support it at the source.
Namely, conversion functions are a bit annoying, and it's always possible
to fuck it up. Plus, same code twice = same bugs.
Is there anything preventing us from adding non-standard flags to
On Mon, Jul 18, 2011, Marc Espie wrote:
If we start adding this to some tools, it would start to make sense to
support it at the source.
Namely, conversion functions are a bit annoying, and it's always possible
to fuck it up. Plus, same code twice = same bugs.
Is there anything preventing
please don't even think of adding something without documenting it. :(
really, don't do that. lacking documentation can really mess one up.
but i'm fine with the idea of actually adding this syntax support.
2011/7/17 Ted Unangst t...@tedunangst.com
On Sun, Jul 17, 2011, Jason McIntyre wrote:
On Sun, Jul 17, 2011 at 09:50:05PM +0200, Matthias Kilian wrote:
Then those ports should be fixed. There seem to be more GNUisms in
(recent?) GNU grep that are picked up by projects, for example the
use of \s and \S in pxltoraster
Oops, that was GNU sed, not grep.
Ted Unangst t...@tedunangst.com wrote:
I recently learned that our grep does not support the \\ syntax for
word boundaries, only the somewhat more difficult to use [[::]] format.
It's fairly easy to convert one to the other however.
If we actually want this, should it go into grep or into the
On Sun, Jul 17, 2011, Matthias Kilian wrote:
Then those ports should be fixed. There seem to be more GNUisms in
(recent?) GNU grep that are picked up by projects, for example the
use of \s and \S in pxltoraster (currently a disabled part of
ghostscript, for which I've got a diff and waiting
