From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: restoring window configuration after vc-ediff
Date: Sat, 14 May 2022 14:21:05 +0300 [thread overview]
Message-ID: <83mtfkl5r2.fsf@gnu.org> (raw)
In-Reply-To: <87mtfkbded.fsf@ucl.ac.uk> (message from Eric S Fraga on Sat, 14 May 2022 11:46:02 +0100)
> From: Eric S Fraga <e.fraga@ucl.ac.uk>
> Date: Sat, 14 May 2022 11:46:02 +0100
>
> I often use vc-ediff instead of vc-diff to see the differences between
> the working copy and a previous version. Works very well. I have just
> one quibble: when I quit ediff, the previous version buffer is still
> displayed. Is there an easy way to restore the window configuration to
> what it was when vc-ediff is invoked?
The easiest way of leaving your window configuration untouched by a
command is to invoke that command in a separate frame.
next prev parent reply other threads:[~2022-05-14 11:21 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 [this message]
2022-05-14 12:31 ` Eric S Fraga
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=83mtfkl5r2.fsf@gnu.org \
--to=eliz@gnu.org \
--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).