GNU bug report logs - #48579
28.0.50; Spawning an emacs process using call-process results in inconsistent behavior between GNU/Linux and macOS

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Third <alan <at> idiocy.org>
Cc: mail <at> daniel-mendler.de, alan <at> idiocy.org, 48579 <at> debbugs.gnu.org
Subject: bug#48579: 28.0.50; Spawning an emacs process using call-process results in inconsistent, behavior between GNU/Linux and macOS
Date: Sat, 22 May 2021 16:10:59 +0300

> Date: Sat, 22 May 2021 14:01:06 +0100
> From: Alan Third <alan <at> idiocy.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 48579 <at> debbugs.gnu.org
> 
> > the problem here is if Emacs is started from a script. Would it be
> > possible to adjust the directory changing behavior, for example if
> > Emacs is started with the arguments `--daemon`, `--batch` or
> > `--script`? Is there another way to detect if the finder launched
> > Emacs, such that only in that case the directory changing to the
> > home directory takes place?
> 
> You can run with "-t", "-nw", "--chdir", "--batch" or "--script" to
> disable this behaviour.

That again doesn't necessarily mean you'd be able to tell the cwd of
the Emacs process at any time during the session.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.