Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: info-gnus-english@gnu.org
Subject: Re: gnus-agent-fetch in batch mode in a cron job
Date: Fri, 22 Feb 2013 07:10:52 +0100	[thread overview]
Message-ID: <87r4k8lvyr.fsf@free.fr> (raw)
In-Reply-To: <878v6jszx6.fsf@riseup.net>

wgreenhouse@riseup.net (W. Greenhouse)
writes:

> Hi Julien,
>
> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> The subject says it all. I'm fetching news through emacs in batch mode
>> in a cron job but I can't figure out how to get the possible errors
>> through the mails sent by cron.
>>
>> In batch mode emacs output everything that should go to the *Messages*
>> buffer to stderr so cron sends an email each time the job is run, even
>> without any error. I don't want to receive an email when there is no
>> problem. Is there a way to get emacs to send only the error messages to
>> stderr ?
>>
>> Julien.
>
> Yes, this should be a matter of shell redirection.  Cron actually sends
> both stdout and stderr to email, so if you only want stderr, then you
> should redirect stdout to /dev/null.  There isn't a -quiet option or
> similar for Emacs in batch mode, so it's all up to the shell.

From what I understand Emacs outputs the whole *Messages* buffer to
stdout. So there is nothing the shell can do to sort error messages from
information messages. Is that right ?


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2013-02-22  6:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 22:08 Julien Cubizolles
2013-02-20 16:39 ` W. Greenhouse
2013-02-22  6:10   ` Julien Cubizolles [this message]
2013-02-22  6:32     ` W. Greenhouse
     [not found]   ` <mailman.20575.1361513992.855.info-gnus-english@gnu.org>
2013-08-01 12:48     ` Lars Magne Ingebrigtsen

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=87r4k8lvyr.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --cc=info-gnus-english@gnu.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).