From: Bill White <billw@wolfram.com>
Subject: Re: `|' error in summary buffer
Date: Thu, 14 Mar 2002 09:16:38 -0600 [thread overview]
Message-ID: <ruosn73nprd.fsf@billwlx.wolfram.com> (raw)
In-Reply-To: <vpqelinw62x.fsf@montrose.imag.fr> (Matthieu Moy's message of "Thu, 14 Mar 2002 15:56:54 +0100")
On Thu Mar 14 2002 at 08:56, Matthieu Moy <Matthieu.Moy@imag.fr> said:
> Bill White <billw@wolfram.com> writes:
>
>> Unless my fingers are mis-remembering something, until very recently
>> typing `|' on an article in the summary buffer would give me a
>> minibuffer prompt letting me specify a shell command to run on the
>> article. Now I get this nonsense about saving the article:
>
> It does with my Gnus. (Oort Gnus v0.06/GNU Emacs 21.1.1)
>
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>> byte-code("\b.\b.ÆÇ!. q.\n.\f...È. .\fÉ=.\x1f.Ê. .\r.\f\fË=.*..\r....q.\b.\f!+." [gnus-default-article-saver gnus-article-buffer save-buffer gnus-save-article-buffer gnus-prompt-before-saving file error "No default saver is defined" default always nil t filename num gnus-number-of-articles-to-be-saved gnus-article-current-summary] 2)
>
> Usually, people prefer to read /code/ than /byte code/, so, you
> should run gnus uncompiled if you want to post understandable stake
> trace ;-)
so I removed the .elc files, restarted emacs and gnus, and `|' worked
fine . Then I recompiled gnus, restarted emacs and gnus, and it's
*still* working fine. WTF?
Cheers -
bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."
next prev parent reply other threads:[~2002-03-14 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:38 Bill White
2002-03-14 14:56 ` Matthieu Moy
2002-03-14 15:16 ` Bill White [this message]
2002-03-16 15:42 ` Kai Großjohann
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=ruosn73nprd.fsf@billwlx.wolfram.com \
--to=billw@wolfram.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).