Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: Re: automatic Agentizing of servers (was: Summary buffer
Date: Mon, 29 Dec 2003 23:36:18 +0100	[thread overview]
Message-ID: <87y8svxndp.fsf@doohan.bang.priv.no> (raw)
In-Reply-To: <87pte72rb7.fsf@doohan.bang.priv.no>

>>>>> Steinar Bang <sb@dod.no>:

> I'll recompile and restart and see what the behaviour's like.

Now I've recompiled and started a fresh XEmacs, and the servers are
still agentized when I start up (if I do an ls -al on ~/News/agent/ I
can see stuff appearing there during startup).

Here's a few messages from the minibuffer during Gnus startup.

...
Reading /home/sb/.newsrc.eld...
Loading efs-cu...done
Loading efs-cu...
Loading bbdb-gnus...done
Loading bbdb-gnus...
First time agent user, agentizing remote groups...
Loading gnus-agent...done
Loading gnus-agent...
Loading gnus-demon...done
Loading gnus-demon...
Loading executable...done
Loading executable...
Loading gnus-start...done
Loading gnus-start...
Loading gnus...done
Loading gnus-xmas...done
Loading gnus-xmas...
Loading gnus...
...

My platform:
 - Gnus CVS update as of a few minutes ago
 - XEmacs 21.4 (patch 6) "Common Lisp" [Lucid] (i386-debian-linux, Mule) of Sat Apr  6 2002 on eeyore
 - Intel PII, running debian sarge testing/unstable




  reply	other threads:[~2003-12-29 22:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 15:14 Summary buffer highlighting Emerick Rogul
2003-11-24 16:17 ` automatic Agentizing of servers (was: Summary buffer highlighting) Ted Zlatanov
2003-11-24 16:42   ` automatic Agentizing of servers (was: Summary buffer Emerick Rogul
2003-11-24 16:47   ` Kevin Greiner
2003-11-24 17:05     ` Emerick Rogul
2003-11-24 17:07     ` Ted Zlatanov
2003-11-25  2:48       ` Kevin Greiner
2003-11-25  8:25         ` Simon Josefsson
2003-11-25 18:31           ` Ted Zlatanov
2003-12-29 21:22           ` Steinar Bang
2003-12-29 21:39             ` Simon Josefsson
2003-12-29 21:58               ` Steinar Bang
2003-12-29 22:23                 ` Steinar Bang
2003-12-29 22:27                   ` Steinar Bang
2003-12-29 22:36                     ` Steinar Bang [this message]
2003-12-29 22:33                 ` Simon Josefsson
2003-12-29 22:44                   ` Steinar Bang
2003-12-29 23:00                     ` Simon Josefsson
2003-12-29 23:10                       ` Kevin Greiner
2003-12-29 23:17                         ` Simon Josefsson
2003-12-29 23:37                           ` Kevin Greiner
2003-12-29 23:53                             ` Simon Josefsson
2003-12-30  2:19                               ` Harry Putnam
2003-12-30  9:44                                 ` Steinar Bang
2003-12-30 11:16                                 ` Simon Josefsson
2003-12-30 20:55                                   ` Steinar Bang
2003-12-30 21:30                                     ` Simon Josefsson
2003-12-30 22:49                                       ` Harry Putnam
2003-12-31 12:55                                       ` Steinar Bang
2003-12-30  9:40                       ` Steinar Bang

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=87y8svxndp.fsf@doohan.bang.priv.no \
    --to=sb@dod.no \
    /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).