From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 40213@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#40213: what-cursor-position could tell the meaning of marks too!
Date: Wed, 05 Aug 2020 23:44:47 -0400 [thread overview]
Message-ID: <E1k3Wpj-00051w-5v@fencepost.gnu.org> (raw)
In-Reply-To: <877dud9uzh.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 05 Aug 2020 13:45:38 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > No worry, C-u C-x = (what-cursor-position) will tell you:
> >
> > There are text properties here:
> > face gnus-summary-high-unread
> > gnus-number 31074
> >
> > Ahhh... alas it could tell you more!
> I think that's pretty much impossible -- there's no infrastructure in
> Emacs to have it tell you what a random character in a generated buffer
> means. And adding a bunch of text properties everywhere just in case
> you wonder would be impractically slow.
Here's a way that is trivially easy to implement, and won't be slow.
Invent a new text property: 'significance'. If the character
has that property, its value should be a string which explains
what the character "means" in that particular case.
If a mode puts some sort of special marker in a buffer, it can
put that text property on it.
This is trivial to implement because it requires no code.
C-u C-x = will display the text property anyway ;-}.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-08-06 3:44 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 [this message]
2020-08-06 7:15 ` Lars Ingebrigtsen
2020-08-06 23:33 ` Juri Linkov
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=E1k3Wpj-00051w-5v@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=40213@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.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).