From: Lars Ingebrigtsen <larsi@gnus.org>
To: Keith Rautenbach <krautenbach@ntlworld.com>
Cc: 11544@debbugs.gnu.org, 11480@debbugs.gnu.org
Subject: bug#11544: Subject: 24.1.50; ediff-buffers command window does not work properly
Date: Mon, 02 May 2022 11:43:31 +0200 [thread overview]
Message-ID: <87v8uo2rss.fsf@gnus.org> (raw)
In-Reply-To: <87y5otlui5.fsf@ntlworld.com> (Keith Rautenbach's message of "Tue, 15 May 2012 09:26:58 +0100")
Keith Rautenbach <krautenbach@ntlworld.com> writes:
> Typing ediff command '?' initially redraws the command frame at the
> correct size and then auto-shrinks the width down to 1.
>
> I am seeing the problem happen most (but not all) the time. Perhaps 95%.
> I think that a particular run of emacs will either happen 100% or 0%.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Do you still see this in recent versions of Emacs and/or the operating
system? The best guess in this bug report seemed to indicate that this
might be due to a bug/misfeature in Unity, if I skim it correctly.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-02 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 8:26 bug#11480: 24.1.50; ediff command frame auto-shrinks to 1 column wide Keith Rautenbach
2012-05-23 9:09 ` martin rudalics
2022-05-02 9:43 ` Lars Ingebrigtsen [this message]
2022-05-30 18:07 ` bug#11480: bug#11544: Subject: 24.1.50; ediff-buffers command window does not work properly Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2012-05-22 20:54 Munawar Cheema
2012-05-23 9:10 ` martin rudalics
[not found] ` <CADwNEa6EKG3nxAxnq7oN8Azfd28SBw52Cw7d0ENePuafkUjCqQ@mail.gmail.com>
2012-05-24 9:01 ` martin rudalics
2012-05-24 16:25 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8uo2rss.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11480@debbugs.gnu.org \
--cc=11544@debbugs.gnu.org \
--cc=krautenbach@ntlworld.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.