From: Eli Zaretskii <eliz@gnu.org>
To: Scott Otterson <scotto@sharpleaf.org>
Cc: 51758@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#51758: 27.2; Backtrace put in home dir, not current dir
Date: Tue, 20 Sep 2022 18:42:40 +0300 [thread overview]
Message-ID: <83fsgmvyq7.fsf@gnu.org> (raw)
In-Reply-To: <CAPY3P0Tj-GpVyZZ4KgSS8KKvOx+R5KJjbCP2C-UPGtMY98MLUg@mail.gmail.com> (message from Scott Otterson on Tue, 20 Sep 2022 07:31:34 -0700)
> From: Scott Otterson <scotto@sharpleaf.org>
> Date: Tue, 20 Sep 2022 07:31:34 -0700
>
> The default directory of the buffer that was active when emacs crashed. In my case, I had only one buffer
> open, so this was obvious, but I can see how it wouldn't be necessarily.
Yes, but which buffer? When Emacs crashes, there could be several
buffers in the session, each one with its own default-directory.
> So, Lars's recommended text change seems like a good one to me.
Lars suggested to say EMACSHOME, which is simply incorrect.
Would it be okay to say that the file gets written in the directory
where Emacs was started? The only problem with that is that people
may not know where that is...
[Please use "Reply All" to replay, so that the bug tracker is CC'ed.]
next prev parent reply other threads:[~2022-09-20 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 23:36 bug#51758: 27.2; Backtrace put in home dir, not current dir Scott Otterson
2022-09-20 12:22 ` Lars Ingebrigtsen
2022-09-20 12:45 ` Eli Zaretskii
2022-09-20 13:05 ` Lars Ingebrigtsen
2022-09-20 14:13 ` Scott Otterson
2022-09-20 14:24 ` Eli Zaretskii
2022-09-20 14:52 ` Lars Ingebrigtsen
2022-09-20 15:48 ` Eli Zaretskii
2022-09-20 17:02 ` Scott Otterson
2022-09-20 17:28 ` Eli Zaretskii
2022-09-20 18:14 ` Scott Otterson
[not found] ` <CAPY3P0Tj-GpVyZZ4KgSS8KKvOx+R5KJjbCP2C-UPGtMY98MLUg@mail.gmail.com>
2022-09-20 15:42 ` Eli Zaretskii [this message]
2022-09-20 15:45 ` Lars Ingebrigtsen
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=83fsgmvyq7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51758@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=scotto@sharpleaf.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).