Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Hanging gnus session
Date: Wed, 11 Feb 2015 08:15:43 +0100	[thread overview]
Message-ID: <874mqs536o.fsf@gnu.org> (raw)
In-Reply-To: <87mw4lgane.fsf@engels.histomat.net>

Haines Brown <haines@engels.histomat.net> writes:

Hi Haines,

> Here is my setup. In .fluxbox I have a key defined that starts an
> "emacs-gnus" executable script. That script simply has:
>
>      #!/bin/sh
>      emacs -q -l /home/haines/.emacs.d/elisp/gnus.el
>      exit 0
>
> The gnus.el file defines the news servers and some other parameters
> which have never been a problem. As its final line I have:
>
>       (gnus)
>
> When I hit the key, gnus starts OK, and it checks new news. However,
> there are two problems.
>
> First, when gnus starts, the emacs minibuffer says, "Gnus auto-save
> file exists. Do you want to read it?" If I respond "y", messages are
> retrieved. I don't know why gnus needs to access an auto-save file and I
> would like to avoid the query under normal conditions.

Gnus regularly auto-saves what articles you've read etc, and when you
hit `s' in *Group* or quit Gnus it saves that information to
~/.newsrc.eld and deletes the auto-saved file.  So when it asks you that
question on startup, it means that you've not properly quit your
previous Gnus session.  Maybe you simply killed emacs without quitting
Gnus before?  Or maybe there's another Emacs session running Gnus
already?

> Second, when I do "g" to update the groups, gnus simply hangs. $ ps aux
> tells me there are two processes running:
>
>     /bin/sh /home/haines/scripts/emacs-gnus
>     emacs -q -l /home/haines/.emacs.d/elisp/gnus.el
>
> I have to kill them and start gnus anew in order to read news again. I
> would prefer that the emacs client run gnus all the time and I only need
> to press g to update it.

That's how it's supposed to work.  Does the echo area indicate what
server it checks when it hangs?

What you can also do is `M-x toggle-debug-on-quit RET' before you update
with `g'.  Then, when Gnus hangs for a while hit `C-g'.  That will show
you a backtrace which you can post here.

Bye,
Tassilo



      reply	other threads:[~2015-02-11  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 13:26 Haines Brown
2015-02-11  7:15 ` Tassilo Horn [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=874mqs536o.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --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).