From: Jake Colman <colman@ppllc.com>
Subject: Re: Invalid Data on Line 1 - Please Help!
Date: Thu, 30 Oct 2003 14:39:20 -0500 [thread overview]
Message-ID: <76znfitt07.fsf@newjersey.ppllc.com> (raw)
In-Reply-To: <uwuam7e02.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Thu, 30 Oct 2003 12:54:21 -0600")
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
>>>>> "KG" == Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
KG> 4) Start gnus as usual.
KG> 5) Proceed until you get thrown into the debugger.
KG> 6) While in the debugger, eval (current-buffer). If that buffer isn't
KG> visible, select it so that you can see what is wrong with line 1.
KG> 7) Exit gnus, edit the broken file to fix line 1, then start gnus to
KG> see if you're OK.
KG> I'd appreciate it if you'd post which file had the invalid line and
KG> also the invalid line itself. Gnus may not be able to avoid the error
KG> but it should, if at all possible, handle it with more grace.
I've left just enough of your post to give some context.
Just before I saw your reply, I completed my fight with edebug to gain some
insight into what's going on.
The problem is in (gnus-nov-parse-line). It correctly parses all of the
components of the header line and then calls (widen). It is there that the
error is triggered.
I am not sure what's going on but I have my suspicions. I recently loaded a
new library: narrow-stack.el. This package has the following line:
(ad-enable-advice 'widen 'before 'ns-widen-advice))
I strongly suspect that this is the cause of the problem, though I have no
idea why. I have removed narrow-stack.el and will see whether my problem
goes away.
In case you are interested, I am attaching narrow-stack.el with this
message. Please let me know what you think of my diagnosis.
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman@ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
[-- Attachment #2: narrow-stack.el --]
[-- Type: application/emacs-lisp, Size: 4883 bytes --]
prev parent reply other threads:[~2003-10-30 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 15:41 Jake Colman
2003-10-30 18:54 ` Kevin Greiner
2003-10-30 19:39 ` Jake Colman [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=76znfitt07.fsf@newjersey.ppllc.com \
--to=colman@ppllc.com \
/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).