From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 12911@debbugs.gnu.org
Subject: bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written
Date: Tue, 20 Nov 2012 09:11:46 -0800 [thread overview]
Message-ID: <A5B77C60B99D463D8B4818431132BD6F@us.oracle.com> (raw)
In-Reply-To: <CAAeL0STTFjDRCjWUbQJOc1=YdF+M9JG6_BypOfr1X9_vQN+yeg@mail.gmail.com>
> > FWIW, I'd be annoyed if I were a w32 user and had to deal with
> > emacs_backtrace.txt files appearing in directories without my saying
> > so explicitly.
>
> Windows binaries for official releases (as opposed to trunk snapshots)
> rarely crash. It's not as if the user is going to get backtraces all
> over his hard disk on every single run.
FWIW, that is not my experience, not with Emacs 24.
Official Emacs binaries 24.1 and 24.2 crash for me, seemingly randomly, sooner
or later, pretty much each time I use them - and I don't get to use them for
long. If I had a recipe I would send it along. I sent an emacs-backtrace.txt
file recently, which Eli said should be useful, but no news yet on whether it
helped fix some bug. ;-)
I agree, however, that a user is not going to be getting backtraces all over the
place. That's some consolation, but not reason enough by itself to introduce
this regression, IMHO (just one opinion).
As Eli himself said - and was the first to point out AFAIK
(http://lists.gnu.org/archive/html/emacs-devel/2012-09/msg00501.html):
EZ> Based on my experience, I expect this "feature" to be hated,
EZ> by users and Emacs maintainers alike.
I think he's likely to be right in that guess. And he points out several
reasons against introducing this feature (reasons I'm not qualified to judge).
Eli also said, there:
EZ> using the limited information it provides can be quite difficult
Whether the feature is worth the various drawbacks mentioned, I, for one, cannot
say.
But it sure would be good to find a way to put these backtrace files somewhere
other than a user folder. That I will say.
FWIW, both Emacs maintainers have seemed to agree. Yidong said this
(http://lists.gnu.org/archive/html/emacs-devel/2012-09/msg00870.html):
CY> Littering the filesystem with these backtrace files is
CY> kind of obnoxious.
Certainly, plopping them into user folders is. User data is not for Emacs to
fiddle with uninvited, and that includes folders.
next prev parent reply other threads:[~2012-11-20 17:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 20:48 bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Drew Adams
2012-11-16 21:05 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files " Drew Adams
2012-11-16 21:19 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files " Stefan Monnier
2012-11-17 7:26 ` Eli Zaretskii
2012-11-17 17:38 ` Drew Adams
2012-11-17 17:55 ` Eli Zaretskii
2012-11-17 18:24 ` Drew Adams
2012-11-19 1:52 ` Stefan Monnier
2012-11-19 3:51 ` Eli Zaretskii
2012-11-19 4:07 ` Stefan Monnier
2012-11-19 15:52 ` Eli Zaretskii
2012-11-19 18:04 ` Stefan Monnier
2012-11-19 18:13 ` Eli Zaretskii
2012-11-19 18:35 ` Stefan Monnier
2012-11-19 18:40 ` Eli Zaretskii
2012-11-19 19:47 ` Stefan Monnier
2012-11-19 20:05 ` Eli Zaretskii
2012-11-19 21:15 ` Stefan Monnier
2012-11-20 3:58 ` Eli Zaretskii
2012-11-20 4:59 ` Stefan Monnier
2012-11-20 5:02 ` Daniel Colascione
2012-11-20 13:16 ` Andy Moreton
2012-11-20 16:27 ` Eli Zaretskii
2012-11-20 17:03 ` Eli Zaretskii
2012-11-20 17:36 ` Daniel Colascione
2012-11-20 18:02 ` Eli Zaretskii
2012-11-20 18:57 ` bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' " Drew Adams
2012-11-20 19:58 ` Eli Zaretskii
2012-11-20 21:47 ` Drew Adams
2012-11-21 3:47 ` Eli Zaretskii
2012-11-21 4:03 ` Daniel Colascione
2012-11-21 15:43 ` Juanma Barranquero
2012-11-21 16:24 ` bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written Drew Adams
[not found] ` <E86D7DFBD2BD4C3394E5316EF0321A! 95@us.oracle.com>
2012-11-21 16:45 ` Juanma Barranquero
2012-11-21 17:40 ` Drew Adams
2012-11-21 17:43 ` Juanma Barranquero
2012-11-21 18:01 ` Drew Adams
2012-11-21 18:13 ` Juanma Barranquero
2012-11-21 18:42 ` Drew Adams
2012-11-20 18:30 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Stefan Monnier
2012-11-20 18:37 ` Eli Zaretskii
2012-11-20 20:15 ` Stefan Monnier
2012-11-20 16:36 ` Juanma Barranquero
2012-11-20 17:11 ` Drew Adams [this message]
2012-11-20 17:53 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files " Eli Zaretskii
2012-11-20 18:10 ` Drew Adams
2012-11-20 18:27 ` Eli Zaretskii
2012-11-20 19:15 ` Dani Moncayo
2012-11-20 19:41 ` Eli Zaretskii
2012-11-20 20:11 ` Dani Moncayo
2012-11-20 17:49 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files " Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2012-11-16 18:30 bug#12908: 24.3.50; file `emacs_backtrace.txt'? Drew Adams
2012-11-17 18:45 ` Paul Eggert
2012-11-17 19:09 ` Eli Zaretskii
2012-11-17 19:29 ` Paul Eggert
2012-11-17 19:42 ` Eli Zaretskii
2012-11-17 21:25 ` Paul Eggert
2012-11-18 4:04 ` Eli Zaretskii
2012-11-18 5:19 ` Paul Eggert
2012-11-18 17:16 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Eli Zaretskii
2012-11-18 19:18 ` Paul Eggert
2012-11-18 21:10 ` Eli Zaretskii
2012-11-19 1:44 ` Stefan Monnier
2012-11-19 3:50 ` Eli Zaretskii
2012-11-17 23:01 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Drew Adams
2012-11-18 3:58 ` Eli Zaretskii
2012-11-18 4:40 ` Drew Adams
2012-11-18 17:53 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Eli Zaretskii
2012-11-18 18:42 ` Drew Adams
2012-11-18 5:19 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Paul Eggert
2012-11-18 17:08 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written Eli Zaretskii
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=A5B77C60B99D463D8B4818431132BD6F@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12911@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).