From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: cron & emacs -batch -l ~/.emacs -f gnus-agent-batch
Date: Wed, 14 Aug 2002 22:11:19 +0200 [thread overview]
Message-ID: <iluvg6dnqu0.fsf@latte.josefsson.org> (raw)
In-Reply-To: <8765yd1bwv.fsf@pale.loc> (Alexander Kotelnikov's message of "Wed, 14 Aug 2002 23:24:32 +0400")
Alexander Kotelnikov <sacha@giotto.sj.ru> writes:
> I got troubles while putting
> emacs -batch -l ~/.emacs -f gnus-agent-batch
> in my crontab. The trouble is that when using (nnimap-stream shell)
> emacs receives hangup when cron runs this command. It is easyly
> reproduceble from shell, just run
> emacs -batch -l ~/.emacs -f gnus-agent-batch </dev/null
>
> This is rather strange, since this command does not require any
> interaction with user, so no terminal is really needed.
Does the patch below together with (setq imap-process-connection-type
t) help? Just a long shot.
--- imap.el.~6.39.~ 2002-08-12 23:09:16.000000000 +0200
+++ imap.el 2002-08-14 22:09:08.000000000 +0200
@@ -215,7 +213,8 @@
:type '(repeat string))
(defcustom imap-process-connection-type nil
- "*Value for `process-connection-type' to use for Kerberos4 and GSSAPI."
+ "*Value for `process-connection-type' to use for process streams.
+The \"process streams\" include Kerberos4, GSSAPI and shell."
:group 'imap
:type 'boolean)
@@ -681,6 +686,7 @@
(let* ((port (or port imap-default-port))
(coding-system-for-read imap-coding-system-for-read)
(coding-system-for-write imap-coding-system-for-write)
+ (process-connection-type imap-process-connection-type)
(process (start-process
name buffer shell-file-name shell-command-switch
(format-spec
next prev parent reply other threads:[~2002-08-14 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 19:24 Alexander Kotelnikov
2002-08-14 20:11 ` Simon Josefsson [this message]
2002-08-14 21:55 ` Alexander Kotelnikov
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=iluvg6dnqu0.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).