From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Q: Stop "?" and "!" moving forward?
Date: 13 Feb 1996 19:50:22 +0100 [thread overview]
Message-ID: <w8s20nz5ac1.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: John Griffith's message of Tue, 13 Feb 1996 11:09:46 +0100
John Griffith <griffith@sfs.nphil.uni-tuebingen.de> writes:
> So shouldn't gnus-summary-tick-article be interactive like *-forward
> and *-backward? Otherwise I have to write something like
I've now made that function interactive.
> I was also thinking that if the non-movement versions of these
> commands were given numerical arguments, it would be nice if the next
> n articles were marked, but the current article stayed the same.
> Here's as near as I could come up with for dormant articles on short
> notice. (I hope it doesn't make anyone feel sick)
>
> (define-key gnus-summary-mode-map "?"
> (lambda (n) (interactive "p")
> (progn
> (gnus-summary-mark-as-dormant n)
> (previous-line n))))
(define-key gnus-summary-mode-map "?"
(lambda (n) (interactive "p")
(save-excursion
(gnus-summary-mark-as-dormant n))))
will do the trick. Perhaps you could put lots on non-moving ticking
commands (like this) on `M-C-?', `M-C-u', `M-C-d' (or wherever)? I
don't feel that things like this should go into the distribution,
though.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-02-13 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-12 13:46 John Griffith
1996-02-12 16:07 ` Kai Grossjohann
1996-02-13 10:09 ` John Griffith
1996-02-13 18:50 ` Lars Magne Ingebrigtsen [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=w8s20nz5ac1.fsf@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).