From: Bill White <billw@wolfram.com>
Subject: `|' error in summary buffer
Date: Thu, 14 Mar 2002 08:38:17 -0600 [thread overview]
Message-ID: <ruoofhrp63q.fsf@billwlx.wolfram.com> (raw)
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:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
byte-code("\b.\b.ÆÇ!. q.\n.\f.\x15.È. .\fÉ=.\x1f.Ê. .\r.\f\fË=.*.\x0e\r.\x0e.\x0fq.\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)
gnus-article-save(#<buffer *Gnus Save*> nil 1)
gnus-summary-save-article(nil t)
gnus-summary-pipe-output(nil)
call-interactively(gnus-summary-pipe-output)
----------------------------------------------------------------------
Here's what it's supposed to do:
| runs the command gnus-summary-pipe-output
which is an interactive compiled Lisp function in `gnus-sum'.
It is bound to |, O p, <menu-bar> <Article> <Output> <Pipe through a filter>.
(gnus-summary-pipe-output &optional ARG)
Pipe the current article to a subprocess.
If N is a positive number, pipe the N next articles.
If N is a negative number, pipe the N previous articles.
If N is nil and any articles have been marked with the process mark,
pipe those articles instead.
Cheers -
bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."
next reply other threads:[~2002-03-14 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:38 Bill White [this message]
2002-03-14 14:56 ` Matthieu Moy
2002-03-14 15:16 ` Bill White
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=ruoofhrp63q.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).