From: Matthew Persico <matthew.persico@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 37390@debbugs.gnu.org
Subject: bug#37390: 26.3; ediff-buffers appears to have a focus issue
Date: Tue, 17 Sep 2019 08:19:15 -0400 [thread overview]
Message-ID: <CAL20dLBiWh7tOtcVWjtPW3JsdK5NetoF7Kp09Kotw4o1dAhQug@mail.gmail.com> (raw)
In-Reply-To: <dcdda7c6-359c-eee7-42f4-8245971b4b37@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Split window horizontally? Oh man I have to try that!
On Tue, Sep 17, 2019 at 4:56 AM martin rudalics <rudalics@gmx.at> wrote:
> > For YEARS I've been using a separate frame for control. I'll just toggle
> > that off. No issues with that in 26.2. I will try in 26.3. And now that
> I
> > see it, why the heck would you want a separate frame? To have multiple
> > diffs going at the same time?
>
> 'ediff-window-setup-function' has a misguided default value. Luckily
> you can change it - the speedbar, for example, doesn't allow to do
> that. I'm using 'ediff-setup-windows-plain' ever since together with
> 'ediff-split-window-function' set to 'split-window-horizontally'.
>
> martin
>
--
Matthew O. Persico
[-- Attachment #2: Type: text/html, Size: 1174 bytes --]
next prev parent reply other threads:[~2019-09-17 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 15:42 bug#37390: 26.3; ediff-buffers appears to have a focus issue Matthew Persico
2019-09-13 7:36 ` martin rudalics
2019-09-15 8:26 ` martin rudalics
2019-09-15 23:38 ` Matthew Persico
2019-09-16 16:46 ` Matthew Persico
2019-09-16 18:37 ` Matthew Persico
2019-09-17 8:56 ` martin rudalics
2019-09-17 12:19 ` Matthew Persico [this message]
2019-09-17 12:25 ` Matthew Persico
2019-09-17 12:29 ` Matthew Persico
2019-09-18 7:45 ` martin rudalics
2019-09-18 22:31 ` Noam Postavsky
2019-09-19 8:19 ` martin rudalics
2019-09-17 8:55 ` martin rudalics
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=CAL20dLBiWh7tOtcVWjtPW3JsdK5NetoF7Kp09Kotw4o1dAhQug@mail.gmail.com \
--to=matthew.persico@gmail.com \
--cc=37390@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).