Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill White <billw@wolfram.com>
Subject: Re: Error with function gnus-summary-pipe-output (Was htmlified mail)
Date: 26 Jan 2001 02:17:01 -0600	[thread overview]
Message-ID: <ruo7l3in2wy.fsf@g.wolfram.com> (raw)
In-Reply-To: <m3elxrx8tr.fsf_-_@lohad.darby.net> (Mike Pullen's message of "25 Jan 2001 21:59:12 -0600")

On Thu Jan 25 2001 at 21:59, Mike Pullen <mpullen@midwest.net> said:

    mp> Bill White <billw@wolfram.com> writes:

    >> I'm seeing a lot of this crap nowadays.  Is this MS Lookout!
    >> output?  Sometimes I use html2text - with the article
    >> displayed, type `|' in the Summary buffer and tell it to run a
    >> script.

    mp> When trying to pipe the article output from gnus using '|', I
    mp> get the following backtrace.  Any ideas?

    mp> Oort Gnus v0.01
    mp> XEmacs 21.1 (patch 12) "Channel Islands" [Lucid] (i386-redhat-linux) of Thu Aug 24 2000 on porky.devel.redhat.com
    mp> 200 Leafnode NNTP Daemon, version 1.9.17 running at lohad.darby.net

    mp> Signaling: (wrong-type-argument stringp default)
    mp>   call-process-internal("/bin/bash" "/tmp/mtp/emacs3iG36A" #<buffer "*Shell Command Output*"> nil "-c" default)
    mp>   apply(call-process-internal "/bin/bash" "/tmp/mtp/emacs3iG36A" #<buffer "*Shell Command Output*"> nil ("-c" default))
    mp>   call-process("/bin/bash" "/tmp/mtp/emacs3iG36A" #<buffer "*Shell Command Output*"> nil "-c" default)
    mp>   apply(call-process "/bin/bash" "/tmp/mtp/emacs3iG36A" #<buffer "*Shell Command Output*"> nil ("-c" default))
    mp>   call-process-region(1 2630 "/bin/bash" nil #<buffer "*Shell Command Output*"> nil "-c" default)
    mp>   shell-command-on-region(1 2630 default nil)
    mp>   gnus-summary-save-in-pipe(default)

<grapsing at straws>
The "default" stuff that appears from here on up doesn't happen when I
run `|'.  Maybe it's related to the "No default saver is defined"
message?

Maybe you could customize `gnus-default-article-saver' to be sure it
has a sane value.
</grapsing at straws>

I bet Shenghuo ZHU can fix it!

    mp>   byte-code("..." [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)
    mp>   gnus-article-save(#<buffer " *Gnus Save*"> nil 1)
    mp>   gnus-summary-save-article(nil t)
    mp>   gnus-summary-pipe-output(nil)
    mp>   call-interactively(gnus-summary-pipe-output)

Cheers -

bw
-- 
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."



  reply	other threads:[~2001-01-26  8:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24  9:15 htmlified mail Joakim Hove
2001-01-24 11:38 ` Bill White
2001-01-24 14:06   ` Randal L. Schwartz
2001-01-24 15:03     ` Stainless Steel Rat
2001-01-24 15:22     ` Hannu Koivisto
2001-01-26  3:59   ` Error with function gnus-summary-pipe-output (Was htmlified mail) Mike Pullen
2001-01-26  8:17     ` Bill White [this message]
2001-01-26 13:20       ` ShengHuo ZHU
2001-01-28 20:44         ` James H. Cloos Jr.
2001-01-29  0:35           ` ShengHuo ZHU
2001-01-29  1:49             ` James H. Cloos Jr.
2001-02-06  6:51               ` ShengHuo ZHU
2001-01-26 19:01       ` James H. Cloos Jr.
2001-01-26 19:17         ` ShengHuo ZHU
2001-01-26 22:32           ` James H. Cloos Jr.
2001-01-26 23:00             ` ShengHuo ZHU
2001-01-27 21:17               ` James H. Cloos Jr.
2001-01-27 21:44                 ` ShengHuo ZHU

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=ruo7l3in2wy.fsf@g.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).