Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: cloudy Gnus
Date: Fri, 11 Mar 2011 13:47:30 -0600	[thread overview]
Message-ID: <87ipvpfnhp.fsf@lifelogs.com> (raw)
In-Reply-To: <87zkplz5nr.fsf_-_@lifelogs.com>

On Thu, 24 Feb 2011 11:47:04 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> Yeah, but gnus-sync it probably triggering the bugs.  Cloudy Gnus is on
TZ> my TODO list after someday finishing auth-source.el and bringing GnuTLS
TZ> up to 2.1x in Emacs.  I don't know how much time Lars will have for it
TZ> but it's definitely time to give Gnus that functionality so I'll do what
TZ> I can.  I actually thought I'd be done with auth-source by now but the
TZ> damn UI is too complicated.  UI is hard, let's go shopping!

I disabled the automatic `gnus-sync-read' calls in the Gnus hooks, so
now loading gnus-sync.el and enabling it is harmless.  You'll just get a
file saved if you set the `gnus-sync-backend'.  You have to call
`gnus-sync-read' yourself when you want to load that data.

I wrote in the comments that this is a temporary measure.  I'd like to
get started on Cloudy Gnus soon.  Can we close the book on No Gnus?  Or
is there something yet to be done?

Thanks
Ted




  reply	other threads:[~2011-03-11 19:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 12:21 nntp marks getting reset all the time Ted Zlatanov
2011-02-23 13:45 ` Steinar Bang
2011-02-23 14:32   ` Ted Zlatanov
2011-02-24  7:37     ` Steinar Bang
2011-02-24 16:31       ` Ted Zlatanov
2011-02-24 17:34         ` Steinar Bang
2011-02-24 17:47           ` cloudy Gnus (was: nntp marks getting reset all the time) Ted Zlatanov
2011-03-11 19:47             ` Ted Zlatanov [this message]
2011-03-15 15:54               ` cloudy Gnus Lars Magne Ingebrigtsen
2011-03-15 16:02                 ` Ted Zlatanov
2011-03-15 16:11                   ` Lars Magne Ingebrigtsen
2011-03-15 16:25                     ` Ted Zlatanov
2011-03-15 16:33                       ` Lars Magne Ingebrigtsen
2011-03-17  8:49                   ` Steinar Bang
2011-03-15 16:59               ` Didier Verna
2011-03-15 17:02                 ` Lars Magne Ingebrigtsen
2011-03-15 17:09                   ` Adam Sjøgren
2011-03-15 17:21                     ` Lars Magne Ingebrigtsen
2011-03-16  8:15                   ` Didier Verna
2011-03-16 13:58                     ` Ted Zlatanov
2011-03-16 17:30                       ` Lars Magne Ingebrigtsen
2011-03-16 19:57                         ` Frank Schmitt
2011-03-17 11:03                         ` Didier Verna
2011-03-15 17:17                 ` Ted Zlatanov
2011-03-15 17:23                   ` Lars Magne Ingebrigtsen
2011-03-25  8:17             ` Steinar Bang
2011-03-25 19:31               ` Ted Zlatanov
2011-03-25 21:45                 ` Steinar Bang
2011-03-26 20:53                   ` Bernt Hansen
2011-03-27 17:12                     ` Steinar Bang
2011-03-27 18:35                       ` Steinar Bang
2011-02-25  3:01 ` nntp marks getting reset all the time Lars Ingebrigtsen
2011-02-25 14:45   ` Ted Zlatanov

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=87ipvpfnhp.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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).