From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: lekktu@gmail.com, 12908@debbugs.gnu.org
Subject: bug#12908: 24.3.50; file `emacs_backtrace.txt'?
Date: Sat, 17 Nov 2012 08:36:52 -0800 [thread overview]
Message-ID: <3F1572E6BD6046649786AD0DD7B93FF2@us.oracle.com> (raw)
In-Reply-To: <83y5i03d7j.fsf@gnu.org>
> > Then put it under the Emacs installation directory.
> > The point is to get it away from user files.
>
> Again, I just mimicked the behavior on Unix, as best as possible.
> Please read the manual to learn where this information is put on Unix.
No one is blaming you, and certainly not for making things consistent with what
is done on Unix. You have pointed out that the bug (annoyance) exists on Unix
also. Fine. So let's correct it everywhere.
next prev parent reply other threads:[~2012-11-17 16:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 18:30 bug#12908: 24.3.50; file `emacs_backtrace.txt'? Drew Adams
2012-11-16 18:40 ` Juanma Barranquero
2012-11-16 19:08 ` Drew Adams
2012-11-16 19:42 ` Eli Zaretskii
2012-11-16 21:02 ` Drew Adams
2012-11-17 7:23 ` Eli Zaretskii
2012-11-17 16:36 ` Drew Adams [this message]
2012-11-16 21:49 ` Stefan Monnier
2012-11-17 7:27 ` Eli Zaretskii
2012-11-16 19:00 ` Eli Zaretskii
2012-11-16 19:22 ` Drew Adams
2012-11-16 19:39 ` Eli Zaretskii
2012-11-16 20:56 ` Drew Adams
2012-11-17 7:21 ` Eli Zaretskii
2012-11-17 16:36 ` 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-17 23:08 ` bug#12911: " Drew Adams
2012-11-18 1:12 ` Paul Eggert
2012-11-18 1:19 ` bug#12911: " Paul Eggert
2012-11-18 3:55 ` Eli Zaretskii
2012-11-18 3:56 ` Eli Zaretskii
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 1:24 ` Paul Eggert
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
2012-11-18 7:08 ` bug#12908: 24.3.50; file `emacs_backtrace.txt'? Achim Gratz
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=3F1572E6BD6046649786AD0DD7B93FF2@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12908@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.com \
/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).