From: Scott Otterson <scotto@sharpleaf.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51758@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#51758: 27.2; Backtrace put in home dir, not current dir
Date: Tue, 20 Sep 2022 07:13:36 -0700 [thread overview]
Message-ID: <CAPY3P0Q_6udoWfq++34jM3LNW-7LFR7D61AMAo1CUQY5xkcgwQ@mail.gmail.com> (raw)
In-Reply-To: <87bkragpra.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
That's right, I thought that the "current directory" was the
`current-directory'. Like most people would, I'd guess.
On Tue, Sep 20, 2022 at 6:05 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> "Select:\n"
> >> "YES -- to debug Emacs, or\n"
> >> "NO -- to abort Emacs and produce a backtrace\n"
> >> " (emacs_backtrace.txt in current directory)."
> >> #if __GNUC__
> >> "\n\n(type \"gdb -p <emacs-PID>\" and\n"
> >> "\"continue\" inside GDB before clicking YES.)"
> >> #endif
> >> , "Emacs Abort Dialog",
> >>
> >> Eli, should that text just be amended? (If it always puts the backtrace
> >> in EMACSHOME, that is -- I haven't actually cheked the code here.)
> >
> > The text is correct. I'm guessing the OP starts Emacs from EMACSHOME
> > directory.
>
> Or perhaps the user thinks that the "current directory" here is
> `current-directory'?
>
[-- Attachment #2: Type: text/html, Size: 1741 bytes --]
next prev parent reply other threads:[~2022-09-20 14:13 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPY3P0Q_6udoWfq++34jM3LNW-7LFR7D61AMAo1CUQY5xkcgwQ@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 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.