Gnus development mailing list
 help / color / mirror / Atom feed
From: Sivaram N <nsivaram.net@gmail.com>
To: ding@gnus.org
Subject: Re: any way to timestamp Messages?
Date: Tue, 19 Jun 2007 19:22:41 +0530	[thread overview]
Message-ID: <uir9kgifq.fsf@gmail.com> (raw)
In-Reply-To: <b4m4pl4tafw.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <u4pl5b4h3.fsf@gmail.com> Sivaram N wrote:
>
>> If this feature can be plugged in a future release, at least for some
>> actions especially those involving downloading, refreshing the NG,
>> sending emails....
>
> I've implemented this feature in the right way (maybe), in the
> Gnus CVS trunk.  Now this is controlled by:
>
> ,----
> | `gnus-add-timestamp-to-message'
> |      This variable controls whether to add timestamps to messages that
> |      are issued controlled by `gnus-verbose' and
> |      `gnus-verbose-backends'.  The default value is `nil' which means
> |      never to add timestamp.  If it is `log', add timestamps to only
> |      the messages that go into the `*Messages*' buffer (in XEmacs, it
> |      is the ` *Message-Log*' buffer).  If it is neither `nil' nor
> |      `log', add timestamps not only to log messages but also to the
> |      ones displayed in the echo area.
> `----
>
> I use the following so that it may be t when running Gnus as a
> cron job:
>
> (setq gnus-add-timestamp-to-message (if noninteractive t 'log))
>
> Regards,
>
>

many thanks,  I'll download the CVS snapshot to check it out.

And the sentence

"This variable controls whether to add timestamps to messages that are
issued controlled...."
^^^^^^^^^^^^^^^^^

Is that "issued & controlled" or a small typo.



 sivaram
 -- 




  reply	other threads:[~2007-06-19 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 19:04 Sivaram N
2007-06-18  7:12 ` Katsumi Yamaoka
2007-06-18 16:40   ` Sivaram N
2007-06-19 12:06     ` Katsumi Yamaoka
2007-06-19 13:52       ` Sivaram N [this message]
2007-06-19 23:49         ` Katsumi Yamaoka

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=uir9kgifq.fsf@gmail.com \
    --to=nsivaram.net@gmail.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).