From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: restoring window configuration after vc-ediff
Date: Sat, 14 May 2022 13:31:07 +0100 [thread overview]
Message-ID: <87ilq8b8j8.fsf@ucl.ac.uk> (raw)
In-Reply-To: 83mtfkl5r2.fsf@gnu.org
On Saturday, 14 May 2022 at 14:21, Eli Zaretskii wrote:
> The easiest way of leaving your window configuration untouched by a
> command is to invoke that command in a separate frame.
Well, sure, but it definitely adds friction... currently, a simple key
binding invokes vc-ediff. I would have to include creating and deleting
a frame to the process. And this interferes to some degree with the
window (x parlance) manager.
For vc-ediff, there's (generally) no benefit in having the previous
version buffer remain visible after the ediff operation is finished.
I guess I'll advise the function instead making use of
save-window-excursion.
thank you,
eric
--
Eric S Fraga via gnus (Emacs 29.0.50 2022-05-10) on Debian 11.3
next prev parent reply other threads:[~2022-05-14 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 10:46 restoring window configuration after vc-ediff Eric S Fraga
2022-05-14 11:21 ` Eli Zaretskii
2022-05-14 12:31 ` Eric S Fraga [this message]
2022-05-14 13:31 ` Eli Zaretskii
2022-05-14 14:55 ` Eric S Fraga
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=87ilq8b8j8.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@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.
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).