unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: Setting keybinding for org-support-shift-select t
Date: Sun, 4 Oct 2020 07:40:18 -0500	[thread overview]
Message-ID: <20201004124018.GA292110@scrozzle> (raw)
In-Reply-To: <trinity-ea55b089-9c61-4365-a6e3-aebaea91e021-1601814327180@3c-app-mailcom-bs04>

On 2020-10-04 at 14:25:27 +0200,
Christopher Dimech <dimech@gmx.com> wrote:

> A problem I am encountering with keybindings is that I end up with
> very strange key combinations. I rather type a key followed by a
> string as is done in Emacs such as "M-x org-mode". Is there an
> relatively easy way to do this for one's own operations?

The same way Emacs does it:  define your function as interactive, e.g.:

    (defun scroll-up-1-line () "Scroll up one line."
      (interactive) (scroll-up 1))

interactive can handle functions that take parameters, too, and will
prompt you when you execute the function with M-x.  It can also
interpret C-u and other numeric prefixes.



  reply	other threads:[~2020-10-04 12:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-04 10:55 Setting keybinding for org-support-shift-select t Christopher Dimech
2020-10-04 11:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 11:31   ` Christopher Dimech
2020-10-04 11:49     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 11:52       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 12:25         ` Christopher Dimech
2020-10-04 12:40           ` 2QdxY4RzWzUUiLuE [this message]
2020-10-04 12:54             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 14:03             ` Christopher Dimech
2020-10-04 15:02               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 16:19                 ` Christopher Dimech
2020-10-04 18:57                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 19:26                     ` Christopher Dimech
2020-10-04 19:34                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 16:57                 ` Christopher Dimech
2020-10-04 17:08                   ` Drew Adams
2020-10-04 17:36                     ` Christopher Dimech
2020-10-04 17:52                       ` Drew Adams
2020-10-04 18:10                         ` Christopher Dimech
2020-10-04 19:00                           ` Drew Adams
2020-10-05  3:55                             ` Christopher Dimech
2020-10-05  4:12                               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 19:16                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 19:10                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 12:48           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 11:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 12:14   ` Christopher Dimech

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=20201004124018.GA292110@scrozzle \
    --to=2qdxy4rzwzuuilue@potatochowder.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).