From: martin rudalics <rudalics@gmx.at>
To: David Phillips <dphillips@cfa.harvard.edu>
Cc: pillule@riseup.net, 50112@debbugs.gnu.org
Subject: bug#50112: 28.0.50; ediff help frame does not display text
Date: Fri, 20 Aug 2021 17:34:25 +0200 [thread overview]
Message-ID: <6870aaf2-64d2-d9af-a56d-d585e319946e@gmx.at> (raw)
In-Reply-To: <DD8ED695-9B41-4983-A989-0B8C66809517@cfa.harvard.edu>
> I do have two frames (and the help frame has no content). There is a
> buffer named *Ediff Control Panel* with the help text in it, but it
> isn’t displayed in the frame labeled Ediff. When I run ediff-buffers,
> hit ‘?’, switch back to the main frame, and evaluate the elisp you
> sent, I get ’nil’ in the mini buffer and the buffer *foo* has the help
> text in it. However, the help frame is still empty. I’m trying to
> understand what this means. It seems like the frame has the right
> buffer assigned to it but that it is in some weird mode so that it
> isn’t being rendered properly.
Is *Ediff Control Panel* the first line of *foo*? What does *Messages*
show? Here it contains the four lines
Buffer A: Processing difference region 0 of 1
Buffer B: Processing difference region 0 of 1
Processing difference regions ... done
#<buffer *Ediff Control Panel*>
martin
next prev parent reply other threads:[~2021-08-20 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 18:39 bug#50112: 28.0.50; ediff help frame does not display text David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-19 13:33 ` Lars Ingebrigtsen
2021-08-21 12:18 ` Alan Third
2021-08-21 12:54 ` Lars Ingebrigtsen
2021-08-21 13:20 ` David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-20 8:18 ` martin rudalics
2021-08-20 14:12 ` David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-20 15:34 ` martin rudalics [this message]
2021-08-20 15:44 ` David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=6870aaf2-64d2-d9af-a56d-d585e319946e@gmx.at \
--to=rudalics@gmx.at \
--cc=50112@debbugs.gnu.org \
--cc=dphillips@cfa.harvard.edu \
--cc=pillule@riseup.net \
/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).