From: Josef Oswald <NO.SPAM.for.gnus@chello.at>
Subject: Re: Customization file for gnus where is it?
Date: Sat, 29 Nov 2003 22:26:45 GMT [thread overview]
Message-ID: <sweet.nirwana_is87y8tyrc4z.fsf@home_at> (raw)
In-Reply-To: <m2ptfb9ncp.fsf@bitstream.net>
Tim McNamara <timmcn@bitstream.net> writes:
> Josef Oswald <NO.SPAM.for.gnus@chello.at> writes:
>
>> actually this was not correct, some configuration was still missing,
>> but Tim got me _looking_ on the right track and I found one more
>> file I had to copy: nesrc.news.my.provider.eld.
>>
>> One would think that gnus does keep those configurations ( since no
>> other news-reader uses them) in its own customization
>> file.... Anyway
>
> .newsrc.eld is a file unique to Gnus- other newsreaders don't use it.
> .newsrc is a common file for newsreaders to use. Watch the minibuffer
> as Gnus loads- it reads .newsrc.eld rather than .newsrc.
Yeah but a lot of the infos is stored in the
_newsrc.news.my.provider.eld_, a file I never paid close attention when
I was looking for the custom settings. In any case now it really back
to normal ( at least with Gnus) but I can't get XEmacs running on this
machine, ( and even in Debian stable it seems the package is broken, a
attemt to configure a new one failed miserably ....)
And in this X-environment I don't get the key to produce "@" ....sorry
If I bothered you with this _non_ gnus problems...
Thanks for your help nontheless :-)
Josef Oswald also -> gnus@chello.at :-)
--
Gnus gives you all the opportunity you could possibly want for
shooting yourself in the foot.
--from the INFO --
prev parent reply other threads:[~2003-11-29 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pan.2003.11.28.19.09.35.404092@chello.at>
2003-11-28 19:19 ` Tim McNamara
[not found] ` <sweet.nirwana_ism2zneg9ji4.fsf@home_at>
[not found] ` <sweet.nirwana_ism2y8tz72fa.fsf@home_at>
[not found] ` <m2ptfb9ncp.fsf@bitstream.net>
2003-11-29 22:26 ` Josef Oswald [this message]
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=sweet.nirwana_is87y8tyrc4z.fsf@home_at \
--to=no.spam.for.gnus@chello.at \
/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).