From: Ray <ray@invald.com>
To: info-gnus-english@gnu.org
Subject: Re: Check for new news g hangs gnus
Date: Sat, 07 Mar 2015 18:07:45 +0000 [thread overview]
Message-ID: <87a8zollzi.fsf@Sony.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87y4nvz2f0.fsf@engels.histomat.net>
Haines Brown <haines@engels.histomat.net> writes:
> I installed gnus with ELPA for emacs 24. It worked properly on old
> hardware, but a similar setup on new hardware hangs when I check for new
> news by typing "g". What is different is the overall setup.
>
> I have a key in fluxbox that calls ~/scripts/emacs-gnus executable
> script. This script has this line pointing to its init file:
>
> emacs -q -l /home/haines/.emacs.d/elisp/gnus.el
>
> The basic change from the working system was to relocate ~/.emacs-gnus
> to ~/.emacs.d/elisp/emacs-gnus. Other changes I do not believe are
> relevant.
>
> When the window comes up to display the subscribed news groups and the
> number of new messagse in them, the menu bar provides such things as
> Gnus, Groups, Group. In the first is the command g to check for new
> news. In my current setup, when I type g, it causes gnus to hang.
As stated in this thread I too have had the g to update news causing it
to hang.
However I think I may have just cured my own issues and perhaps it will
work for some of you guys too. I noticed that in my server buffer all
NNTP servers had agent applied but NOT news.gwene.org I added the agent
now g seems to refresh any new news immediately. Good luck all.
RayH
prev parent reply other threads:[~2015-03-07 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 15:04 Haines Brown
2015-02-18 22:55 ` Ray
2015-02-18 23:10 ` Rasmus
2015-02-19 4:35 ` Clemens Schüller
2015-02-23 8:02 ` Igor Sosa Mayor
2015-03-07 18:07 ` Ray [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=87a8zollzi.fsf@Sony.i-did-not-set--mail-host-address--so-tickle-me \
--to=ray@invald.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).