Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: add a gnus-summary-pipe-output-default-command variable
Date: Wed, 09 Jul 2008 20:26:38 +0200	[thread overview]
Message-ID: <kztzeyx6ap.fsf@kafka.physik3.gwdg.de> (raw)
In-Reply-To: <b4mtzf8ecd3.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 02 Jul 2008 20:47:52 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:
> BTW, I've fixed some bugs in relation to the saving articles
> features:

The command `gnus-summary-save-in-pipe' does not work for me
anymore. This is due to the change from `gnus-article-buffer' to
`gnus-save-article-buffer' in l.3965 in gnus-art.el. For example, if I
do something like

(gnus-summary-save-in-pipe "bogofilter -v -n")

in the summary buffer, I get an error because gnus-save-article-buffer
is nil:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  get-buffer(nil)
  get-buffer-window-list(nil nil visible)
  gnus-get-buffer-window(nil visible)
  (let* ((GnusStartBufferWindow ...) (buf gnus-save-article-buffer) (w ...)) (unwind-protect (progn ... ...) (select-window GnusStartBufferWindow)))
  (gnus-eval-in-buffer-window gnus-save-article-buffer (save-restriction (widen) (shell-command-on-region ... ... command nil)))
  gnus-summary-save-in-pipe("bogofilter -vvv -n")

-David



  reply	other threads:[~2008-07-09 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29 18:42 jidanni
2008-06-30  0:35 ` Katsumi Yamaoka
2008-07-01 16:01   ` jidanni
2008-07-02 11:47     ` Katsumi Yamaoka
2008-07-09 18:26       ` David Engster [this message]
2008-07-10  8:56         ` Katsumi Yamaoka
2008-07-10 23:59           ` Katsumi Yamaoka
2008-07-11  7:45             ` David Engster

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=kztzeyx6ap.fsf@kafka.physik3.gwdg.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.org \
    /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).