Hello all
A milestone, a usage message for sed!
-- Pieter
From 281667bb736e7196342039513252f7b0587a52ad Mon Sep 17 00:00:00 2001
From: Pieter Kockx
Date: Wed, 25 Oct 2017 09:55:50 +0200
Subject: [PATCH] sed: Add usage
---
sed.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
Here's a second patch that makes the surrounding comments more in line with
the code, in my opinion.
On Wed, 25 Oct 2017 at 09:38 Pieter Kockx wrote:
> Hello everyone
>
> sed 's/[[x=]//'
>
> 's/[[x=]//' was parsed as 's/[[=x]//' which (correctl
after encountering an opening bracket
while inside the bracket expression.
-- Pieter
From 45102a167a8b3a101072f8ec62927158ccaa7027 Mon Sep 17 00:00:00 2001
From: Pieter Kockx
Date: Sun, 22 Oct 2017 02:09:46 +0200
Subject: [PATCH] sed: Fix parsing bug in find_delim
's/[[x=]//' was pa
Surprisingly, the GNU coreutils don't include which, but Busybox does
(under the heading 'debianutils').
If we remove it, I'd add an FAQ referring to 'command -v' though.
On Thu, 12 Oct 2017 at 18:07 Alex Pilon wrote:
> > > On 2017-10-10-17, Evan Gates wrote:
> > >> I dislike that which(1) is
ch essentially tries to mimic a typical shell
Also included is a patch to correct some whitespacing in the same file
(spaces where tabs should have been used).
-- Pieter
On Wed, 11 Oct 2017 at 05:06 Michael Forney wrote:
> On 10/10/17, Pieter Kockx wrote:
> > Hello hackers
> >
>
Hello hackers
$ which /usr/bin/env
/usr/bin//usr/bin/env
which should probably be idempotent when applied to its own output as
in which $(which $(which env)).
The underlying reason is that fstatat ignores dirfd if the the given
filename is an absolute path.
The following fix is possible:
if ((d
tions in between are false
j = m + 1; // (2) j == 3
// (5) j == len+1
goto nextbrack;
}
literal:
// not reached
Changing j == len to j >= len feels like sweeping the bug under the carpet.
Thoughts?
-- Pieter
From 99d23a812164d17b9d8062ff5eac9eae04cbe950 Mon Sep 17 00
>
From 9d7d618026353910e2629edee6913688c6b89b37 Mon Sep 17 00:00:00 2001
From: Pieter Kockx
Date: Thu, 7 Sep 2017 19:00:10 +0200
Subject: [PATCH] Fix segmentation fault in paste(1)
libutil/unescape received a pointer to a a string in
read-only memory.
---
paste.c | 2 +-
1 file changed, 1
Hello hackers
Get a segfault by typing:
paste blabla
It seems wise to scrutinize other calls to unescape() as well.
-- Pieter
From 45c61280dc1ef9e5692e2b570f6e191bfe4c9906 Mon Sep 17 00:00:00 2001
From: Pieter Kockx
Date: Thu, 7 Sep 2017 19:00:10 +0200
Subject: [PATCH] Fix segmentation fault
From 9aab281ce8c4060fb207abe409ef952631cbd40d Mon Sep 17 00:00:00 2001
From: Pieter Kockx
Date: Tue, 2 May 2017 21:41:14 +0200
Subject: [PATCH] Add usage message
---
sed.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/sed.c b/sed.c
index 6cfd121..f6d5f0b 100644
10 matches
Mail list logo
