From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: jwiegley@gmail.com, 23577@debbugs.gnu.org
Subject: bug#23577: 24.5; emacs_backtrace.txt
Date: Thu, 19 May 2016 19:35:09 +0300 [thread overview]
Message-ID: <83d1oi9fb6.fsf@gnu.org> (raw)
In-Reply-To: <df7350ad-0ac6-4b68-8621-baa00979b503@default> (message from Drew Adams on Wed, 18 May 2016 22:47:53 -0700 (PDT))
> Date: Wed, 18 May 2016 22:47:53 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 23577@debbugs.gnu.org
>
> Is there a way for me to prevent Emacs from writing such useless
> files, and return to the way things were before Emacs started
> cleverly writing them?
No.
next prev parent reply other threads:[~2016-05-19 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 19:38 bug#23577: 24.5; emacs_backtrace.txt Drew Adams
2016-05-18 19:57 ` Eli Zaretskii
2016-05-19 1:04 ` John Wiegley
2016-05-19 5:47 ` Drew Adams
2016-05-19 16:35 ` Eli Zaretskii [this message]
2016-06-05 17:47 ` bug#23577: Glenn Morris
[not found] <<4de15268-d7a7-4d69-814c-54c3d4302e2b@default>
[not found] ` <<83k2ir9m0s.fsf@gnu.org>
2016-05-18 21:08 ` bug#23577: 24.5; emacs_backtrace.txt Drew Adams
2016-05-19 4:30 ` Eli Zaretskii
2016-05-19 10:16 ` Nicolas Richard
2016-05-19 16:41 ` Eli Zaretskii
[not found] <<<4de15268-d7a7-4d69-814c-54c3d4302e2b@default>
[not found] ` <<<83k2ir9m0s.fsf@gnu.org>
[not found] ` <<b9346a09-71ed-435f-9520-6c331fa1bdbb@default>
[not found] ` <<83h9duacvb.fsf@gnu.org>
2016-05-19 6:06 ` Drew Adams
2016-05-20 12:04 ` Nicolas Richard
2016-05-20 13:50 ` Drew Adams
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=83d1oi9fb6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23577@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=jwiegley@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).