unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: "Tor-björn Claesson" <tclaesson@gmail.com>,
	emacs-devel@gnu.org, emacs-orgmode@gnu.org,
	"Philip Kaludercic" <philipk@posteo.net>,
	"Omar Antolín Camarena" <omar@matem.unam.mx>,
	"Jonas Bernoulli" <emacs.transient@jonas.bernoulli.dev>,
	"Juri Linkov" <juri@linkov.net>,
	karthikchikmagalur@gmail.com, Visuwesh <visuweshm@gmail.com>,
	charles.choi@yummymelon.com, "Justin Burkett" <justin@burkett.cc>
Subject: Re: [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark?
Date: Sat, 14 Dec 2024 09:59:59 +0000	[thread overview]
Message-ID: <87bjxefuu8.fsf@localhost> (raw)
In-Reply-To: <8734irb383.fsf@gmail.com>

Suhail Singh <suhailsingh247@gmail.com> writes:

>> For a given Emacs "prefix" command (e.g. org-open-at-point), we define a
>> set of customizations:
>>
>> 1. List of possible actions: ((name1 . action1 props) (name2 . action2 ...) ...)
>>    PROPS is a plist defining extra properties like key-binding, display
>>    string, maybe something else to be used in the future.
>> 2. Menu interface to use (transient, context-menu, embark, which-key)
>> 3. Layout settings for the specific interfaces. For example, transient
>>    layout definition.
>
> By "display string" do you mean a description of the action?  Or would
> that be additional?

I mean some way to define how the action should be displayed in the
menu. It may be a full string or just a description to be appended to
the action name, or something else.

> Hopefully, the description of each action will be a first-class member
> of the "List of possible actions".  Or is the intent that the
> description be taken from the form representing an action (e.g. a defun,
> a lambda etc).

Using a docstring sounds like a good idea. But it is a bit early to
decide these details. I'd like to discuss the more general design first.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
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>



  reply	other threads:[~2024-12-14  9:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8734m28l9a.fsf@gmail.com>
     [not found] ` <874j6h3rw8.fsf@localhost>
     [not found]   ` <877cbamq2q.fsf@gmail.com>
     [not found]     ` <87cykvrgwr.fsf@localhost>
     [not found]       ` <8734lpmkjn.fsf@gmail.com>
     [not found]         ` <87r08lqlbu.fsf@localhost>
     [not found]           ` <87a5ewfvo1.fsf@gmail.com>
2024-10-22 17:58             ` Org-cite: Replace basic follow-processor with transient menu? Ihor Radchenko
     [not found] ` <87wmhlmp83.fsf@gmail.com>
     [not found]   ` <871pzte929.fsf@localhost>
     [not found]     ` <87v7x548ri.fsf@gmail.com>
     [not found]       ` <87y120daue.fsf@localhost>
     [not found]         ` <874j4m9ep6.fsf@gmail.com>
     [not found]           ` <87h68gfqj1.fsf@localhost>
     [not found]             ` <CAO0k701CGFnQwCCuODjTFuf=OTsj9Vdqg+COP8nkpJg0wL_hQg@mail.gmail.com>
     [not found]               ` <87pln3f3cc.fsf@localhost>
     [not found]                 ` <CAO0k7006goK-AfhG+3PVwhz=4QU_DMm+5edmATZpjdRHkj61Bg@mail.gmail.com>
     [not found]                   ` <87jzd9ojj0.fsf@localhost>
     [not found]                     ` <87cyj0ajm9.fsf@gmail.com>
     [not found]                       ` <87zfm4s50x.fsf@localhost>
     [not found]                         ` <CAO0k703a5SCv4Eaogjs-14zgmTi-pK5qqG=8VzB8+7h-kcC8yg@mail.gmail.com>
     [not found]                           ` <87wmh8s358.fsf@localhost>
     [not found]                             ` <87y11nwp9z.fsf@gmail.com>
     [not found]                               ` <CAO0k702GsRi-h8BEY08kpf5FzMxi_MvRygNXJCyFnbtaC-a59w@mail.gmail.com>
     [not found]                                 ` <87v7wd9a2h.fsf@localhost>
     [not found]                                   ` <878qt7fbki.fsf@gmail.com>
     [not found]                                     ` <87o71jwdxz.fsf@localhost>
     [not found]                                       ` <87wmg6edr0.fsf@gmail.com>
2024-12-13 18:41                                         ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?) Ihor Radchenko
2024-12-13 22:09                                           ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? Gabriel Santos
2024-12-14  9:57                                             ` Ihor Radchenko
2024-12-14 10:59                                               ` Gabriel Santos
2024-12-14 13:10                                                 ` Ihor Radchenko
2024-12-13 22:57                                           ` Suhail Singh
2024-12-14  9:59                                             ` Ihor Radchenko [this message]
2024-12-14 14:30                                               ` Suhail Singh
2024-12-14  1:16                                           ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?) Panayotis Manganaris
2024-12-14 10:08                                             ` Ihor Radchenko
2024-12-14 10:50                                           ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? indieterminacy
2024-12-14  0:37 [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? (was: Fwd: Org-cite: Replace basic follow-processor with transient menu?) Psionic K
2024-12-14  9:48 ` Ihor Radchenko
2024-12-14 10:12   ` [RFC] The best way to choose an "action" at point: context-menu-mode, transient, which-key or embark? Philip Kaludercic

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=87bjxefuu8.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=charles.choi@yummymelon.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=emacs.transient@jonas.bernoulli.dev \
    --cc=juri@linkov.net \
    --cc=justin@burkett.cc \
    --cc=karthikchikmagalur@gmail.com \
    --cc=omar@matem.unam.mx \
    --cc=philipk@posteo.net \
    --cc=suhailsingh247@gmail.com \
    --cc=tclaesson@gmail.com \
    --cc=visuweshm@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.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).