unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nika Otiashvili <nikaoto@gmail.com>
Cc: 45357@debbugs.gnu.org
Subject: bug#45357: [PATCH] * lisp/man.el (Man-getpage-in-background): always use shell-file-name
Date: Tue, 22 Dec 2020 17:14:23 +0200	[thread overview]
Message-ID: <83zh25rhyo.fsf@gnu.org> (raw)
In-Reply-To: <CAHJNDzd7xqaeiFktD1E_Dsp61cwrdz402qoJw9-pNKBKqu0xJQ@mail.gmail.com> (message from Nika Otiashvili on Mon, 21 Dec 2020 23:24:13 +0400)

> From: Nika Otiashvili <nikaoto@gmail.com>
> Date: Mon, 21 Dec 2020 23:24:13 +0400
> 
> First time sending a patch to bug-gnu-emacs, not sure if this is the
> correct format.
> Please indicate any errors I made in my formatting of the email or the
> attached patch file.

In terms of formatting the patch, I see no problems with your
submission.

My problem is more a conceptual one: it is not trivial to replace
/bin/sh with any other shell, because they work differently.  The
command in question builds a complex shell command to run, and it
isn't obvious that any user shell will be able to run it.

OTOH, every Posix system I know about does have /bin/sh, so I'm
curious what kind of system did you see where /bin/sh is absent.

And finally, I don't think I understand the issue with .bashrc etc.:
if you launch /bin/sh, it is not supposed to process these init files,
they are processed by bash, zsh, and other shells.

Could you please elaborate on the specific problems you had and tell
more about your system configuration where you bumped into these
problems?

Thanks.





  reply	other threads:[~2020-12-22 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 19:24 bug#45357: [PATCH] * lisp/man.el (Man-getpage-in-background): always use shell-file-name Nika Otiashvili
2020-12-22 15:14 ` Eli Zaretskii [this message]
2020-12-22 18:50   ` Michael Albinus
2020-12-23  0:55     ` Nika Otiashvili
2020-12-23  8:17       ` Michael Albinus

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zh25rhyo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45357@debbugs.gnu.org \
    --cc=nikaoto@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).