From: Ted Phelps <phelps@gnusto.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
Cc: michael.albinus@gmx.de, 75308@debbugs.gnu.org
Subject: bug#75308: 30.0.93; man.el assume shell is bash
Date: Sat, 4 Jan 2025 18:12:02 +1100 [thread overview]
Message-ID: <12d19908-d1ee-4a7c-8853-119c1f3909dc@gnusto.com> (raw)
In-Reply-To: <86o70ogluk.fsf@gnu.org>
On 3/1/25 22:47, Eli Zaretskii wrote:
>> From: Stefan Kangas <stefankangas@gmail.com>
>> Date: Fri, 3 Jan 2025 03:26:42 -0600
>> Cc: phelps@gnusto.com, 75308@debbugs.gnu.org, michael.albinus@gmx.de
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> Cc: Michael Albinus <michael.albinus@gmx.de>
>>>> From: Stefan Kangas <stefankangas@gmail.com>
>>>> Date: Fri, 3 Jan 2025 02:46:28 -0600
>>>>
>>>> Ted Phelps <phelps@gnusto.com> writes:
>>>>
>>>>> Steps to reproduce:
>>>>> * env SHELL=/bin/tcsh emacs -Q
>>>>> * invoke M-x man
>>>>> * request a man page (e.g. emacs)
>>>>>
>>>>> This will produce output like the following instead of the man page:
>>>>>
>>>>> Unmatched '''.
>>>>> BEGIN: Command not found.
>>>>> anonblank=0: Command not found.
>>>>> }: Command not found.
>>>>> Illegal variable name.
>>>>> {: Command not found.
>>>>> }: Command not found.
>>>>> Illegal variable name.
>>>>> Badly placed ()'s.
>>>>> Unmatched '''.
>>>>>
>>>>> process exited abnormally with code 1
>>>>>
>>>>> Replacing /bin/tcsh with /bin/bash in the above command produces the
>>>>> expected man page.
>>>>>
>>>>> It looks like the behavior was broken by the following commit:
>>>>>
>>>>> commit 861ac933dd8aed1028edc4b9142400e3702874d5
>>>>> Author: Michael Albinus <michael.albinus@gmx.de>
>>>>> Date: Wed Nov 1 16:54:31 2023 +0100
>>>>>
>>>>> Many thanks,
>>>>> -Ted
>>>>
>>>> Thanks for the bug report. For emacs-30, we should look into a some
>>>> small workaround. I'm copying in Michae.
>>>
>>> I think we should force SHELL to be 'sh' (except on Windows) before
>>> calling shell-command etc.
>>
>> I was first thinking /bin/bash but if we don't expect to need it, then
>> sh is better.
>
> If we do need Bash and not just Bourne-compatible shell, we have a
> serious bug there. I hope that is not the case.
I don't think there's anything bash-specific required, just the ability
to redirect stdout and stderr independently. I've confirmed that
Debian's /bin/sh (dash) works just fine.
-Ted
next prev parent reply other threads:[~2025-01-04 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 23:39 bug#75308: 30.0.93; man.el assume shell is bash Ted Phelps
2025-01-03 8:46 ` Stefan Kangas
2025-01-03 8:50 ` Eli Zaretskii
2025-01-03 9:26 ` Stefan Kangas
2025-01-03 11:47 ` Eli Zaretskii
2025-01-04 7:12 ` Ted Phelps [this message]
2025-01-04 7:58 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12d19908-d1ee-4a7c-8853-119c1f3909dc@gnusto.com \
--to=phelps@gnusto.com \
--cc=75308@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.