all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 40213@debbugs.gnu.org
Subject: bug#40213: what-cursor-position could tell the meaning of marks too!
Date: Wed, 05 Aug 2020 13:45:38 +0200	[thread overview]
Message-ID: <877dud9uzh.fsf@gnus.org> (raw)
In-Reply-To: <87v9mtn5as.5.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Tue, 24 Mar 2020 23:25:31 +0800")

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> It's one of those days. You see those marks "+", "A+" in the Summary
> Buffer,
>
>   + 1 200306 16|      |台電資訊處            :RE: Fartsworth Affair
>     1 200324 39|      |John (John Lewddis)   :[Maniphest] [Closed] T99999: Can not do any thing
>  A+ 1 200324 24|      |cclin                 :Re: Ants in pants
>
> but are too lazy to look up what they mean (in (info "(gnus) Other
> Marks") etc.).
>
> 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.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-05 11:45 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 [this message]
2020-08-06  3:44   ` Richard Stallman
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dud9uzh.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=40213@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.