unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Set the HOME environment variable in Emacs package debug script instead of using it on command line.
Date: Wed, 27 Oct 2021 08:40:58 +0800	[thread overview]
Message-ID: <CAGP6POJPV9OVyEofXmderYUOdH2KfMzPiev2=YBqUgUbwAUQ+g@mail.gmail.com> (raw)
In-Reply-To: <87pmrrkhvb.fsf@zoho.eu>

On Tue, Oct 26, 2021 at 9:58 PM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> > Although in these two methods, you get the same HOME
> > variable in Emacs, this does not mean that the order of the
> > libraries and related subprocesses called during Emacs
> > startup is exactly the same.
>
> These are the methods I'm familiar with.

See here [1] for more detailed explanation:

```quoted
Some software uses /etc/passwd instead of the HOME variable.
It's a bug.

Possibly you can inspect 'proxychains-ng-socks5' if it's an script and
fix the bug yourself.

That bug was very common in the past. Fortunately nowadays most
software has fixed it. Ivan Shmakov commented about that in
comp.emacs a pair of years ago:

Ivan Shmakov <iv...@siamics.net> on comp.emacs
Message-ID: <8736wyx2...@violet.siamics.net>

Unfortunately, some software refers to passwd(5) data directly
instead, leaving no way for the user to override the home
directory location. In particular, this was the behavior (IIRC)
of programs based on older Glib versions. And I vaguely recall
that Emacs might have been affected as well.
```

[1] https://groups.google.com/g/comp.unix.shell/c/3vrq7pqoG-A/m/Hnk0lsKfAwAJ

HZ



  reply	other threads:[~2021-10-27  0:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  2:01 Set the HOME environment variable in Emacs package debug script instead of using it on command line Hongyi Zhao
2021-10-26  5:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-26  9:57   ` Hongyi Zhao
2021-10-26 11:25     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-26 12:37       ` Hongyi Zhao
2021-10-26 12:49         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-26 13:39           ` Hongyi Zhao
2021-10-26 13:58             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-27  0:40               ` Hongyi Zhao [this message]
2021-10-27  0:52                 ` Emanuel Berg via Users list for the GNU Emacs text editor

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='CAGP6POJPV9OVyEofXmderYUOdH2KfMzPiev2=YBqUgUbwAUQ+g@mail.gmail.com' \
    --to=hongyi.zhao@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.
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).