all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60032@debbugs.gnu.org
Subject: bug#60032: 30.0.50; [WISH] Customizing Info directories
Date: Sat, 17 Dec 2022 14:55:43 +0200	[thread overview]
Message-ID: <83tu1ugpf4.fsf@gnu.org> (raw)
In-Reply-To: <87wn6up9fc.fsf@localhost> (message from Ihor Radchenko on Wed, 14 Dec 2022 10:27:19 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 60032@debbugs.gnu.org
> Date: Wed, 14 Dec 2022 10:27:19 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Changing environment variables is something I never ever needed to
> >> customize Emacs' behaviour. Once I see it, my thinking goes: "Surely,
> >> there should be some custom variable.", but no such variable exists.
> >
> > Does this include PATH?  If not, why not?
> >
> > IME, the *PATH variables are quite special: they should generally be
> > set from outside Emacs, and doing the same via customization options
> > is usually not a good idea.
> 
> I agree. However, I expect in-Emacs info reader to be more configurable.
> It's not like info.el requires external system tools. I prefer Emacs to
> be portable as much as sanely possible.

Feel free to submit a patch for the master branch.  We will then have
enough time to see if it causes trouble for someone.





  reply	other threads:[~2022-12-17 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 13:19 bug#60032: 30.0.50; [WISH] Customizing Info directories Ihor Radchenko
2022-12-13 13:31 ` Eli Zaretskii
2022-12-13 13:43   ` Ihor Radchenko
2022-12-13 14:39     ` Eli Zaretskii
2022-12-14 10:27       ` Ihor Radchenko
2022-12-17 12:55         ` Eli Zaretskii [this message]
2022-12-15  0:23 ` Michael Heerdegen

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=83tu1ugpf4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60032@debbugs.gnu.org \
    --cc=yantar92@posteo.net \
    /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.