From: Roland.Meier@continental-corporation.com
To: monnier@iro.umontreal.ca
Cc: 4587@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#4597: Antwort: Re: bug#4587: 23.1; sort-lines and sort-fields always set buffer modified
Date: Wed, 30 Sep 2009 12:00:56 +0200 [thread overview]
Message-ID: <OF2B158154.15C4FD67-ONC1257641.00349840-C1257641.003704BF@continental-corporation.com> (raw)
In-Reply-To: <jwvhbul82pq.fsf-monnier+emacsbugreports@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
> Yes, that's generally desirable. But in the above cases, given the way
> the code currently works, it's fairly inconvenient to do (the code does
> modify the buffer, it just so happens that the end text is the same as
> the original text), so it doesn't seem worth the trouble.
Wouldn't it be possible in case of an unmodified buffer to copy the
content of the region at the beginning to a temporary buffer, compare it
to the result afterwards, and if they match to restore the unmodified
status?
I sometimes need to check a list (which isn't small enough to be checked
at a glance) after editing it if it is still sorted.
Now I write he region before and after sorting it to separate files and
compare them, but I wonder if a powerful tool like emacs must keep such an
obvious annoyance like this...
Thanks!
--
Mit freundlichen Grüßen
Roland Meier
\|||/
(o o)
==ooO==U==Ooo==
[-- Attachment #2: Type: text/html, Size: 1285 bytes --]
next prev parent reply other threads:[~2009-09-30 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 16:38 bug#4587: 23.1; sort-lines and sort-fields always set buffer modified Roland.Meier
2009-09-30 4:44 ` Stefan Monnier
2009-09-30 10:00 ` Roland.Meier [this message]
2009-09-30 13:51 ` bug#4587: Antwort: " Stefan Monnier
2009-10-01 12:25 ` Kevin Rodgers
2009-10-01 14:19 ` Stefan Monnier
2009-10-25 13:41 ` Kevin Rodgers
2009-10-25 15:27 ` Stefan Monnier
2009-09-30 16:56 ` bug#4597: " Magnus Henoch
2022-05-03 19:24 ` bug#4587: " Lars Ingebrigtsen
2022-05-04 7:21 ` Eli Zaretskii
2022-05-04 7:53 ` Lars Ingebrigtsen
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=OF2B158154.15C4FD67-ONC1257641.00349840-C1257641.003704BF@continental-corporation.com \
--to=roland.meier@continental-corporation.com \
--cc=4587@emacsbugs.donarmstrong.com \
--cc=4597@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).