From: Bud Rogers <budr@sirinet.net>
Subject: Re: pipe filter output to file?
Date: 11 Oct 1998 10:09:53 -0500 [thread overview]
Message-ID: <m2lnmn879a.fsf@twocups.sirinet.net> (raw)
In-Reply-To: Kai Grossjohann's message of "09 Oct 1998 18:50:44 +0200"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2366 bytes --]
Kai Grossjohann <grossjohann@amaunet.informatik.uni-dortmund.de> writes:
> What does C-h c | tell you when typed in a Gnus summary buffer? For me,
> it says it runs the command gnus-summary-pipe-output. If it is different
> for you, that might be a problem.
It is defined as gnus-summary-pipe-output.
> Just for fun, could you `emacs -q -no-site-file' then start Gnus then see
> whether `|' works. The `-q' means don't load ~/.emacs, the
> `-no-site-file' means don't load site-start.el. Omitting one of the two
> arguments loads the respective file, this way you can narrow down where
> the problem might be.
I spent some time with this. By temporarily renaming my startup files one
by one I've narrowed it down a little more. My .emacs seems to be OK. If
I rename .gnus AND .xemacs-options I'm OK. If I load either .gnus OR
.xemacs-options, I get 'Wrong type argument: stringp, nil'. The backtraces
in either case appear to be identical except for the tmp buffer name.
I've been through both files and I don't see anything obviously wrong. But
then, I don't really know what I'm looking for.
Backtrace with .gnus loaded follows. I hope that's OK.
Signaling: (wrong-type-argument stringp nil)
call-process-internal("/bin/bash" "/tmp/emacsa29486" #<buffer "*Shell
Command Output*"> nil "-c" nil) apply(call-process-internal "/bin/bash"
"/tmp/emacsa29486" #<buffer "*Shell Command Output*"> nil ("-c" nil))
call-process("/bin/bash" "/tmp/emacsa29486" #<buffer "*Shell Command
Output*"> nil "-c" nil) apply(call-process "/bin/bash" "/tmp/emacsa29486"
#<buffer "*Shell Command Output*"> nil ("-c" nil)) call-process-region(1
3244 "/bin/bash" nil #<buffer "*Shell Command Output*"> nil "-c" nil)
shell-command-on-region(1 3244 nil nil) gnus-summary-save-in-pipe(default)
byte-code("\b¬ÁÂ!\vq\f\x1d\x0e\x06¬Çª\x0e\x06Èa«Éª\x0e\n\x1e\v\x0e\x06Ìa\x0e\r\x1e\x0e\x0e\x0fq\b\x0e\v!+"
[gnus-default-article-saver error "No default saver is defined"
gnus-article-buffer save-buffer gnus-save-article-buffer
gnus-prompt-before-saving default always nil file filename t 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)
--
Bud Rogers <budr@sirinet.net> http://www.sirinet.net/~budr/zamm.html
formerly <budr@tanet.net>
next prev parent reply other threads:[~1998-10-11 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-08 18:07 Bud Rogers
1998-10-08 20:25 ` Wes Hardaker
1998-10-09 4:13 ` Bud Rogers
1998-10-09 16:09 ` Wes Hardaker
1998-10-09 8:52 ` Kai Grossjohann
1998-10-09 16:39 ` Bud Rogers
1998-10-09 16:50 ` Kai Grossjohann
1998-10-11 15:09 ` Bud Rogers [this message]
1998-10-11 16:31 ` Lars Magne Ingebrigtsen
1998-10-11 17:54 ` Bud Rogers
1998-10-11 17:59 ` Lars Magne Ingebrigtsen
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=m2lnmn879a.fsf@twocups.sirinet.net \
--to=budr@sirinet.net \
/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).