Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: notbob <notbob@nothome.com>
To: info-gnus-english@gnu.org
Subject: Re: More gnewb questions
Date: Mon, 01 Jun 2009 17:11:39 GMT	[thread overview]
Message-ID: <slrnh282ua.3kl.notbob@bb.nothome.com> (raw)
In-Reply-To: <87my8s836x.fsf@topper.koldfront.dk>

On 2009-06-01, Adam Sjøgren <asjo@koldfront.dk> wrote:
>
> ,----[ C-h v gnus-read-active-file RET ]
>| `gnus-read-active-file' is a variable declared in Lisp.
>|   -- loaded from "gnus-start"

I tried it and gnus doesn't work at all, now.  Is it a toggle variable --
just run again?  The only gnus-start I can find is a binary file.  I'm
reading the gnus manual like crazy, but it's so vague.  Where is the
"active" file.  Manual talks about it, but doesn't identify it.  

Also, a ~/.gnus.el file has yet to be created.  I gotta do it manually?

nb





>| 
>| Value: nil
>| 
>| Documentation:
>| *Non-nil means that Gnus will read the entire active file at startup.
>| If this variable is nil, Gnus will only know about the groups in your
>| `.newsrc' file.
>| 
>| If this variable is `some', Gnus will try to only read the relevant
>| parts of the active file from the server.  Not all servers support
>| this, and it might be quite slow with other servers, but this should
>| generally be faster than both the t and nil value.
>| 
>| If you set this variable to nil or `some', you probably still want to
>| be told about new newsgroups that arrive.  To do that, set
>| `gnus-check-new-newsgroups' to `ask-server'.  This may not work
>| properly with all servers.
> `----
>
> As you can see above, I have configured mine to nil (in .gnus, like
> this:
>   ; I find new groups myself:
>   (setq gnus-read-active-file nil)
> )
>
>> ......then the groups come up and are listed.  WTF!?  slrn does it in
>> 1/2 sec.
>
> I guess Gnus works differently than slrn, then.
>
>> I've tried reading the ~/newsrc (.el, .eld?) and can find no such
>> file.
>
> I've got:
>
>   $ ls .newsrc*
>   .newsrc  .newsrc.eld
>   $ 
>
>> All I find is ~/.news-dribble, which isn't even mentioned in the emacs
>> or gnus manuals.
>
> Perhaps that is because that file is an internal one?
>
>> One reason (other than the fact I despise vi!) I want to get better at
>> emacs instead of remaining with jed is, I can copy and paste into
>> emacs with better results.  With jed, specially with code, if I copy
>> and paste into jed, the indentations (and sometimes no indentations)
>> will always further indent to a stairstep, which has to be hand edited
>> out.  This is maddening and unacceptable.  I don't have this problem
>> with emacs.  That makes it all worth the effort.
>
> Do note though, that you can use Emacs with slrn just as easily as you
> can jed.
>
>
>   Best regards,
>
>      Adam
>

  reply	other threads:[~2009-06-01 17:11 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 13:52 notbob
2009-06-01 13:59 ` Adam Sjøgren
2009-06-01 17:11   ` notbob [this message]
2009-06-01 17:26     ` Adam Sjøgren
2009-06-01 17:59       ` notbob
2009-06-01 18:09         ` Adam Sjøgren
2009-06-01 18:42           ` notbob
2009-06-01 19:44             ` Adam Sjøgren
2009-06-01 20:11               ` notbob
2009-06-01 22:02                 ` Open urls in a browser (was: More gnewb questions) Memnon Anon
     [not found]                 ` <mailman.8311.1243894209.31690.info-gnus-english@gnu.org>
2009-06-02 12:42                   ` notbob
2009-06-02 15:24                     ` Open urls in a browser Richard Riley
2009-06-02 16:10                       ` notbob
2009-06-02 16:40                         ` Richard Riley
2009-06-19  3:54                 ` More gnewb questions Marshall Price
2009-06-19  3:40               ` Marshall Price
2009-06-19  3:42               ` Marshall Price
2009-06-19 10:01                 ` Adam Sjøgren
2009-06-21 10:04                   ` Marshall Price
2009-06-21 12:32                     ` Adam Sjøgren
2009-06-21 22:44                       ` Marshall Price
2009-06-22  5:50                         ` Adam Sjøgren
2009-06-19  3:27             ` Marshall Price
2009-06-19  3:25           ` Marshall Price
2009-06-01 14:25 ` notbob
2009-06-01 14:53   ` Vivien Moreau
2009-06-01 14:55   ` Tim Landscheidt
2009-06-01 18:15     ` Tassilo Horn
     [not found]   ` <mailman.8279.1243868161.31690.info-gnus-english@gnu.org>
2009-06-01 16:02     ` notbob
2009-06-01 16:09       ` Teemu Likonen
2009-06-01 16:59         ` notbob
2009-06-01 16:19       ` Vivien Moreau
2009-06-01 17:00         ` notbob
2009-06-01 18:19       ` Tassilo Horn
     [not found]       ` <mailman.8290.1243880414.31690.info-gnus-english@gnu.org>
2009-06-01 18:47         ` notbob
2009-06-01 18:25 ` Tassilo Horn
     [not found] ` <mailman.8291.1243880764.31690.info-gnus-english@gnu.org>
2009-06-01 18:56   ` notbob
2009-06-02  2:06 ` William Xu
     [not found] ` <mailman.8325.1243909737.31690.info-gnus-english@gnu.org>
2009-06-02  2:46   ` notbob
2009-06-02  8:53 ` Frédéric Perrin
     [not found] ` <mailman.8355.1243932820.31690.info-gnus-english@gnu.org>
2009-06-02 12:22   ` notbob
2009-06-02 15:41     ` Richard Riley
2009-06-02 16:37       ` notbob
2009-06-04  5:00   ` notbob
2009-06-04  7:02     ` Tassilo Horn
     [not found]     ` <mailman.3.1244098966.2128.info-gnus-english@gnu.org>
2009-06-04 12:52       ` notbob

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=slrnh282ua.3kl.notbob@bb.nothome.com \
    --to=notbob@nothome.com \
    --cc=info-gnus-english@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.
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).