Gnus development mailing list
 help / color / mirror / Atom feed
From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Cc: griffith@filippo.sfs.nphil.uni-tuebingen.de
Subject: Re: Q: Stop "?" and "!" moving forward?
Date: Tue, 13 Feb 1996 11:09:46 +0100	[thread overview]
Message-ID: <199602131009.LAA01349@filippo.sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Your message of "12 Feb 1996 17:07:59 +0100." <vafka1sa5nk.fsf@dusty.informatik.uni-dortmund.de>


Kai Grossjohann writes:
>>>>>> <griffith@sfs.nphil.uni-tuebingen.de> said:
>
>  John> Is there a variable to set to stop ticking and marking
>  John> articles as dormant ("!" and "?") from moving to the next
>  John> article?
>
>You want to execute gnus-summary-tick-article rather than
>gnus-summary-tick-article-forward.  ! is by default bound to
>*-forward.
>
>Try this to change the binding:
>
>(define-key gnus-summary-mode-map "!" 'gnus-summary-tick-article)

This almost works except that gnus-summary-tick-article is not
interactive so I get the error 
   "Wrong type argument: commandp, gnus-summary-tick-article"

So shouldn't gnus-summary-tick-article be interactive like *-forward
and *-backward?  Otherwise I have to write something like

(define-key gnus-summary-mode-map "!"
  (lambda (n) (interactive "p") (gnus-summary-tick-article)))

Also, for dormant articles, there is only one command,
gnus-summary-mark-as-dormant.  Maybe there should also be
gnus-summary-mark-as-dormant-forward and
gnus-summary-mark-as-dormant-backward, with *-forward as the default
for "?".

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))))

I'm sure that using previous-line here is a bad idea but I'm not sure
what's the correct function.


  reply	other threads:[~1996-02-13 10:09 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 [this message]
1996-02-13 18:50     ` Lars Magne Ingebrigtsen

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=199602131009.LAA01349@filippo.sfs.nphil.uni-tuebingen.de \
    --to=griffith@sfs.nphil.uni-tuebingen.de \
    --cc=griffith@filippo.sfs.nphil.uni-tuebingen.de \
    /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).