unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: instead of gnus-cloud.el
Date: Wed, 13 Jul 2016 10:32:13 -0400	[thread overview]
Message-ID: <87mvllwqvm.fsf@lifelogs.com> (raw)
In-Reply-To: m337ne3lfc.fsf@gnus.org

On Tue, 12 Jul 2016 17:50:31 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

On Wed, 13 Jul 2016 09:06:34 -0400 Richard Stallman <rms@gnu.org> wrote: 

>> If "cloud" is really unacceptable, this replaces gnus-sync.el so maybe
>> it could take that name. But I would rather explain the joke in the
>> commentary.

RS> That joke might be funny, if it were presented clearly enough that
RS> people could get it.

RS> But please don't put the joke in the file name.  Most people who see
RS> the file name won't know it is a joke.  With them, it will really encourage
RS> the harmful "cloud" meme.

OK, I'll let you and Lars and the maintainers figure it out. Let's do
the rename, if that's the decision, after the current gnus-cloud code is
reviewed and merged, or it will get confusing (because the feature
branch currently removes the old gnus-sync.el).

On Wed, 13 Jul 2016 09:04:48 -0400 Richard Stallman <rms@gnu.org> wrote: 

RS> Writing for the manual later is ok, but it should have comments in the
RS> file now, don't you think?

I already documented many of the gnus-cloud.el functions in my feature
branch. I'll add more docs to the code and expand the manual after it's
merged, since it's still in progress.

On Wed, 13 Jul 2016 09:52:56 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

SM> BTW, the text says "imap" but the code (and the name) doesn't look
SM> specific to imap (other than a call to nnimap-request-articles).

Yeah, indeed it may work with nnml right now, but we want to use IMAP
features in the future. For instance I think the native IMAP unique
article ID from https://tools.ietf.org/html/rfc3501#section-2.3.1 will
be better than the current `gnus-cloud-sequence' defvar. And IMAP flags
may be good for separating full vs. incremental updates, which currently
are encoded in the article subject.

Ted




  reply	other threads:[~2016-07-13 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k2gs8bak.fsf@lifelogs.com>
2016-07-12  5:10 ` instead of gnus-cloud.el Richard Stallman
2016-07-12  7:44   ` Lars Magne Ingebrigtsen
2016-07-13 13:04     ` Richard Stallman
2016-07-13 13:52     ` Stefan Monnier
2016-07-12 13:44   ` Ted Zlatanov
2016-07-12 15:50     ` Lars Ingebrigtsen
2016-07-13 14:32       ` Ted Zlatanov [this message]
2016-07-13 13:06     ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mvllwqvm.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).