Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "Daniel Hernández" <daniel@degu.cl>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] deleting files from source
Date: Wed, 20 Oct 2010 11:17:11 -0300	[thread overview]
Message-ID: <1287582761-sup-3447@maullin> (raw)
In-Reply-To: <op.vkuz1znr0495wc@localhost>

Excerpts from Chris Parsons's message of Wed Oct 20 02:26:13 -0300 2010:
> On Tue, 19 Oct 2010 02:52:54 +0100, Daniel Hernández <daniel@degu.cl>  
> wrote:
> 
> > I started using sup recently. Now I have only one source that is a
> > inbox maildir folder. I want to delete some emails from the source
> > forever, but when I delete or kill emails they are not really deleted
> > from the maildir folder. How can I clean the maildir folder, removing
> > deleted or killed emails?
> 
> The design intent of sup is to specifically remove the need to worry about  
> deleting e-mails. But if you really need to do that then one way might be  
> to do the following (assuming your machine has the right tools installed).  
> Doing stuff like this could lose your messages. Info supplied for  
> education purposes only. Proceed at your own risk!

The reason because I need to delete some emails is that I read emails
in several computers. In each computer I have sup installed and I
synchronize the maildir with other maildirs using a primary imap
server. Thus I like to delete some unimportant emails to reduce the
network traffic.

I started with this practice using mutt and the wanderlust email
client, but I prefer the sup email client. I like the tagging system
of sup and its capacity to manage threads. But now I have another
problem, because tags are not stored in the maildir and I don't know
how to synchronize tags in several computers.
 
> # change to top of the Maildir
>    cd ~/Mail
> # get message id of all files with tag 'deleted' and put in temp file
>    FL=/tmp/del-filelist
>    rm -f $FL
>    for i in `sup-dump | grep deleted | cut -f 1 -d' '`; do grep -l -r $i  
> ./*  >> $FL;done
> # delete the files in the file list
>    for i in `cat $FL`; do rm $i; done
> # sync the index. New versions of sup-sync don't have the --changed  
> argument
>    sup-sync --verbose --changed
> 
> repeat for "killed" instead of "deleted"

That works fine, but I have written some modifications because my
maildir don't store emails using the message-id.

Thanks,
Daniel
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-10-20 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  1:52 Daniel Hernández
2010-10-19 11:31 ` Daniel Hernández
2010-10-19 12:18   ` Pedro F. «pancho» Horrillo
2010-10-20  5:26 ` Chris Parsons
2010-10-20 14:17   ` Daniel Hernández [this message]
2010-10-20 15:11     ` Helge Titlestad
2010-10-21 18:11 ` Hamish D
2010-10-24 10:52 ` Alexander Ulrich
2010-10-24 20:11   ` Damien Leone
2010-12-15  7:57     ` Matthias Vallentin
2010-12-15 11:53       ` Damien Leone
2010-12-18  4:09         ` Matthias Vallentin

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=1287582761-sup-3447@maullin \
    --to=daniel@degu.cl \
    --cc=sup-talk@rubyforge.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