GNU bug report logs - #77944
31.0.50; M-x man on macOS fails with error

Previous Next

Full log

Message #11 received at 77944 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Gerd Möllmann <gerd.moellmann <at> gmail.com>,
 77944 <at> debbugs.gnu.org
Subject: Re: bug#77944: 31.0.50; M-x man on macOS fails with error
Date: Mon, 21 Apr 2025 17:18:47 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

Hi Gerd,

>> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
>> Date: Sun, 20 Apr 2025 18:27:44 +0200
>> 
>> To reproduce with emacs -Q
>> 
>> M-x man RET ls RET
>> 
>> The man buffer shows
>> 
>> sed: 1: "/^[\o001-\o032][\o001-\ ...": RE error: invalid character range
>
> Micheal, that's your addition.  Are these octal escapes not portable
> enough?

Don't know. It was "-e '/^[\001-\032][\001-\032]*$/d'" before. I've
changed it due to problems with remote man pages, see the comment above.

This is macOS, isn't it? What does the following shell command show?

--8<---------------cut here---------------start------------->8---
# sed -e '/^[\o001-\o032][\o001-\o032]*$/d' /dev/null
--8<---------------cut here---------------end--------------->8---

If it fails, does the following work?

--8<---------------cut here---------------start------------->8---
# sed -e '/^[\001-\032][\001-\032]*$/d' /dev/null
--8<---------------cut here---------------end--------------->8---

Does 'sed --version' return something useful? Do you know which sed
version it is, otherwise?

Best regards, Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.