From: Eli Zaretskii <eliz@gnu.org>
To: 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 05:58:33 +0200 [thread overview]
Message-ID: <83zk2dvsba.fsf@gnu.org> (raw)
In-Reply-To: <jwvy5hxxpv3.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: drew.adams@oracle.com, 12911@debbugs.gnu.org
> Date: Mon, 19 Nov 2012 16:15:17 -0500
>
> > Making it in ~/.emacs.d on w32 alone doesn't change the basic fact
> > that most of the users we care about will still have their backtraces
> > in random places.
>
> No, ~/.xsesson-errors is not a random place. Even if the user doesn't
> know it, we do.
This place is also platform-specific. Not on every Posix platform
stderr is put there.
> > Why not change that on all platforms?
>
> Because stderr is good enough under GNU/Linux (and it's easy to
> redirect when it matters).
And the current arrangement on Windows is good enough for that system.
> > Why demand that only of w32?
>
> Because currently w32 users get annoyed with new files appearing where
> they don't want any.
Only one user complained so far.
> If you prefer to always send it to stderr under Windows, please do
> so, I really couldn't care less if that means it's usually sent to
> /dev/null.
Well, I do care, so I wrote the code to be better than that.
> No, writing to an arbitrary file in the current directory is not
> a good arrangement.
I disagree, obviously.
> I didn't like the backtrace business to start with and am finding it
> worse by the day.
Should I say "told you so"?
next prev parent reply other threads:[~2012-11-20 3:58 UTC|newest]
Thread overview: 66+ 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 [this message]
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 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files " Drew Adams
2012-11-20 17:53 ` 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 20:37 ` selected-frame and selected-window Stefan Monnier
2012-11-21 17:05 ` Stefan Monnier
2012-12-08 12:24 ` Eli Zaretskii
2012-12-08 23:51 ` Stefan Monnier
2012-12-09 3:50 ` Eli Zaretskii
2012-12-14 15:53 ` Stefan Monnier
2012-12-14 16:04 ` Eli Zaretskii
2012-11-20 17:49 ` bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zk2dvsba.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12911@debbugs.gnu.org \
--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 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.