From: Scott Otterson <scotto@sharpleaf.org>
To: Eli Zaretskii <eliz@gnu.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 10:02:00 -0700 [thread overview]
Message-ID: <CAPY3P0SAeJK5nJYkp=xvemy1LsaY-Ap_Biv+rr5_Zt_4iWd7CQ@mail.gmail.com> (raw)
In-Reply-To: <83czbqvygn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
Maybe the solution is to put it in some totally unambiguous place:
~/.emacs.crashdump (or whatever)
and then change the docs to match.
On Tue, Sep 20, 2022 at 8:48 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Lars Ingebrigtsen <larsi@gnus.org>
> > Cc: Scott Otterson <scotto@sharpleaf.org>, 51758@debbugs.gnu.org
> > Date: Tue, 20 Sep 2022 16:52:26 +0200
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > >> That's right, I thought that the "current directory" was the
> > >> `current-directory'. Like most people would, I'd
> > >> guess.
> > >
> > > What is your interpretation of current-directory in this case? Where
> > > do you think that is?
> >
> > "The value of `current-directory' where the user was when the crash
> > happened" would be the natural interpretation.
>
> You mean default-directory, I presume?
>
> The problem, as I explained, is that there's a different one in every
> buffer, and there could be many of them. As far as users are
> concerned, Emacs doesn't have a well-defined notion of "current
> directory", so saying "where the user was" makes little sense with
> Emacs.
>
> > Why not just change the message to "the directory Emacs was started
> > from"? That should be clear.
>
> I'm okay with that, I just fear that many users won't know where that
> is. On MS-Windows, the starting directory can (and usually is)
> determined by the desktop shortcut used to start Emacs, and people
> rarely are aware where is that.
>
[-- Attachment #2: Type: text/html, Size: 2308 bytes --]
next prev parent reply other threads:[~2022-09-20 17:02 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 [this message]
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
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='CAPY3P0SAeJK5nJYkp=xvemy1LsaY-Ap_Biv+rr5_Zt_4iWd7CQ@mail.gmail.com' \
--to=scotto@sharpleaf.org \
--cc=51758@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).