From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: global-set-key with function taking arguments
Date: Sun, 1 Nov 2020 14:19:22 +0100 [thread overview]
Message-ID: <trinity-2901ec1e-abbb-4269-b3aa-6caf7c8813ab-1604236762683@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87h7q9xmim.fsf@zoho.eu>
> IMO proper functions (defuns) should be used with keys, not lambdas.
> Except for perhaps very simple or temporary solutions.
Agreed. For simple keybindings using a few lines of Emacs In-Built Commands,
using Anonymous Function is sensible, rather than having to make a 'defun'.
Anonymous Functions are especially when you see no reason why one would
normally call it. Because you may also document the Anonymous Function,
the 'lamdba' construct, Anonymous Functions become a pragmatic way of working.
Documentation for an Anonymous Function should have the same purpose as for a
'defun'. Conssequently, Documentation for an Anonymous Function should not
lack much from documentation of a 'defun'.
> Sent: Sunday, November 01, 2020 at 1:57 PM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: global-set-key with function taking arguments
>
> Christopher Dimech wrote:
>
> >> ... you mean `describe-function'?
> >
> > No. I mean describe-key. If you try describe-key for a key binding
> > you are not going to get useful documentation with an
> > anonymous function.
>
> Ah, that's what you mean. No, you are right, and I agree!
>
> > But I might be mistaken. May one include documentation string for
> > lambda ()?
>
> You can! But it doesn't work the same way. C-h f lambda RET
>
> (lambda ARGS [DOCSTRING] [INTERACTIVE] BODY)
>
> DOCSTRING is an optional documentation string.
> If present, it should describe how to call the function.
> But documentation strings are usually not useful in nameless functions.
>
> IMO proper functions (defuns) should be used with keys, not lambdas.
> Except for perhaps very simple or temporary solutions.
>
> Because functions are up in the sky - heaven, almost. And keys are by
> all means a way, one way, a good way, but not the _only_ way, to
> reach them. Functions shouldn't be imprisoned down there, at the same
> level as mere keys...
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2020-11-01 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 9:53 global-set-key with function taking arguments jai-bholeki via Users list for the GNU Emacs text editor
2020-11-01 10:57 ` William Xu
2020-11-01 11:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 11:47 ` Christopher Dimech
2020-11-01 12:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 12:28 ` Christopher Dimech
2020-11-01 12:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 13:19 ` Christopher Dimech [this message]
2020-11-01 13:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 14:08 ` Christopher Dimech
2020-11-01 14:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 23:38 ` Corwin Brust
2020-11-01 13:05 ` William Xu
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=trinity-2901ec1e-abbb-4269-b3aa-6caf7c8813ab-1604236762683@3c-app-mailcom-bs11 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).