branch: externals/transient commit 05801dcb545e88de4256309059385f7ab68fa40f Author: Jonas Bernoulli <jo...@bernoul.li> Commit: Jonas Bernoulli <jo...@bernoul.li>
manual: Fix inaccuracies in Suffix Specifications --- docs/transient.org | 6 ++---- docs/transient.texi | 5 ++--- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/transient.org b/docs/transient.org index 0410dedae5..227dc29434 100644 --- a/docs/transient.org +++ b/docs/transient.org @@ -1011,7 +1011,7 @@ suffixes”. Here it means the former. Suffix specifications have this form: #+begin_src emacs-lisp - ([LEVEL] [KEY] [DESCRIPTION] COMMAND|ARGUMENT [KEYWORD VALUE]...) + ([LEVEL] [KEY [DESCRIPTION]] COMMAND|ARGUMENT [KEYWORD VALUE]...) #+end_src {{{var(LEVEL)}}}, {{{var(KEY)}}} and {{{var(DESCRIPTION)}}} can also be specified using the {{{var(KEYWORD)}}}s @@ -1042,9 +1042,7 @@ argument that is mandatory in all cases. with it (as would be the case if ~transient-define-suffix~ or ~transient-define-infix~ were used to define it). - Anonymous, dynamically defined suffix commands are also supported. - See information about the ~:setup-children~ function in [[*Group - Specifications]]. + COMMAND can also be a ~lambda~ expression. As mentioned above, the object that is associated with a command can be used to set the default for certain values that otherwise have to diff --git a/docs/transient.texi b/docs/transient.texi index a83d837ce0..bc72121a43 100644 --- a/docs/transient.texi +++ b/docs/transient.texi @@ -1206,7 +1206,7 @@ suffixes”. Here it means the former. Suffix specifications have this form: @lisp -([LEVEL] [KEY] [DESCRIPTION] COMMAND|ARGUMENT [KEYWORD VALUE]...) +([LEVEL] [KEY [DESCRIPTION]] COMMAND|ARGUMENT [KEYWORD VALUE]...) @end lisp @var{LEVEL}, @var{KEY} and @var{DESCRIPTION} can also be specified using the @var{KEYWORD}s @@ -1244,8 +1244,7 @@ Any command will do; it does not need to have an object associated with it (as would be the case if @code{transient-define-suffix} or @code{transient-define-infix} were used to define it). -Anonymous, dynamically defined suffix commands are also supported. -See information about the @code{:setup-children} function in @ref{Group Specifications}. +COMMAND can also be a @code{lambda} expression. As mentioned above, the object that is associated with a command can be used to set the default for certain values that otherwise have to