From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Uhm
Date: 26 Nov 1997 10:30:33 +0100 [thread overview]
Message-ID: <m3ra8480jq.fsf@sparky.gnus.org> (raw)
In-Reply-To: Steinar Bang's message of "26 Nov 1997 10:03:46 +0100"
Steinar Bang <sb@metis.no> writes:
> > I just wrote a command to keep the X-Sent line updated in the article
> > buffer. Continually. (Timers, you know.)
>
> OK... so I'm stupid: what does this mean?
I find that I don't want to know when an article was written. The
Date header is useless for me. What I want to know is how long ago
the article was written, so I have `gnus-article-date-lapsed' in
`gnus-article-display-hook'.
The new function keeps the result of this function updated
continually, to let you feel the passage of time, pulling you into the
future. Endlessly pulling you into the future.
(Oops. I'm quoting Laurie Anderson songs. And Anderson was quoting
Fassbinder. Someone please help.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1997-11-26 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-25 17:10 Uhm Lars Magne Ingebrigtsen
1997-11-25 19:56 ` Uhm Dan Christensen
1997-11-26 7:32 ` Uhm Lars Magne Ingebrigtsen
1997-11-26 9:03 ` Uhm Steinar Bang
1997-11-26 9:30 ` Lars Magne Ingebrigtsen [this message]
1997-11-26 15:41 ` Uhm Sean Doran
1997-11-26 16:07 ` Uhm Neil Crellin
1997-11-26 17:33 ` Uhm Wes Hardaker
1997-11-27 8:29 ` Uhm Steinar Bang
1997-11-27 16:12 ` Uhm Alan Shutko
1997-11-27 16:32 ` Uhm Lars Magne Ingebrigtsen
[not found] ` <6f4t50j9c6.fsf@bavur.dna.lth.se>
1997-11-27 8:26 ` Uhm Steinar Bang
1997-11-26 15:01 ` Parse error.. Uhm Andy Eskilsson
1997-11-26 15:45 ` Lars Magne Ingebrigtsen
1998-02-21 23:34 Uhm Lars Magne Ingebrigtsen
1998-02-22 3:19 ` Uhm Hrvoje Niksic
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=m3ra8480jq.fsf@sparky.gnus.org \
--to=larsi@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).