From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Richard Stallman <rms@gnu.org>,
40213@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#40213: what-cursor-position could tell the meaning of marks too!
Date: Fri, 07 Aug 2020 02:33:42 +0300 [thread overview]
Message-ID: <87364z9wo9.fsf@mail.linkov.net> (raw)
In-Reply-To: <877ducgs82.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 06 Aug 2020 09:15:41 +0200")
>> If a mode puts some sort of special marker in a buffer, it can
>> put that text property on it.
>
> But that would be slow. The use case here is all the different
> characters used as markers in a Gnus Summary buffer -- and there may be
> tens of thousands of them. Making generation of these buffers (which is
> already slow) even slower, just to make it possible to these characters
> for their meaning, would be a disservice to the users.
Maybe then 'describe-char' could check if the mode's symbol has a special property
with a function name, and output a string returned from that function, e.g.
(put 'gnus-summary-mode 'describe-char 'gnus-summary-mode-describe-char)
Then 'describe-char' called in a gnus-summary-mode buffer will get the
function from its property, and 'gnus-summary-mode-describe-char' will
introspect its buffer and report information about the character
displayed at the given position and its meaning.
next prev parent reply other threads:[~2020-08-06 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 15:25 bug#40213: what-cursor-position could tell the meaning of marks too! 積丹尼 Dan Jacobson
2020-08-05 11:45 ` Lars Ingebrigtsen
2020-08-06 3:44 ` Richard Stallman
2020-08-06 7:15 ` Lars Ingebrigtsen
2020-08-06 23:33 ` Juri Linkov [this message]
2020-08-07 7:06 ` Lars Ingebrigtsen
2020-08-07 3:01 ` Richard Stallman
2020-08-07 7:07 ` Lars Ingebrigtsen
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=87364z9wo9.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=40213@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=rms@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).