From: Ihor Radchenko <yantar92@posteo.net>
To: "Tor-björn Claesson" <tclaesson@gmail.com>
Cc: Jonas Bernoulli <jonas@bernoul.li>, emacs-orgmode@gnu.org
Subject: Re: Org-cite: Replace basic follow-processor with transient menu?
Date: Tue, 29 Oct 2024 18:55:54 +0000 [thread overview]
Message-ID: <874j4ueo1x.fsf@localhost> (raw)
In-Reply-To: <CAO0k702FGLWna5ZYUbJ6nACRnkmAKQOSPO_aWmmh29+pBte4cA@mail.gmail.com>
Tor-björn Claesson <tclaesson@gmail.com> writes:
> ...
>> (mapcar (pcase-lambda (`(,key ,desc ,fn ,transform))
>> (list ,key ,desc
>> (lambda ()
>> (interactive)
>> (apply fn (eval transform)))))
>> org-cite-basic-follow-actions)))
>
> ...
> I will keep trying, but I must find the spare time to learn more about
> mapping and pattern matching in elisp, so this might take a while. In
> case Ihor wants to just fix it, please go ahead :-)
Check "11.4.4 Destructuring with ‘pcase’ Patterns" section of Elisp
manual. It has examples explaining how backquote pattern works.
> It would be good if we could match against the case of '(key desc
> suffix) as well, so that we could include otherwhere defined suffixes.
To not complicate things, I suggest something simple along the lines of
(lambda (&rest suffix-spec)
(pcase suffix-spec
(`(,key ,desc ,fn ,transform) ...)
(`(,key ,desc ,suffix) ...)))
Remember that you can always play around with things in scratch buffer,
in IELM, or even just using C-x C-e from anywhere:
(pcase '(1 2 3 4)
(`(,key ,desc ,fn ,transform)
(format "key: %s; desc: %s; fn:%s; transform: %s"
key desc fn transform))
(`(,key ,desc ,suffix)
(format "key: %s; desc: %s; suffix:%s"
key desc suffix)))
;; => "key: 1; desc: 2; fn:3; transform: 4"
(pcase '(1 2 3)
(`(,key ,desc ,fn ,transform)
(format "key: %s; desc: %s; fn:%s; transform: %s"
key desc fn transform))
(`(,key ,desc ,suffix)
(format "key: %s; desc: %s; suffix:%s"
key desc suffix)))
;; => "key: 1; desc: 2; suffix:3"
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-10-29 18:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 12:36 Org-cite: Replace basic follow-processor with transient menu? Tor-björn Claesson
2024-09-15 14:36 ` Ihor Radchenko
2024-09-17 12:18 ` Tor-björn Claesson
2024-09-22 12:50 ` Ihor Radchenko
2024-09-24 10:07 ` Tor-björn Claesson
2024-10-12 17:31 ` Ihor Radchenko
2024-10-22 7:23 ` Tor-björn Claesson
2024-10-22 17:58 ` Ihor Radchenko
2024-10-24 14:18 ` Jonas Bernoulli
2024-10-24 17:32 ` Ihor Radchenko
2024-10-26 11:45 ` Jonas Bernoulli
2024-10-27 8:09 ` Ihor Radchenko
2024-10-27 9:17 ` Tor-björn Claesson
2024-10-29 4:58 ` Tor-björn Claesson
2024-10-29 18:55 ` Ihor Radchenko [this message]
2024-10-30 5:37 ` Tor-björn Claesson
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874j4ueo1x.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jonas@bernoul.li \
--cc=tclaesson@gmail.com \
/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/org-mode.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).