Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: binding a summary key to *two* commands
Date: Thu, 22 Jan 2015 23:53:49 +0100	[thread overview]
Message-ID: <87mw5abf5u.fsf@debian.uxu> (raw)
In-Reply-To: <8xxvbk094tf.fsf@village.keycorner.org>

Hikaru Ichijyo <ichijyo@macross.sdf.jp> writes:

> Ok, the function I was trying to make, debugged, in
> case anyone wants it.

That's exactly right!

1. Write a defun that is (interactive).

2. Stack the commands as you have been using them up
   to today.

3. Use the help for each command or compile the Elisp
   to learn if some command is available in some
   other, better form.

4. Re-bind the old key to your new defun.

Plain and simple. Sometimes...

-- 
underground experts united

      reply	other threads:[~2015-01-22 22:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 17:54 Hikaru Ichijyo
2015-01-20 18:08 ` Adam Sjøgren
     [not found] ` <mailman.18212.1421777358.1147.info-gnus-english@gnu.org>
2015-01-20 22:11   ` Hikaru Ichijyo
2015-01-21  3:43   ` Hikaru Ichijyo
2015-01-22 22:53     ` Emanuel Berg [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mw5abf5u.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@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 NNTP newsgroup(s).