From: Daniel Mendler <mail@daniel-mendler.de>
To: Alan Third <alan@idiocy.org>, Eli Zaretskii <eliz@gnu.org>,
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 15:13:03 +0200 [thread overview]
Message-ID: <b6620c12-edbf-6af7-2cc8-5ff701bcef5e@daniel-mendler.de> (raw)
In-Reply-To: <YKkBepRHimos55d8@idiocy.org>
On 5/22/21 3:04 PM, Alan Third wrote:
> On Sat, May 22, 2021 at 02:54:26PM +0200, Daniel Mendler wrote:
>> But this discussion here seems to be a bit off-track. My point here is
>> that the current working directory determination on MacOS uses a
>> heuristic, which is not correct. It incorrectly determines that Emacs
>> has been launched from the finder or some other Mac GUI application and
>> therefore changes the directory to the home directory. If Emacs is
>> indeed started from the GUI, this makes all sense. But this is not the
>> case here. The TTY heuristic, that Alan described, is insufficient.
>
> I can't find any other way, and we had multiple complaints when the
> behaviour was broken whereas this is the first complaint in the other
> direction that I've seen.
>
> If you find an alternative, please let us know.
As I wrote, if "--batch" opts out of this, I am happy. I should have
used "--batch" right away in my program. Since this is what I am doing -
I am starting a batch background worker job. I just wasn't aware of the
opt-out. Hopefully the batch setting does not have other unexpected side
effects.
next prev parent reply other threads:[~2021-05-22 13:13 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
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 [this message]
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
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=b6620c12-edbf-6af7-2cc8-5ff701bcef5e@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=48579@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
/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).