Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: archiving threads one contributes to
Date: Wed, 23 Jul 2014 16:25:04 +0200	[thread overview]
Message-ID: <878unk9mpr.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.5889.1406097766.1147.info-gnus-english@gnu.org>

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> My problem is twofolds: how do I make sure that the
> files corresponding to threads I've replied to remain
> on my hard drive, while other files may be cleared at
> some point

You mean, you will delete the other files manually?

> and how do I integrate these file to my mail search
> infrastructure (which is using notmuch).

I have no experience of notmuch, but perhaps it can
sort your mails in directories based on threads?

> Copying the articles into a mailbox seems to be the
> most straightforward way to solve both issues, I just
> don't know how to do it automatically.

Well, I don't see why you would want to delete any
files to begin with - just lots of extra work, it seems
to me, for no obvious advantage (?).

If there isn't any Gnus library or other software that
will help you with this, you'll have to record the
subjects and message IDs of the posts you send.

As in:

(defun save-sent-msg-data ()
  ; save Message ID and Subject to a file
  ; (I don't know if the Message ID is available at
  ;  this point - ?)
)
(add-hook 'message-sent-hook 'save-sent-msg-data)

Then, when you delete the unwanted messages, don't
delete any that has a Subject that is listed in that
file, or if any of your Message IDs is in the
References header.

Or, when you receive a post, do a corresponding check
and, as you say, send it to a group.

But this seems a bit sketchy so I recommend looking
around if there isn't a time tested solution
around... again, if you really feel you must delete the
other files that is!

-- 
underground experts united

  parent reply	other threads:[~2014-07-23 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5872.1406046569.1147.info-gnus-english@gnu.org>
2014-07-22 17:51 ` John Hasler
2014-07-22 18:39   ` Alan Schmitt
     [not found]   ` <mailman.5875.1406054409.1147.info-gnus-english@gnu.org>
2014-07-22 20:38     ` Emanuel Berg
2014-07-23  6:42       ` Alan Schmitt
     [not found]       ` <mailman.5889.1406097766.1147.info-gnus-english@gnu.org>
2014-07-23 14:25         ` Emanuel Berg [this message]
2014-07-23 14:51           ` Alan Schmitt
     [not found]           ` <mailman.5906.1406127108.1147.info-gnus-english@gnu.org>
2014-07-23 15:16             ` Emanuel Berg
2014-07-23 17:36               ` Alan Schmitt
     [not found]               ` <mailman.5920.1406137007.1147.info-gnus-english@gnu.org>
2014-07-23 18:25                 ` Emanuel Berg
2014-07-23 18:52                   ` Alan Schmitt
2014-07-22 16:28 Alan Schmitt

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=878unk9mpr.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.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).