From: michael@cadilhac.name (Michaël Cadilhac)
To: ding@gnus.org
Subject: nnimap using shell command.
Date: Tue, 21 Aug 2007 16:05:43 +0200 [thread overview]
Message-ID: <87d4xhkmo8.fsf@lrde.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]
When using `imap-shell-program' (with a nnimap-stream of 'shell), the
process is created `as is' with start-process. The docstring of
start-process says :
If you want to separate standard output from standard error,
invoke the command through a shell and redirect one of them
using the shell syntax.
Well, this is fun, because my distant imapd says the following :
$ imapd
* PREAUTH Ready.
INFO: LOGIN, user=cadilhac, ip=[127.0.0.1], protocol=IMAP
Oh, heck. Gnus is searching for PREAUTH on the INFO line, doesn't found
it, and just wait until the end of time to see what's happening next[1].
Well, I'm not comfortable with the use of `2> /dev/null' on a package
meant to work on Windows, so I propose this more radical change :
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: gnus.patch --]
[-- Type: text/x-patch, Size: 946 bytes --]
--- gnus.texi 09 Aug 2007 16:22:28 +0200 7.241
+++ gnus.texi 21 Aug 2007 15:54:10 +0200
@@ -14254,7 +14254,9 @@
ssh %s imapd
@end example
-The valid format specifier characters are:
+Make sure nothing is interfering with the output of the program, e.g.,
+don't forget to redirect the error output to the void. The valid format
+specifier characters are:
@table @samp
@item s
@@ -16881,8 +16883,10 @@
@vindex imap-shell-program
@vindex imap-shell-host
-For @acronym{IMAP} connections using the @code{shell} stream, the variable
-@code{imap-shell-program} specify what program to call.
+For @acronym{IMAP} connections using the @code{shell} stream, the
+variable @code{imap-shell-program} specify what program to call. Make
+sure nothing is interfering with the output of the program, e.g., don't
+forget to redirect the error output to the void.
@item nnimap-authenticator
@vindex nnimap-authenticator
[-- Attachment #1.3: Type: text/plain, Size: 499 bytes --]
and maybe change imap.el to not wait indefinitely, but just a few
seconds.
Cheers !
Footnotes:
[1] Which is, as we know, that everybody leaves the Restaurant.
--
| Michaël `Micha' Cadilhac | Une erreur peut devenir exacte |
| http://michael.cadilhac.name | selon que celui qui l'a commise |
| JID/MSN: | s'est trompé ou non. |
`---- michael.cadilhac@gmail.com | -- Pierre Dac - --'
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2007-08-21 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 14:05 Michaël Cadilhac [this message]
2007-08-21 20:05 ` Bjørn Mork
2007-08-26 19:53 ` Michaël Cadilhac
2007-08-29 9:06 ` Michaël Cadilhac
2007-08-31 15:18 ` Michaël Cadilhac
2007-08-29 14:48 ` Michaël Cadilhac
2007-08-31 13:54 ` Michaël Cadilhac
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=87d4xhkmo8.fsf@lrde.org \
--to=michael@cadilhac.name \
--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).