all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Drew Adams <drew.adams@oracle.com>
Cc: 12911@debbugs.gnu.org
Subject: bug#12911: bug#12908: 24.3.50; file `emacs_backtrace.txt'?
Date: Sat, 17 Nov 2012 17:19:57 -0800	[thread overview]
Message-ID: <50A837BD.10707@cs.ucla.edu> (raw)
In-Reply-To: <0D5E662929EB46BABC33674094EA6A24@us.oracle.com>

On 11/17/2012 03:08 PM, Drew Adams wrote:
>> I must have missed that request; all I see from him in Bug#12908
>> > is a comment about how to deal with the file names
> That's because Stefan wrote it in the proper bug thread, and not in this one

Stefan's comment <http://bugs.gnu.org/12911#11> was in response to the request
"Please do not write such files willy nilly to the directory where the
Emacs process was opened (or whatever).  That is not user-friendly."
Stefan agreed with the request, and suggested ~/.emacs.d.  However,
the request was about Emacs's behavior on Microsoft Windows.

On GNU and other non-Microsoft platforms, Emacs already satisfies
the request, because it relies on its invoker to specify where
the debugging information will go, and in practice this approach
works reasonably well on these platforms.  Stefan's comment,
in context, does not imply that Emacs should change its behavior
on these platforms.





  parent reply	other threads:[~2012-11-18  1:19 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
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             ` Paul Eggert [this message]
2012-11-18  3:55               ` bug#12911: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50A837BD.10707@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=12911@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.