From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 75308@debbugs.gnu.org, phelps@gnusto.com, michael.albinus@gmx.de
Subject: bug#75308: 30.0.93; man.el assume shell is bash
Date: Fri, 03 Jan 2025 10:50:56 +0200 [thread overview]
Message-ID: <86ttaggu1b.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkWsjB-FLtzkUwr-REzNjGb4YK-0c53sucN+WxC6p1t7g@mail.gmail.com> (message from Stefan Kangas on Fri, 3 Jan 2025 02:46:28 -0600)
> 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.
next prev parent reply other threads:[~2025-01-03 8:50 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 [this message]
2025-01-03 9:26 ` Stefan Kangas
2025-01-03 11:47 ` Eli Zaretskii
2025-01-04 7:12 ` Ted Phelps
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=86ttaggu1b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75308@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=phelps@gnusto.com \
--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.