From: Manoj Srivastava <srivasta@acm.org>
Subject: Re: Trouble with gnus customize
Date: Wed, 12 Apr 2006 09:17:12 -0500 [thread overview]
Message-ID: <874q0ydgk7.fsf@glaurung.internal.golden-gryphon.com> (raw)
In-Reply-To: <m3lkubwg86.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 12 Apr 2006 06:49:29 +0200")
On 11 Apr 2006, Lars Magne Ingebrigtsen spake thusly:
> leandro noferini <lnoferin@cybervalley.org> writes:
>
>> I have a trouble with the Gnus Customize function ("G c" keys)
>> because I cannot edit any field in the buffer and I get the error
>>
>> Text is read-only: Attempt to change text outside editable field
>
> Hm... works for me. `(setq debug-on-error t)', repeat the bug and
> post the resulting backtrace.
I can reproduce this -- but setting debug-on-error gave no
backtrace, just the error message, as above.
manoj
--
UFOs are for real: the Air Force doesn't exist.
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
next prev parent reply other threads:[~2006-04-12 14:17 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 [this message]
2006-04-12 14:36 ` Lars Magne Ingebrigtsen
2006-04-13 4:43 ` Manoj Srivastava
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=874q0ydgk7.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).