GNU bug report logs -
#51758
27.2; Backtrace put in home dir, not current dir
Previous Next
Full log
Message #39 received at 51758 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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 <at> gnu.org> wrote:
> > From: Lars Ingebrigtsen <larsi <at> gnus.org>
> > Cc: Scott Otterson <scotto <at> sharpleaf.org>, 51758 <at> debbugs.gnu.org
> > Date: Tue, 20 Sep 2022 16:52:26 +0200
> >
> > Eli Zaretskii <eliz <at> 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.
>
[Message part 2 (text/html, inline)]
This bug report was last modified 124 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.