unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Multiple definitions of explicit-shell-file-name
Date: Thu, 16 Apr 2020 18:54:59 +0100	[thread overview]
Message-ID: <87zhbb71u4.fsf@tcd.ie> (raw)
In-Reply-To: <jwv5zdzfrnn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 16 Apr 2020 10:12:04 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I noticed that explicit-shell-file-name has been defined as a user
>> option in three different places since at least as far back as 1997:
>>
>> - lisp/shell.el
>> - lisp/term.el
>> - lisp/obsolete/terminal.el
>>
>> Each file also assigns it a different custom :group.  Can we consolidate
>> these duplicates in a single place such as lisp/simple.el, as follows?
>
> I don't think it belongs in simple.el.  It should be in shell.el.

I agree, but explicit-shell-file-name is used in contexts unrelated to
shell.el, such as ansi-term and dired-insert-directory.

Rather than define explicit-shell-file-name in a central place like
simple.el, should these external users all check that the variable is
bound first?

If so, I'll update the patch and send it to the issue tracker for
further feedback.

Thanks,

-- 
Basil



  reply	other threads:[~2020-04-16 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 23:58 Multiple definitions of explicit-shell-file-name Basil L. Contovounesios
2020-04-16  0:06 ` Basil L. Contovounesios
2020-04-16  5:15   ` Eli Zaretskii
2020-04-16 14:12 ` Stefan Monnier
2020-04-16 17:54   ` Basil L. Contovounesios [this message]
2020-04-16 18:05     ` Stefan Monnier

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=87zhbb71u4.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).