From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: auth-source.el and eieio
Date: Thu, 17 Feb 2011 19:46:58 +0100 [thread overview]
Message-ID: <87lj1ev6ql.fsf@dod.no> (raw)
In-Reply-To: <87fwrmzj39.fsf@lifelogs.com>
>>>>> Ted Zlatanov <tzz@lifelogs.com>:
> On Thu, 17 Feb 2011 15:02:56 +0100 Steinar Bang <sb@dod.no> wrote:
SB> One thing that may be coincidental: I lost a lot of gnus-sync read
SB> marks in this group when starting the new version.
SB> Could it be that the .authinfo prompting messed up the
SB> tramp-contacting-my-sync-server? I killed the first emacs process
SB> without saving anything and started gnus in a fresh emacs, without
SB> reading any auto save files. And this time it clearly used tramp to
SB> get the sync stuff. But the read information in this group was
SB> still lost (247 unread instead of 11).
> I don't know. I would version the gnus-sync file so you can come back
> to an earlier version. Any bugs in that code won't get fixed, now
> that Lars has promised to have Cloudy Gnus done by the weekend ;)
Possibly.
Until then I will just live with the gnus-sync.el the way it is. :-)
next prev parent reply other threads:[~2011-02-17 18:46 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 1:25 Katsumi Yamaoka
2011-02-14 1:45 ` Lars Ingebrigtsen
2011-02-14 15:33 ` Ted Zlatanov
2011-02-14 15:40 ` Richard Riley
2011-02-14 16:49 ` Ted Zlatanov
2011-02-14 17:39 ` David Engster
2011-02-14 18:02 ` Ted Zlatanov
2011-02-14 20:16 ` Lars Ingebrigtsen
2011-02-14 20:44 ` David Engster
2011-02-14 20:45 ` Reiner Steib
2011-02-14 21:09 ` Lars Ingebrigtsen
2011-02-14 22:01 ` Steinar Bang
2011-02-16 9:20 ` Reiner Steib
2011-02-16 19:10 ` Ted Zlatanov
2011-02-16 20:59 ` David Engster
2011-02-14 21:07 ` Ted Zlatanov
2011-02-14 21:18 ` Lars Ingebrigtsen
2011-02-14 21:26 ` David Engster
2011-02-14 21:39 ` Ted Zlatanov
2011-02-14 21:53 ` David Engster
2011-02-14 21:57 ` Lars Ingebrigtsen
2011-02-14 22:07 ` Ted Zlatanov
2011-02-14 22:20 ` Lars Ingebrigtsen
2011-02-14 22:33 ` Ted Zlatanov
2011-02-15 8:11 ` Reiner Steib
2011-02-15 8:41 ` David Engster
2011-02-15 13:43 ` Ted Zlatanov
2011-02-15 14:11 ` Steinar Bang
2011-02-16 20:28 ` Reiner Steib
2011-02-16 20:50 ` Ted Zlatanov
2011-02-16 22:16 ` Ted Zlatanov
2011-02-17 0:31 ` Katsumi Yamaoka
2011-02-17 0:40 ` Matt Lundin
2011-02-17 14:02 ` Steinar Bang
2011-02-17 17:06 ` Ted Zlatanov
2011-02-17 18:46 ` Steinar Bang [this message]
2011-02-17 22:01 ` Steinar Bang
2011-02-17 22:39 ` Lars Ingebrigtsen
2011-02-18 8:48 ` Steinar Bang
2011-02-18 10:52 ` Steinar Bang
2011-02-18 12:22 ` Steinar Bang
2011-02-18 20:26 ` Ted Zlatanov
2011-02-18 21:33 ` Charles Philip Chan
2011-02-19 18:00 ` Charles Philip Chan
2011-02-21 16:53 ` Charles Philip Chan
2011-02-18 22:11 ` Lars Ingebrigtsen
2011-02-22 21:53 ` Ted Zlatanov
2011-02-14 22:46 ` David Engster
2011-02-15 8:37 ` Steinar Bang
2011-02-14 22:18 ` David Engster
2011-02-14 22:04 ` Steinar Bang
2011-02-15 8:13 ` Jochen Hein
2011-02-16 20:15 ` Jochen Hein
2011-02-14 9:49 ` Michael Albinus
2011-02-14 15:26 ` Ted Zlatanov
2011-02-14 15:47 ` Michael Albinus
2011-02-14 16:54 ` 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=87lj1ev6ql.fsf@dod.no \
--to=sb@dod.no \
--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).