Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Mats Löfdahl" <xyzzy@chello.se>
Subject: Re: IMAP drafts
Date: 22 Dec 2003 20:42:07 +0100	[thread overview]
Message-ID: <m3ekuwfxm8.fsf@1-1-1-8a.ras.sth.bostream.se> (raw)
In-Reply-To: <87ad5mgsdt.fsf@emptyhost.emptydomain.de>

Kai Grossjohann <kai@emptydomain.de> writes:

> Mats Löfdahl <xyzzy@chello.se> writes:
> 
> > Is there any way to get Gnus to store the drafts group on the IMAP
> > server? 
> 
> Drafts are stored using the Emacs autosave mechanism, which saves
> files, not messages.  One way to approach the problem would be to
> write a file handler (similar to Ange-FTP, say) that uses imap for
> storage.  Then the message buffers could have an appropriate
> autosave name and then everything would Just Work.

Of course, ange-ftp! It would not have to have anything to with
nnimap! The important thing is that the drafts directory is shared
between home and work.

So I could set nndraft-directory in my home .emacs to a tramp or
ange-ftp remote file name pointing to the drafts directory on my work
machine. Or I could set it on both those machines so it points to that
directory on a third machine, the one that hosts the imap server.

Would that work or would Gnus be confused if the contents of the
drafts directory changed between sessions? And would it be able to
handle Gnus being run on both machines at the same time?

-- 
Mats Löfdahl


       reply	other threads:[~2003-12-22 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3d6ai3273.fsf@1-1-1-8a.ras.sth.bostream.se>
     [not found] ` <87ad5mgsdt.fsf@emptyhost.emptydomain.de>
2003-12-22 19:42   ` Mats Löfdahl [this message]
2003-12-30  1:29   ` Lars Magne Ingebrigtsen

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=m3ekuwfxm8.fsf@1-1-1-8a.ras.sth.bostream.se \
    --to=xyzzy@chello.se \
    /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).