From: "Daniel Martín" <mardani29@yahoo.es>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Show show-paren context in a child frame
Date: Sat, 05 Feb 2022 19:00:49 +0100 [thread overview]
Message-ID: <m1zgn5gpm6.fsf@yahoo.es> (raw)
In-Reply-To: <87fsoxlc2p.fsf@gnu.org> (Tassilo Horn's message of "Sat, 05 Feb 2022 13:33:22 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> Hi all,
>
> today I've discovered `show-paren-context-when-offscreen' which displays
> the context around the opening paren in the echo area. That's a very
> nice feature, however it competes with eldoc, i.e., it'll show the
> context in the echo area and a fraction of a second later, that's
> repressed by eldoc's text (or the other way round depending on the
> delays one uses).
I'm glad you like the feature! Yes, unfortunately there are some cases
where this feature competes with Eldoc. I taught
`eldoc-display-message-no-interference-p' about this new option, but
perhaphs the mechanism needs some more refinement.
>
> Therefore, I've experimented with adding a special `child-frame' value
> for `show-paren-context-when-offscreen' which displays the context in a
> child frame. This works pretty well although setting up a child frame
> with corresponding buffer for a kind of tooltip pane requires quite some
> gymnastics in frame parameters and buffer-local variables which I've
> copied from vertico. Comments welcome!
Thank you! I've given your code a try and I think it can be a useful
option. Some comments:
- Is there a way to make the header more prominent? I feel it can be
easily confused with the rest of the buffer. Perhaps putting a thin
border around the child frame might be enough.
- I've found an error when I clicked on the child frame by mistake and
scrolled (I wanted to scroll the parent frame instead):
mouse-scroll-subr: Wrong type argument: window-live-p, #<window 386> [30
times]
Not sure if it's a bug in the child frame API or in the way you use it;
I'm not familiar enough with the child frame API.
- The way the child frame is positioned makes me think that using the
header line would be more reliable and imply much less code than using
a child frame. I'd like to give a header line-based approach a try to
see how it compares against using a child frame. To make it a good
citizen, we need to store the current contents of the header line and
restore them when the point is not in a closing delimiter.
next prev parent reply other threads:[~2022-02-05 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 12:33 Show show-paren context in a child frame Tassilo Horn
2022-02-05 18:00 ` Daniel Martín [this message]
2022-02-05 19:03 ` Tassilo Horn
2022-02-05 20:06 ` Tassilo Horn
2022-02-06 10:18 ` Tassilo Horn
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=m1zgn5gpm6.fsf@yahoo.es \
--to=mardani29@yahoo.es \
--cc=emacs-devel@gnu.org \
--cc=tsdh@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.
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).