unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 18@debbugs.gnu.org
Subject: bug#18: Fine-grained revert-buffer
Date: Sun, 20 Sep 2020 01:08:38 +0200	[thread overview]
Message-ID: <874kntjrex.fsf@gnus.org> (raw)
In-Reply-To: <CABczVweO46UcBDcdy5OA+acNdO=wH+WPj+Et9Warus9ManhK3w@mail.gmail.com> (Mauro Aranda's message of "Wed, 15 May 2019 20:10:00 -0300")

Mauro Aranda <maurooaranda@gmail.com> writes:

> I spent some time thinking on how to get this new revert command
> integrated with the rest of revert-buffer functions, and I came up with
> the attached patch.
>
> Since the difference between revert-buffer and
> revert-buffer-with-fine-grain lies at the insert-file-contents level, I
> wrote an alternative to
> revert-buffer-insert-file-contents--default-function, that uses
> replace-buffer-contents, as Eli suggested.  I named it
> revert-buffer-insert-file-contents-delicately.

[...]

> Corrections and comments are welcome.  Better names too.

This was the final message in this thread (which is the oldest
still-open bug report in debbugs!).

I tried the patch out, and it almost worked flawlessly for me -- it did
the "really edit the buffer?" userlock thing, but that was easy enough
to disable, so I did that.

And I pushed the patch set to the trunk.  I agree that perhaps the
command name isn't the most intuitive, so somebody with stronger ideas
about what the name of the command should be should go ahead and change
it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-09-19 23:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwvpruii0xr.fsf@iro.umontreal.ca>
2013-12-17  3:16 ` bug#18: Fine-grained revert-buffer Dmitry Gutov
2013-12-17 13:32   ` Stefan Monnier
2018-04-12  6:21 ` Toon Claes
2018-04-12 12:18   ` Stefan Monnier
2018-04-14  7:00     ` Toon Claes
2018-04-14 14:14       ` Stefan Monnier
2019-04-26 22:42 ` Mauro Aranda
2019-04-27  7:34   ` Eli Zaretskii
2019-04-27 15:10     ` Mauro Aranda
2019-04-27 16:30       ` Eli Zaretskii
2019-04-27 17:46         ` Mauro Aranda
2019-04-29 12:49       ` martin rudalics
2019-05-02 15:54         ` Basil L. Contovounesios
2019-05-02 16:20           ` Glenn Morris
2019-05-02 16:23             ` Basil L. Contovounesios
2019-05-02 21:27           ` Richard Stallman
2019-05-03 14:05             ` Basil L. Contovounesios
2019-05-05 22:41               ` Richard Stallman
2019-04-27  8:31   ` martin rudalics
2019-04-28  2:47   ` Richard Stallman
2019-04-29 23:32     ` Mauro Aranda
2019-04-30  0:17       ` Mauro Aranda
2019-05-15 23:10         ` Mauro Aranda
2020-09-19 23:08           ` Lars Ingebrigtsen [this message]

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=874kntjrex.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18@debbugs.gnu.org \
    --cc=maurooaranda@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).