On Sun, Jul 17, 2011 at 03:25:29PM +, Thordur Bjornsson wrote:
> >
> > The commit comment indicates to me that the underlying mechanism
> > changed significantly, so now I wonder if the information that
> > once was in vnode_if.src (regarding vnode locking disciplines) is
> > irrelevant, obsol
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 fairly easy to convert one to the
Prodded by krw, here's an update to the latest Lynx release. It's quite a big
patch (the configure script regen, mainly):
http://www.recoil.org/~avsm/openbsd-lynx2-8-7.rel2-1.diff
Most of our local patches have been merged upstream, so the kept ones are:
- restore local lynx.cfg settings [avsm]
-
On Sun, Jul 17, 2011 at 04:48:59PM -0400, Ted Unangst wrote:
> 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 (currentl
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 fairly easy to convert one to the other however.
\< and \> are regex extensions for
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 waiti
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 fairly easy to convert one to the other however.
If we actually want this, should it go into grep or into the general
regex
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.
On 18 July 2011 04:28, Jason McIntyre wrote:
> can i ask why you want to support this? it is a gnu grep thing or
> something?
It isn't. I looked on AIX, Tru64, SCO and Solaris. The OS-provided vi
supported this syntax on all four systems, and on Solaris, /usr/bin/grep
supported it as well. The
On Sun, Jul 17, 2011 at 03:19:21PM -0400, Ted Unangst wrote:
> It is supported (and documented) by GNU grep. I'm not proposing
> documenting it per se, it's simply something that will work if you use
> it, but the documented regex format remains the supported way.
>
> There is at least one port (
I recently made a few changes to vnd(4) to make it stricter by better
emulating physical disks and their requirements (e.g., raw disk I/O
must be done with whole sectors). However, it turns out that a lot of
the release scripts depended on the more lenient behavior vnd(4) used
to exhibit.
It's to
On Sun, Jul 17, 2011 at 03:19:21PM -0400, Ted Unangst wrote:
> On Sun, Jul 17, 2011, Jason McIntyre 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 difficu
On Sun, Jul 17, 2011, Jason McIntyre 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 fairly easy to convert one to the o
On Sun, Jul 17, 2011 at 07:28:11PM +0100, Jason McIntyre 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 fairly easy
On Sun, Jul 17, 2011 at 09:12:29AM -0400, Ted Unangst wrote:
> On Sun, Jul 17, 2011, Alexander Schrijver wrote:
> >> nope, only ssize_t is guaranteed.
> >
> > This is the only way i could think off.
>
> I don't think you will ever be able to get a string longer than
> SSIZE_MAX into memory, but
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 fairly easy to convert one to the other however.
>
if you do this, we will need to
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.
Index: grep.c
===
RCS file: /home/ted
On Sun, Jul 17, 2011 at 04:25:59PM +0200, Benny Lofgren wrote:
> While reading up on vnodes I found a couple of glitches in the
> vnode(9) man page (diff below). It refers in one place to the
> file sys/kern/vnode_if.src which was deleted by this commit:
Good catch. I thought I had nuked that;
>
While reading up on vnodes I found a couple of glitches in the
vnode(9) man page (diff below). It refers in one place to the
file sys/kern/vnode_if.src which was deleted by this commit:
8<8<8<8<8< (cut)
From: Thordur I Bjornsson
Subject: [source-changes] CV
On Sun, Jul 17, 2011, Alexander Schrijver wrote:
>> nope, only ssize_t is guaranteed.
>
> This is the only way i could think off.
I don't think you will ever be able to get a string longer than
SSIZE_MAX into memory, but that looks good.
>
> Index: util.c
>
> nope, only ssize_t is guaranteed.
This is the only way i could think off.
Index: util.c
===
RCS file: /home/alex/scm/cvsync/src/usr.bin/grep/util.c,v
retrieving revision 1.41
diff -u -r1.41 util.c
--- util.c 11 Jul 2011 20:43
On Sun, Jul 17, 2011 at 12:15:50PM +0200, Alexander Schrijver wrote:
> On Sun, Jul 17, 2011 at 11:32:27AM +0200, Otto Moerbeek wrote:
> > On Sun, Jul 17, 2011 at 11:20:28AM +0200, Alexander Schrijver wrote:
> >
> > > This fixes an integer overflow with very long lines.
> > >
> > > OK?
> >
> > H
On Sun, Jul 17, 2011 at 11:32:27AM +0200, Otto Moerbeek wrote:
> On Sun, Jul 17, 2011 at 11:20:28AM +0200, Alexander Schrijver wrote:
>
> > This fixes an integer overflow with very long lines.
> >
> > OK?
>
> Hmm, changing from a signed to an unsigned type might lead to
> surprises. I think rego
On Sun, Jul 17, 2011 at 11:20:28AM +0200, Alexander Schrijver wrote:
> This fixes an integer overflow with very long lines.
>
> OK?
Hmm, changing from a signed to an unsigned type might lead to
surprises. I think regoff_t is better.
-Otto
>
> Index: util.c
> =
Fix spacing.
OK?
Index: mmfile.c
===
RCS file: /home/alex/scm/cvsync/src/usr.bin/grep/mmfile.c,v
retrieving revision 1.13
diff -u -r1.13 mmfile.c
--- mmfile.c2 Jul 2010 20:48:48 - 1.13
+++ mmfile.c16 Jul 2011 22:14:
This fixes an integer overflow with very long lines.
OK?
Index: util.c
===
RCS file: /home/alex/scm/cvsync/src/usr.bin/grep/util.c,v
retrieving revision 1.41
diff -u -r1.41 util.c
--- util.c 11 Jul 2011 20:43:21 - 1.41
26 matches
Mail list logo
