all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
	Christopher Howard <christopher@librehacker.com>
Cc: 74673@debbugs.gnu.org
Subject: bug#74673: 30.0.92; face warning on legal elisp syntax
Date: Wed, 4 Dec 2024 09:51:59 -0800	[thread overview]
Message-ID: <f7af52ef-9e2a-07e7-4157-4968ddeff914@gmail.com> (raw)
In-Reply-To: <86bjxr1vtf.fsf@gnu.org>

On 12/4/2024 4:23 AM, Eli Zaretskii wrote:
> If you really need to be able to show tool tips without the mouse, you
> can write a simple function to show its text in the echo-area.
> However, most tooltips are shown on UI parts where you cannot go, so
> such a command will be of somewhat limited use.

Flymake has an option for displaying diagnostic messages in-line: 
'flymake-show-diagnostics-at-end-of-line'. Maybe we could make Elisp 
mode use Flymake's facilities for marking the warning when it's active?





  parent reply	other threads:[~2024-12-04 17:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 18:49 bug#74673: 30.0.92; face warning on legal elisp syntax Christopher Howard
2024-12-03 19:02 ` Eli Zaretskii
2024-12-03 19:19   ` Christopher Howard
2024-12-03 19:38     ` Eli Zaretskii
2024-12-03 20:48       ` Christopher Howard
2024-12-04 12:23         ` Eli Zaretskii
2024-12-04 17:12           ` Kévin Le Gouguec
2024-12-04 17:32             ` Eli Zaretskii
2024-12-05  9:28               ` Robert Pluim
2024-12-05  9:53                 ` Eli Zaretskii
2024-12-05 10:06                   ` Robert Pluim
2024-12-04 17:51           ` Jim Porter [this message]
2024-12-04 18:55             ` Eli Zaretskii
2024-12-06  4:46         ` Richard Stallman
2024-12-06  8:26           ` Eli Zaretskii
2024-12-12 17:20             ` Christopher Howard
2024-12-12 19:04               ` Eli Zaretskii
2024-12-04 15:42 ` Christopher Howard

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=f7af52ef-9e2a-07e7-4157-4968ddeff914@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=74673@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    --cc=eliz@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 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.