Gnus development mailing list
 help / color / mirror / Atom feed
From: George McNinch <gmcninch@gmail.com>
To: ding@gnus.org
Subject: Re: gmail and gnus-summary-move-article
Date: Sat, 06 Feb 2016 13:33:39 -0500	[thread overview]
Message-ID: <82k2mhn0xo.fsf@jobim-via-gmail.com> (raw)
In-Reply-To: <87zivd6h73.fsf@ericabrahamsen.net>

>> 
>>> Well, you could write a function that calls those two 
>>> functions. :-) 
>>  Right... After writing this, I think I had decided to do 
>>  that. But I 
>> realized that I'm not sure I understand how to 
>> recognize/interact with the process marks, though I confess I 
>> really only had a quick look.  Then I got distracted.  Looking 
>> again, I recall noting that gnus-summary-mark-as-expirable 
>> doesn't interact with the process marks, as-is. (Well, outside 
>> of my perhaps odd-ball proposed usage, there is no reason it 
>> should...) 
 
> Expiration won't actually delete a Gmail message, unless the 
> expiry process moves the message to Trash. 

That was exactly what I proposed in my original post, though.

(

>In fact, the usual way I "delete" articles in the gmail account 
>is via expiration: I mark them with E in the summary buffer, and 
>I have a gnus-parameters setting for those accounts which sets  
>      (expiry-target . "nnimap+personal:[Gmail]/Trash") 
> So when I expire articles, they get moved to the "gmail trash", 
>and then gmail regularly prunes its Trash folder without further 
>intervention. 


) 
 
 

-- 
George McNinch http://gmcninch.math.tufts.edu 
oOoOoOoOoOoOoOoOoOoOoOoOoOoOoO




  reply	other threads:[~2016-02-06 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 20:36 George McNinch
2016-02-06  6:45 ` Lars Ingebrigtsen
2016-02-06 13:39   ` George McNinch
2016-02-06 14:34     ` Eric Abrahamsen
2016-02-06 18:33       ` George McNinch [this message]
2016-02-07  2:02         ` Eric Abrahamsen

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=82k2mhn0xo.fsf@jobim-via-gmail.com \
    --to=gmcninch@gmail.com \
    --cc=ding@gnus.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).