gnus-summary-catchup-and-exit-AND-mark-as-expirable

gnus-summary-catchup-and-exit-AND-mark-as-expirable

[jidanni]

c runs the command gnus-summary-catchup-and-exit
E runs the command gnus-summary-mark-as-expirable
OK, but what if sometimes one wants c to also mark them all as E too?
There ought to be a binding...
For now one can only go to the top of the summary, hold down the E key
for a few seconds, then press c.

Re: gnus-summary-catchup-and-exit-AND-mark-as-expirable

[Adam Sjøgren]

On Tue, 03 Aug 2010 07:14:52 +0800, jidanni@jidanni.org wrote:

> c runs the command gnus-summary-catchup-and-exit
> E runs the command gnus-summary-mark-as-expirable
> OK, but what if sometimes one wants c to also mark them all as E too?
> There ought to be a binding...

What binding do you propose?


  Best regards,

-- 
 "The laws of perspective have been repealed!                 Adam Sjøgren
  Objects no longer diminish in size with distance!"     asjo@koldfront.dk

Re: gnus-summary-catchup-and-exit-AND-mark-as-expirable

[Ted Zlatanov]

On Tue, 03 Aug 2010 07:14:52 +0800 jidanni@jidanni.org wrote: 

j> c runs the command gnus-summary-catchup-and-exit
j> E runs the command gnus-summary-mark-as-expirable
j> OK, but what if sometimes one wants c to also mark them all as E too?
j> There ought to be a binding...
j> For now one can only go to the top of the summary, hold down the E key
j> for a few seconds, then press c.

There's auto-expire.  So you're saying you want its effect sometimes
after you've read a group?  It seems like something you should set once
per group and never worry about again.  What kind of groups would you
want to auto-expire only sometimes?  I can't think of any so I am not
eager to put such a binding into Gnus, but perhaps I'm not seeing it.

Ted

Re: gnus-summary-catchup-and-exit-AND-mark-as-expirable

[jidanni]

>What binding do you propose?
I'll leave that to the pros.

TZ> There's auto-expire.  So you're saying you want its effect sometimes
TZ> after you've read a group?  It seems like something you should set once
TZ> per group and never worry about again.  What kind of groups would you
TZ> want to auto-expire only sometimes?  I can't think of any so I am not
TZ> eager to put such a binding into Gnus, but perhaps I'm not seeing it.

OK, it's those nnrss groups. There the ones that actually leave messages
on my disk. But I don't always want to expire them all the same way or
always the same way...

Re: gnus-summary-catchup-and-exit-AND-mark-as-expirable

[Ted Zlatanov]

On Fri, 06 Aug 2010 11:53:14 +0800 jidanni@jidanni.org wrote: 

>> What binding do you propose?
j> I'll leave that to the pros.

TZ> There's auto-expire.  So you're saying you want its effect sometimes
TZ> after you've read a group?  It seems like something you should set once
TZ> per group and never worry about again.  What kind of groups would you
TZ> want to auto-expire only sometimes?  I can't think of any so I am not
TZ> eager to put such a binding into Gnus, but perhaps I'm not seeing it.

j> OK, it's those nnrss groups. There the ones that actually leave messages
j> on my disk. But I don't always want to expire them all the same way or
j> always the same way...

I think making this keybinding generally available will confuse users
who also look at total-expire and auto-expire (those two are confusing
enough alone).  It's easy to write it yourself as a macro or a
function.  I could be wrong, but I need at least one more vote in favor
of this feature to know I'm wrong :)

Ted