Gnus development mailing list
 help / color / mirror / Atom feed
From: Manoj Srivastava <srivasta@acm.org>
Subject: Re: Trouble with gnus customize
Date: Wed, 12 Apr 2006 23:43:07 -0500	[thread overview]
Message-ID: <87psjmw0f8.fsf@glaurung.internal.golden-gryphon.com> (raw)
In-Reply-To: <m31ww27tec.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 12 Apr 2006 16:36:27 +0200")

On 12 Apr 2006, Lars Magne Ingebrigtsen stated:

> Manoj Srivastava <srivasta@acm.org> writes:
>
>> I can reproduce this -- but setting debug-on-error gave no
>> backtrace, just the error message, as above.
>
> Try `(setq debug-ignored-errors nil)' as well...

        OK. I don't understand what just happened, so I'll just tell
 y'all about it, with no speculation. Sequence of events:

 1) I read mail I am replying to. I hit M-u to mark ir un read. I hit
    q to quit the nnml group and return to the *Group* buffer.
 2) M-: (setq debug-on-error t)
    M-: (setq debug-ignored-errors nil)
 3) G C (enter customization buffer)
 4) Hit down arrow twice, till the curso is over a squarer button
    before To-List.
 5) Hit "space" to toggle button.
Debugger entered--Lisp error: (text-read-only "Attempt to change text outside editable field")
  signal(text-read-only ("Attempt to change text outside editable field"))
  widget-before-change(136 136)
  recursive-edit()
  byte-code("Æ\x10	@Ç=ƒ!\0ÈÉÊ\"�É!‰\x1aA@)¢Ì=ƒ!\0ÈÍÊ\"�\v!� �	!ˆ\fƒc\0Ñed\"\rVƒW\0eb�\rÂ¥yˆ`\x1e\x1cdb�\rÂ¥\rZyˆ\x0e\x1c`|ˆ)Ócˆeb�ÕÖ \"� �Ø!�Ê\x1e\x1d\x1e\x1eÔÚ!ˆ� ˆ+Ù‡" [unread-command-char debugger-args x debugger-buffer noninteractive debugger-batch-max-lines -1 debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message "%s" buffer-string kill-emacs "" nil "" recursive-edit middlestart buffer-read-only standard-output] 4)
  debug(error (void-function nil))
  (nil)

 6) Hit C-c C-c

        Emacs crashed.

 7) emacs -f gnus
 8) G C
 9) down arrow, hit space. A check mark appears. !!!
10) down arrow, enter button, hit space: Same error as above.


        The error happens most of the time, just not every time. Which
 file should I load the .el of to get a better backtrace?

        manoj

-- 
I think it's a new feature.  Don't tell anyone it was an accident.
:-) Larry Wall on s/foo/bar/eieio in <10911@jpl-devvax.JPL.NASA.GOV>
Manoj Srivastava   <srivasta@acm.org>  <http://www.datasync.com/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



  reply	other threads:[~2006-04-13  4:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-11 22:49 leandro noferini
2006-04-12  4:49 ` Lars Magne Ingebrigtsen
2006-04-12 14:17   ` Manoj Srivastava
2006-04-12 14:36     ` Lars Magne Ingebrigtsen
2006-04-13  4:43       ` Manoj Srivastava [this message]
2006-04-13  5:40         ` Lars Magne Ingebrigtsen
2006-04-13 13:33           ` Manoj Srivastava
2006-04-13 13:45             ` Lars Magne Ingebrigtsen
2006-04-14 15:50           ` leandro noferini
2006-04-15  5:43             ` Lars Magne Ingebrigtsen
2006-04-15 20:36               ` leandro noferini
2006-04-16  7:25                 ` Lars Magne Ingebrigtsen
2006-04-19 20:36                   ` leandro noferini
2006-04-22  0:22                     ` Lars Magne Ingebrigtsen
2006-04-22 14:42                       ` leandro noferini
2006-04-23 14:23                         ` Lars Magne Ingebrigtsen
2006-04-25 20:57                           ` leandro noferini

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=87psjmw0f8.fsf@glaurung.internal.golden-gryphon.com \
    --to=srivasta@acm.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).