Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ecocode <eco@ecocode.net>
Cc: ding@gnus.org
Subject: Re: gnus-summary-mark-thread-as-expirable
Date: Thu, 27 Sep 2007 05:56:07 -0500	[thread overview]
Message-ID: <m2abr8js1k.fsf@lifelogs.com> (raw)
In-Reply-To: <m2wsucwsr3.fsf@flatsoft.no-ip.info> (ecocode's message of "Thu, 27 Sep 2007 08:02:24 +0200")

On Thu, 27 Sep 2007 08:02:24 +0200 ecocode <eco@ecocode.net> wrote: 

e> * Ted Zlatanov <tzz@lifelogs.com> wrote:
e> |
e> | I would have done it but don't know what's a good value for the prefix
e> | argument to use as a trigger.  Any suggestions?  0 perhaps?

e> What about T E ?

Sorry for responding in Lisp-speak :)

`T E' is the key shortcut you'd like.  What I mean is that
gnus-summary-kill-thread has a prefix argument (it's mapped by default
to `T k'; you press C-u then type a number, then hit `T k' to give that
number to gnus-summary-kill-thread as the prefix argument).  If you
don't pass that number, the prefix argument is null.  This is standard
Emacs behavior and a lot of functions take a prefix argument.

I added an extra option to gnus-summary-kill-thread which is almost
 exactly like the regular null-prefix behavior, but used
 gnus-expirable-mark instead of gnus-killed-mark.  To use it, you don't
 have to play with universal prefixes, just do the following:

1) get latest Gnus from CVS

2) hit `M-C-e' or `T e' on a thread to mark the whole thing expirable.
I used `T e' because `T k' is mapped to gnus-summary-kill-thread and I
wanted to be consistent.

3) if you like the behavior, you can map that to a key by itself, say
C-e:

(define-key gnus-summary-mode-map "\C-e" 'gnus-summary-expire-thread)

Please test and let me know if this works for you.  My testing showed no
problems.  I'll document it once testing is done.

Ted



  reply	other threads:[~2007-09-27 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  7:15 gnus-summary-mark-thread-as-expirable ecocode
2007-09-26 17:27 ` gnus-summary-mark-thread-as-expirable David Z Maze
2007-09-26 21:47 ` gnus-summary-mark-thread-as-expirable Ted Zlatanov
2007-09-27  6:02   ` gnus-summary-mark-thread-as-expirable ecocode
2007-09-27 10:56     ` Ted Zlatanov [this message]
2007-09-27 18:51       ` gnus-summary-mark-thread-as-expirable Reiner Steib
2007-09-27 19:52         ` gnus-summary-mark-thread-as-expirable Ted Zlatanov
2007-09-27 21:01           ` gnus-summary-mark-thread-as-expirable David Z Maze
2007-09-27 21:07           ` gnus-summary-mark-thread-as-expirable Reiner Steib

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=m2abr8js1k.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=eco@ecocode.net \
    /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).