Gnus development mailing list
 help / color / mirror / Atom feed
From: Ian Swainson <ian@qui-oui.com>
Subject: Palm and Gnus
Date: Thu, 13 Sep 2001 15:12:57 +0100	[thread overview]
Message-ID: <ug09rch7a.fsf@qui-oui.com> (raw)

Hi All,

I've had no response to queries about syncing Gnus and the Palm, so I'm going to
have a go at writing something to do it myself. I'd be grateful if someone could
answer a couple of questions about the Gnus side of things.

I am a complete amateur C and lisp programmer, so please bear with me.

Basically, the functionality I want is for all unread messages for any group at
the time of synchronisation to be sent to the Palm, and marked as read when they
are read on the Palm and synchronisation occurs, and vice-versa (marked as read
on the Palm if they were transferred there but were then read in Gnus).
Any mail composed on the Palm is sent via Gnus, and a copy kept in the relevant
Gnus folder.

So, my technique, I reckon is as follows:
1. I'm going to use pilot-link's pilot-mail as a starting point
2. At synchronisation I'll need to loop thru each nnml group and check the
.newsrc file for the filename of the mail (where is the code in Gnus that does
this?) to see what has been read already. I'll need also to check what is on the
Palm already to make sure I avoid duplicates.
3. Mark all messages that are read on the Palm as read in Gnus (by adding the
filenumber to the .newsrc file)? Will this affect the expiry rules?
4. Mark any messages read in Gnus and transferred to the Palm previously as read
on the Palm
5. Finally get any mails composed on the Palm and ... where can I put the mails
so that Gnus will send them? (I'd also like Gnus to add the sig to them)

I'd be grateful for someone who is much more familiar with Gnus than I to point
out the right way to do the Gnus interaction parts - It'd be (I'm sure) much
better to use Gnuserv and Gnus's inbuilt functions than manipulating the Gnus
files directly? Pointers to relevent bits of code in Gnus would be appreciated.

Thanks for your time,
Ian

-- 
fortune says:

Leibowitz's Rule:
	When hammering a nail, you will never hit your
	finger if you hold the hammer with both hands.

~~~~~~~~~~~ Made in Ireland using GNU Emacs ~~~~~~~~~~~
Ian Swainson           Kia Ora!         ian@qui-oui.com
~~~~~~~~~~~~~~~ http://www.qui-oui.com ~~~~~~~~~~~~~~~~






             reply	other threads:[~2001-09-13 14:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 14:12 Ian Swainson [this message]
2001-09-13 23:15 ` Daniel Pittman
2001-09-14  9:43   ` Frank Schmitt
2001-09-14  9:59     ` Robin S. Socha
2001-09-14 11:20       ` Frank Schmitt
2001-09-15 10:16     ` Daniel Pittman
2001-09-14  9:56   ` Ian Swainson
2001-09-15 10:19     ` Daniel Pittman
2001-09-15 12:21       ` IMAP vs nnml ? (was: Palm and Gnus) Fabien Penso
2001-09-15 14:48         ` Simon Josefsson
2001-09-15 21:05         ` Kai Großjohann
2001-09-15 21:21           ` Paul Jarc
2001-09-15 23:36             ` Kai Großjohann
2001-09-16  5:00               ` Paul Jarc
2001-09-16 10:13         ` Nuutti Kotivuori

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=ug09rch7a.fsf@qui-oui.com \
    --to=ian@qui-oui.com \
    /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).