From: Glenn Morris <rgm@gnu.org>
To: Walter Esling <wtresling@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Building 24.3 Problem
Date: Fri, 21 Feb 2014 13:22:33 -0500 [thread overview]
Message-ID: <olr46wgwba.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAA7vtkP3zGLM_d66AwtXpkiD3-QLBsX9Tkx_Hnm78R0hmUgVAg@mail.gmail.com> (Walter Esling's message of "Fri, 21 Feb 2014 08:09:00 -0600")
Walter Esling wrote:
> The build completed without error and emacs runs, but it is unable to save
> modified buffers. The message comes up "Saving file ...", but the file is
> never saved and buffer is left modified.
Does this problem still happen if you start emacs as "emacs -Q"?
If not, crystal ball says that you are adding something to
write-file-functions, or some other hook, in your .emacs, which returns
nil:
C-h v write-file-functions
List of functions to be called before writing out a buffer to a file.
If one of them returns non-nil, the file is considered already written[...]
next prev parent reply other threads:[~2014-02-21 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 14:09 Building 24.3 Problem Walter Esling
2014-02-21 18:08 ` Andreas Röhler
2014-02-21 18:22 ` Glenn Morris [this message]
2014-02-21 18:23 ` Glenn Morris
2014-02-21 20:03 ` walter esling
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=olr46wgwba.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=wtresling@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.
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).