From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: gnus & (windmove-default-keybindings)
Date: Sat, 5 Dec 2015 13:38:34 +0000 [thread overview]
Message-ID: <87vb8d3tid.fsf@ucl.ac.uk> (raw)
In-Reply-To: <5662A3E4.3010606@niwas.net> (Dave's message of "Sat, 5 Dec 2015 00:44:20 -0800")
On Saturday, 5 Dec 2015 at 00:44, Dave wrote:
>> I've turned on:
>>
>
>> (windmove-default-keybindings 'meta)
>>
>> which allows sane keys for moving between windows (M-<up>, M-<dn>,
>> M-<rt>, M-<lft>). All works well, except for the article summary buffer
>> in Gnus, which treats M-<up> and M-<dn> as <up> and <dn>. (Though
>> M-<rt> and M-<lft> behave properly.)
>
> I should add that the command (windmove-down) works fine. It's just the
> bound key that fails. Additionally, using global-set-key to
> specifically set the binding also fails.
>
>> Can anyone give me some pointers of how to proceed?
You could set up a hook for the individual gnus views (group, summary)
to bind M-<up> and M-<down> to the corresponding windmove commands,
along the lines of
#+begin_src emacs-lisp
;; From: pmlists@free.fr (Peter Münster)
;; Newsgroups: gnu.emacs.gnus
;; Message-ID: <87lj1wkv2q.fsf@micropit.couberia.bzh>
(defun esf/alter-summary-map ()
(local-set-key ":" 'bbdb-mua-display-records)
(local-set-key "d" 'gnus-summary-delete-article)
(local-set-key "e" 'gnus-summary-mark-as-expirable)
(local-set-key "u" 'gnus-summary-put-mark-as-unread) ;-next-unread
(local-set-key "w" 'gnus-article-fill-long-lines)
)
(add-hook 'gnus-summary-mode-hook 'esf/alter-summary-map)
#+end_src
HTH,
eric
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.2 + Ma Gnus v0.14 + evil-git-ff74cfb
: BBDB version 3.1.2 (2014-04-28 23:20:47+00:00)
next prev parent reply other threads:[~2015-12-05 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 8:31 Dave
2015-12-05 8:44 ` Dave
2015-12-05 13:38 ` Eric S Fraga [this message]
2015-12-10 8:40 ` Dave
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=87vb8d3tid.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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).