From: Michael Piotrowski <mxp@dynalabs.de>
To: info-gnus-english@gnu.org
Subject: Re: Marking an article as read without moving
Date: Thu, 02 Aug 2007 12:34:47 +0200 [thread overview]
Message-ID: <x6ps26z0l4.fsf@dynalabs.de> (raw)
In-Reply-To: <m3zm1h8g0z.fsf@robolove.meer.net>
On 2007-07-28, Madhu <enometh@meer.net> wrote:
> | How about setting the `gnus-summary-goto-unread' variable to nil?
>
> Thanks, this helps some but really I'd like to be able to invoke both
> behaviours at any point. Some times I want to jump to the next or
> previous unread article. Other times I just want to operate on the
> current article and stay where I am [like saving to mbox or RMAIL does
> not automatically move to the next article --- where I `user-expect' it
> to `move to next' :)] I found the structure of the browsing code makes
> the desired behaviour surprisingly hard to achieve.
I've got this in my .gnus:
--8<---------------cut here---------------start------------->8---
;; A keybinding for marking messages as read in the summary buffer
;; without moving
(define-key gnus-summary-mode-map [(meta d)]
(lambda () (interactive) (gnus-summary-mark-as-read)))
--8<---------------cut here---------------end--------------->8---
Is that what you're looking for?
Greetings
--
Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)
prev parent reply other threads:[~2007-08-02 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3ejjn16xk.fsf@robolove.meer.net>
2007-07-05 10:42 ` Katsumi Yamaoka
[not found] ` <m3zm1h8g0z.fsf@robolove.meer.net>
2007-08-02 10:34 ` Michael Piotrowski [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=x6ps26z0l4.fsf@dynalabs.de \
--to=mxp@dynalabs.de \
--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).