From: Georges KO <gko@gko.net>
Subject: Re: Would like to display part of body in subject in summary buffer
Date: 17 May 2001 20:58:44 +0800 [thread overview]
Message-ID: <01May17.203910cst.119054@ns.alcatel.com.tw> (raw)
In-Reply-To: <vafk83gjr9s.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "17 May 2001 10:47:43 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Can you run procmail or somesuch to move the Summary line from the
> body to the header for these messages?
I don't know, I use NT Emacs... I'll take a look. It seems like a
good idea, as many of these messages are quite long so it would be
horrible when generating summary.
Thanks for the clue.
--
Georges KO, Taipei, Taiwan gko@gko.net 2001-05-17
next prev parent reply other threads:[~2001-05-17 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 3:46 Georges KO
2001-05-17 8:47 ` Kai Großjohann
2001-05-17 12:58 ` Georges KO [this message]
2001-05-17 13:03 ` Georges KO
2001-05-17 12:49 ` Kai Großjohann
2001-05-18 7:05 ` Horst Winkler
2001-05-17 13:19 ` Roland Mas
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=01May17.203910cst.119054@ns.alcatel.com.tw \
--to=gko@gko.net \
/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).