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 12:47:35 +0100 [thread overview]
Message-ID: <trinity-f18d23f1-3245-4e14-905a-a97117cc2922-1604231255628@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87r1pdxqey.fsf@zoho.eu>
It looks to me that it is much better to define your own function so then you can use
describe-key. But I have not checked it.
> Sent: Sunday, November 01, 2020 at 12:33 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
>
> William Xu wrote:
>
> > You could define a macro wraper around:
> >
> > (defmacro my-make-interactive (&rest body)
> > `(lambda ()
> > (interactive)
> > (progn ,@body)))
> >
> > (global-set-key (kbd "C-H-<up>") (my-make-interactive (transpose-paragraphs -1)))
>
> Well, maybe you could, but what would you gain from that?
>
> Better to either use `lambda' or define your own function.
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2020-11-01 11:47 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 [this message]
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
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-f18d23f1-3245-4e14-905a-a97117cc2922-1604231255628@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).