From: Jean Louis <bugs@gnu.support>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>,
Drew Adams <drew.adams@oracle.com>
Subject: Re: Any packages using ThingAtPointPlus for activation?
Date: Tue, 3 Jan 2023 16:10:53 +0300 [thread overview]
Message-ID: <Y7QpXRaMCmGuBveU@protected.localdomain> (raw)
In-Reply-To: <CADs++6jdqmpjoHNBWHBJbmrUM5Mz6awVLJQD+R6K5O40=EN9VA@mail.gmail.com>
* Eduardo Ochs <eduardoochs@gmail.com> [2023-01-03 09:17]:
> just one comment... `hyperscope-action-button' is written in a way
> that I don't like: it doesn't let us inspect what is the thing at
> point before doing something with the thing at point, and so it is
> hard to debug. I would factor it in at least two functions, and the
> lower-level one would be something like this, but I've omitted the
> case that tests for interned symbols...
>
> (defun ee-thing-at-point ()
> (cond ((thing-at-point 'symbol) (list 'symbol (thing-at-point 'symbol)))
> ((thing-at-point 'url) (list 'url (thing-at-point 'url)))
> ((thing-at-point 'email) (list 'email (thing-at-point 'email)))
> ((thing-at-point 'number) (list 'number (thing-at-point 'number)))
> ))
I accept the good idea. I would move into that soon anyway. This is
yet time of thinkering. It is all based on the concept of jumping to
various tings as it is already implemented in Hyperbole.
I wish to bypass Hyperbole, use things with priority myself, and let
the rest be handled by Hyperbole eventually.
Using M-RET is great thing as it is easily accessible action button as
demonstrated in Hyperbole.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2023-01-03 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 10:12 Any packages using ThingAtPointPlus for activation? Jean Louis
2023-01-02 17:08 ` [External] : " Drew Adams
2023-01-03 12:41 ` Jean Louis
2023-01-03 19:54 ` Drew Adams
2023-01-03 20:23 ` Jean Louis
2023-01-03 22:47 ` Drew Adams
2023-01-04 8:46 ` Jean Louis
2023-01-04 15:42 ` Drew Adams
2023-01-04 16:03 ` Eduardo Ochs
2023-01-05 5:42 ` Jean Louis
2023-01-05 8:37 ` ThingAtPointPlus, and extending things at point Jean Louis
2023-01-05 17:00 ` [External] : " Drew Adams
2023-01-06 15:49 ` Jean Louis
2023-01-06 16:23 ` Jean Louis
2023-01-06 17:30 ` Drew Adams
2023-01-06 17:43 ` Jean Louis
2023-01-06 18:21 ` Drew Adams
2023-01-03 6:16 ` Any packages using ThingAtPointPlus for activation? Eduardo Ochs
2023-01-03 13:10 ` Jean Louis [this message]
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=Y7QpXRaMCmGuBveU@protected.localdomain \
--to=bugs@gnu.support \
--cc=drew.adams@oracle.com \
--cc=eduardoochs@gmail.com \
--cc=help-gnu-emacs@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.
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).