unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: jao <jao@gnu.org>
To: "Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 42483@debbugs.gnu.org
Subject: bug#42483: 26.1: thing-at-point doesn't recognize org-link urls
Date: Tue, 26 Jan 2021 00:29:56 +0000	[thread overview]
Message-ID: <87wnw08rqz.fsf@gnus.jao.io> (raw)
In-Reply-To: <87lfcgo9s2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 26 Jan 2021 00:51:25 +0100")

On Tue, Jan 26 2021, Lars Ingebrigtsen wrote:

> jao <jao@gnu.org> writes:
>
>> Excelent, thanks a lot.  I am not sure whether thing-at-point already
>> has that, but it'd then be useful to be able to retrieve, together with
>> the thing-at-point, its category (and even also have a thing/s/-at-point
>> returning all detected things).
>
> I'm not sure I follow you here -- you call thing at point with the
> category (or "thing", as thingatpt calls it) as the parameter:
>
> (thing-at-point 'url)
>
> thingatpt doesn't try to guess at what type of thing exists under point,
> just what the thing is.

yes.  i was imagining a convenience funtion, say `anything-at-point',
that would check in turn for possible things for me, and return, for
instance '(url . "http://www.gnu.org"). 

or perhaps simply having a function, say `things-at-point', returning
the list of symbols that denote possible things at point would be good
enough for the use case i'm imagining (dispatching actions on the thing
at point, whatever it is, based on its type).






  reply	other threads:[~2021-01-26  0:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  3:32 bug#42483: 26.1: thing-at-point doesn't recognize org-link urls Boruch Baum
2021-01-22 19:51 ` Lars Ingebrigtsen
2021-01-22 21:24   ` Jose A. Ortega Ruiz
2021-01-23 19:15     ` Lars Ingebrigtsen
2021-01-23 19:40       ` Lars Ingebrigtsen
2022-05-09 11:41         ` Lars Ingebrigtsen
2022-06-06 13:12           ` Lars Ingebrigtsen
2021-01-23 19:42       ` jao
2021-01-25 23:51         ` Lars Ingebrigtsen
2021-01-26  0:29           ` jao [this message]
2021-01-27  1:36             ` 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=87wnw08rqz.fsf@gnus.jao.io \
    --to=jao@gnu.org \
    --cc=42483@debbugs.gnu.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).