Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: <ding@gnus.org>, <emacs-devel@gnu.org>
Subject: Tracing changes of a variable's value?  `nntp-marks-is-evil'
Date: Sat, 01 Mar 2008 14:57:46 +0100	[thread overview]
Message-ID: <v9zltibl7p.fsf@marauder.physik.uni-ulm.de> (raw)

Hi,

I have set the Gnus server variable `nntp-marks-is-evil' set to t
(default is nil).  Occasionally, e.g. when there are network problems,
after hitting `C-g', this variable changes to nil and I get errors
(see blow: [1]).

I don't know why the variable's value is changed.  Is the any way to
produce a backtrace when a variable changes?  I run Emacs under gdb,
if that is relevant.

[1]
--8<---------------cut here---------------start------------->8---
                  [Hitting `C-g'...]
Quit
                  [Hitting `g' in Gnus ...]
Checking new news...
Creating nntp marks directory ~/News/marks/localhost/foo.bar/
Updating marks for foo.bar...
Error reading nntp marks file ~/News/marks/localhost/foo.bar/ ((error
 IO error reading ~/News/marks/localhost/foo.bar/: Is a directory)).
 Continuing will use marks from .newsrc.eld.  Continue? (y or n)
Updating marks for foo.bar...done
Creating nntp marks directory ~/News/marks/localhost/foo.test/
Updating marks for foo.test...
Error reading nntp marks file ~/News/marks/localhost/foo.test/ ((error
 IO error reading ~/News/marks/localhost/foo.test/: Is a directory)).
 Continuing will use marks from .newsrc.eld.  Continue? (y or n)
Quit
                  [M-x rs-toggle-variable RET nntp-marks-is-evil RET ...]
`nntp-marks-is-evil' set to `t'
Checking new news...
                  [Everything fine again ...]
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




                 reply	other threads:[~2008-03-01 13:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=v9zltibl7p.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).