From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tino Calancha <f92capac@gmail.com>
Cc: kifer@cs.stonybrook.edu, 21854@debbugs.gnu.org
Subject: bug#21854: Ediff 2.81.5 of July 4, 2013; unified plain/multi frame behaviour on exit
Date: Thu, 12 May 2022 14:30:38 +0200 [thread overview]
Message-ID: <8735hfylu9.fsf@gnus.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1511080025270.11665@calancha-ilc.kek.jp> (Tino Calancha's message of "Sun, 8 Nov 2015 00:29:03 +0900 (JST)")
Tino Calancha <f92capac@gmail.com> writes:
> epatch-buffer:
>
> I) on multiframe mode: set current buffer on exit as ediff-buffer-B
> II) on plain frame mode: set current buffer on exit as ediff-buffer-A
>
> Users using emacs with and without X, keeping the default value
> of ediff-window-setup-function
> will experience I) (emacs with GUI) or II) (emacs without GUI).
>
> Its better if the current buffer is the same regarless on if
> the user is running in plain or multiframe mode.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I'm not sure I quite understand this bug report. Is the issue that
epatch-buffer chooses different A/B buffers if you have several frames,
and the A/B buffers are in different frames?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-12 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 15:29 bug#21854: Ediff 2.81.5 of July 4, 2013; unified plain/multi frame behaviour on exit Tino Calancha
2022-05-12 12:30 ` Lars Ingebrigtsen [this message]
2022-06-09 15:03 ` 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=8735hfylu9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21854@debbugs.gnu.org \
--cc=f92capac@gmail.com \
--cc=kifer@cs.stonybrook.edu \
/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).