GNU bug report logs -
#77944
31.0.50; M-x man on macOS fails with error
Previous Next
Reported by: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Date: Sun, 20 Apr 2025 16:29:02 UTC
Severity: normal
Found in version 31.0.50
Fixed in version 31.1
Done: Michael Albinus <michael.albinus <at> gmx.de>
Bug is archived. No further changes may be made.
Full log
Message #14 received at 77944 <at> debbugs.gnu.org (full text, mbox):
Michael Albinus <michael.albinus <at> gmx.de> writes:
Frohe Ostern!
> This is macOS, isn't it? What does the following shell command show?
Right, it's macOS.
>
> # sed -e '/^[\o001-\o032][\o001-\o032]*$/d' /dev/null
>
$ /usr/bin/sed -e '/^[\o001-\o032][\o001-\o032]*$/d' /dev/null
sed: 1: "/^[\o001-\o032][\o001-\ ...": RE error: invalid character rangeThat gives
(I've installed the GNU sed package "gsed" for now, as a workaround.
That's why I invoke /usr/bin/sed.
> If it fails, does the following work?
>
> # sed -e '/^[\001-\032][\001-\032]*$/d' /dev/null
/usr/bin/sed -e '/^[\001-\032][\001-\032]*$/d' /dev/null
sed: 1: "/^[\001-\032][\001-\032 ...": RE error: invalid character range
>
> Does 'sed --version' return something useful? Do you know which sed
> version it is, otherwise?
It doesn't have a --version. The man page says
AUTHORS
Diomidis D. Spinellis <dds <at> FreeBSD.org>
so I guess it's the FreeBSD one.
This bug report was last modified 21 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.