Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Hadron Quark <hadronquark@gmail.com>
Subject: Re: Gnus + Leafnode = 10 minutes to start
Date: Sat, 30 Dec 2006 05:12:47 +0100	[thread overview]
Message-ID: <873b6ym37k.fsf@gmail.com> (raw)
In-Reply-To: <hgng64xph5.ln2@news.gates-of-hell.com>

SINNER <99nesorjd@gates_of_hell.invalid> writes:

> * Charles philip Chan wrote in gnu.emacs.gnus:
>> On 29 Dec 2006, 99nesorjd@gates_of_hell.invalid wrote:
>
>>> No, but why would it mark what is not necessary?
>
>> No, it should only create the hierachy and .marks files for the groups
>> you are subscribe to.
>
>>> absolutley not.
>
>>> [04:34 PM][J:0][sinner@~]$ cat .newsrc | grep ':'
>>> alt.comp.os.linux: 1-64
>>> alt.games.mame: 1-902,1598,1600
>>> alt.os.linux: 1-1081,1433,2586,2588,2594-2595,2605-2606
>>> alt.os.linux.debian: 1-213
>>> alt.os.linux.ubuntu: 1-1231
>>> alt.smokers.cigars: 1-1553
>>> news.software.readers: 1-3000,3090-3092
>
>> Strange.
>
> Tell me about it :)
>
>>> Do you use the spool or nntp setting in .gnus.el?
>
>> nntp.
>
>> Can you post all your Gnus settings to the group?
>
> (setq user-mail-address "SINNER@gates_of_hell.invalid")
> (setq user-full-name "SINNER")
>
> (setq gnus-select-method '(nntp "localhost"))
>
> (setq gnus-check-new-newsgroups nil
>       gnus-read-active-file nil
>       gnus-nov-is-evil nil)
>
> (setq nnfolder-marks-is-evil 1)

The wonders of Linux setups :-;

Im a bit pissed off that this is happening because it might put you off
the best newsreader & email client in the history of the world.

Wish I could help more.

I had lots of issues initially when I set up slrn with leafnode but it
all "just worked" with gnus. Doh! Damn I said it :-;

Dont worry, someone will find the solution.

  reply	other threads:[~2006-12-30  4:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 18:09 SINNER
2006-12-29 18:51 ` Glyn Millington
2006-12-29 20:30   ` SINNER
2006-12-29 20:46     ` Hadron Quark
2006-12-29 21:30       ` SINNER
2006-12-29 21:58         ` Charles philip Chan
2006-12-29 22:40           ` SINNER
2006-12-29 22:58             ` Charles philip Chan
2006-12-30  0:20               ` SINNER
2006-12-30  4:12                 ` Hadron Quark [this message]
2006-12-30 16:00                   ` SINNER
2006-12-30 16:54                   ` Charles philip Chan
2006-12-30  6:59             ` Stepan Golosunov
2006-12-30 15:10               ` SINNER
2006-12-30 15:57                 ` Charles philip Chan
2006-12-30 16:10                   ` SINNER
2006-12-30 16:30                   ` SINNER
2006-12-30 16:48                     ` Charles philip Chan
2006-12-30 17:32                     ` Hadron Quark
2006-12-30 19:00                       ` SINNER
2006-12-30 17:03                 ` Stepan Golosunov
2006-12-30 18:20                   ` SINNER
2006-12-30 19:31         ` Reiner Steib
2006-12-30 20:20           ` SINNER
2006-12-30 22:04             ` Reiner Steib
2006-12-31  7:48               ` Hadron Quark
2006-12-30  0:13   ` Chunhua Li
2006-12-30 16:50     ` Charles philip Chan

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=873b6ym37k.fsf@gmail.com \
    --to=hadronquark@gmail.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).