From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Warning with latest git pull
Date: Mon, 25 Feb 2013 18:27:09 +0100 [thread overview]
Message-ID: <87liacgv82.fsf@Rainer.invalid> (raw)
In-Reply-To: 87mwusmzvo.fsf@bzg.ath.cx
Bastien writes:
> I fixed the comment, thanks.
I'm starting to sound like Drew, but the new comment says exactly what
the old one did, just the two parts juxtaposed.
The point of having the new macro is to avoid the question about
reverting the file when the file visited by a buffer has been edited
outside Emacs. You can do exactly the same changes (cosmetic or not)
with both macros, but org-unmodified will ask you when the file and the
buffer have diverged due to the file changing outside Emacs. You
shouldn't do this of course unless you know with certainty that you are
never going to save the file. There's another difference between these
two: org-unmodified does not let you change read-only buffers (I don't
know if that's intentional or not). With all this said, the
compatibility part of org-with-silent-modifications can't simply be
plugging in org-unmodified (this loses functionality that presumably was
needed). The change to make from the implementation I gave would be
losing the let-bindings for buffer-file-name buffer-file-truename and
perhaps inhibit-read-only.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-02-25 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 18:18 Warning with latest git pull Thomas S. Dye
2013-02-21 21:12 ` Bastien
2013-02-23 9:22 ` Achim Gratz
2013-02-23 11:21 ` Bastien
2013-02-23 11:57 ` Achim Gratz
2013-02-23 13:00 ` Bastien
2013-02-23 13:37 ` Achim Gratz
2013-02-25 9:54 ` Bastien
2013-02-23 19:53 ` Achim Gratz
2013-02-24 9:29 ` Bastien
2013-02-24 10:10 ` Achim Gratz
2013-02-25 10:50 ` Bastien
2013-02-25 17:27 ` Achim Gratz [this message]
2013-02-26 13:53 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87liacgv82.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).