From: Timo Lilja <timo.lilja@iki.fi>
Subject: Re: Script output in mail-source directory :prescript
Date: Sat, 13 May 2006 20:04:48 +0300 [thread overview]
Message-ID: <877j4prh3j.fsf@frog.cs.hut.fi> (raw)
In-Reply-To: <m3u08b1gm3.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>Timo Lilja <timo.lilja@hut.fi> writes:
>
>> Nope, It didn't work for me but I modified it a bit and now it works:
>
>Could you send me a diff against the current sources?
Okey, here is the diff against the latest CVS:
Index: mail-source.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mail-source.el,v
retrieving revision 7.17
diff -u -r7.17 mail-source.el5A
--- mail-source.el 30 Apr 2006 09:44:06 -0000 7.17
+++ mail-source.el 13 May 2006 17:02:32 -0000
@@ -685,13 +685,16 @@
(setq script (substring script 0 (match-beginning 0))
background 0))
(setq result
- (call-process shell-file-name nil background nil
+ (call-process shell-file-name nil stderr nil
shell-command-switch script))
- (when (and result
+ (if (and result
(not (zerop result)))
- (set-buffer stderr)
- (message "Mail source error: %s" (buffer-string)))
- (kill-buffer stderr)))
+ (progn
+ (split-window-vertically)
+ (other-window 1)
+ (switch-to-buffer stderr)
+ (message "Mail source error: %s" (buffer-string)))
+ (kill-buffer stderr))))
;;;
;;; Different fetchers
Just occured to me that using routines from gnus-win.el might make
this task a bit easier.
--
Timo Lilja
"It's a 106 miles to Chicago. We've got a full tank of gas,
half a pack of cigarettes, it's dark, and we're wearing sunglasses."
prev parent reply other threads:[~2006-05-13 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 21:20 Timo Lilja
2006-04-23 14:09 ` Lars Magne Ingebrigtsen
2006-04-26 5:56 ` Timo Lilja
2006-04-30 10:51 ` Lars Magne Ingebrigtsen
2006-05-13 17:04 ` Timo Lilja [this message]
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=877j4prh3j.fsf@frog.cs.hut.fi \
--to=timo.lilja@iki.fi \
/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).