From: Alan Third <alan@idiocy.org>
To: Raj Krishnan <rajkrishnan1996@gmail.com>
Cc: 48579@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 11:26:16 +0100 [thread overview]
Message-ID: <YKjcSA/E3hO+i8Z7@idiocy.org> (raw)
In-Reply-To: <CAOotCtPMnHpVmetVs+EncvtqCsVuaSwNkuEsvMKAqBkhGJZygw@mail.gmail.com>
On Sat, May 22, 2021 at 11:00:43AM +0530, Raj Krishnan wrote:
> Steps for reproduction:
> 1. Run =emacs -Q= in some directory outside the user's home directory
> 2. Check the value of the variable =default-directory=, and verify that
> it matches the directory you started emacs in
> 3. Create an emacs child process using:
>
> #+begin_src emacs_lisp
> (call-process
> (file-truename (expand-file-name invocation-name invocation-directory))
> nil nil nil "-Q")
> #+end_src
>
> 4. In the newly created frame, check the value of the default directory
>
> 5. Behavior on GNU/Linux: The directory matches the value shown in (2)
> Behavior on macOS: The default directory has changed to the user's
> home directory
>
> The behavior was spotted when we noticed inconsistent behavior in
> [[https://github.com/minad/affe][affe.el]], which was subsequently
> reproduced using =emacs -Q=
The NS port checks if it's connected to a TTY when it starts, and if
not assumes it's being run from finder and so sets the starting
directory to something useful ($HOME), instead of / or whatever it
defaults to.
--
Alan Third
next prev parent reply other threads:[~2021-05-22 10:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 5:30 bug#48579: 28.0.50; Spawning an emacs process using call-process results in inconsistent behavior between GNU/Linux and macOS Raj Krishnan
2021-05-22 10:26 ` Alan Third [this message]
2021-05-22 10:39 ` Eli Zaretskii
2021-05-22 11:35 ` Raj Krishnan
2021-05-22 11:44 ` bug#48579: 28.0.50; Spawning an emacs process using call-process results in inconsistent, " Daniel Mendler
2021-05-22 12:06 ` Alan Third
2021-05-22 12:14 ` Daniel Mendler
2021-05-22 12:29 ` Eli Zaretskii
2021-05-22 12:41 ` Daniel Mendler
2021-05-22 12:47 ` Eli Zaretskii
2021-05-22 13:01 ` Alan Third
2021-05-22 13:10 ` Daniel Mendler
2021-05-22 13:10 ` Eli Zaretskii
2021-05-22 13:15 ` Daniel Mendler
2022-07-15 10:01 ` bug#48579: 28.0.50; Spawning an emacs process using call-process results in inconsistent " Lars Ingebrigtsen
2021-05-22 12:20 ` bug#48579: 28.0.50; Spawning an emacs process using call-process results in inconsistent, " Eli Zaretskii
2021-05-22 12:37 ` Daniel Mendler
2021-05-22 12:46 ` Eli Zaretskii
2021-05-22 12:54 ` Daniel Mendler
2021-05-22 13:04 ` Alan Third
2021-05-22 13:13 ` Daniel Mendler
2021-05-22 13:20 ` Daniel Mendler
2021-05-22 13:09 ` Eli Zaretskii
2021-05-23 10:30 ` Philipp
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=YKjcSA/E3hO+i8Z7@idiocy.org \
--to=alan@idiocy.org \
--cc=48579@debbugs.gnu.org \
--cc=rajkrishnan1996@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 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.