From: Mark Moll <mmoll@cs.cmu.edu>
Subject: hack of .overview files
Date: 03 Mar 1998 10:59:28 -0500 [thread overview]
Message-ID: <uttbtvnkbof.fsf@gs236.sp.cs.cmu.edu> (raw)
If I am the sender of a message, I'd rather see the recipient than my own
name in the summary. That's how I used to have it configured with VM and MH.
With USENET news that's kinda hard to do, but mail .overview files can be
hacked. That's exactly what I did; a quick and dirty hack:
> diff -c nnheader.el.orig nnheader.el
*** nnheader.el.orig Sun Mar 1 10:25:55 1998
--- nnheader.el Tue Mar 3 10:49:39 1998
***************
*** 205,212 ****
;; From.
(progn
(goto-char p)
! (if (search-forward "\nfrom: " nil t)
! (nnheader-header-value) "(nobody)"))
;; Date.
(progn
(goto-char p)
--- 205,219 ----
;; From.
(progn
(goto-char p)
! (cond ((string-match (user-full-name)
! (if (search-forward "\nfrom: " nil t)
! (nnheader-header-value) "(nobody)"))
! (goto-char p)
! (if (search-forward "\nto: " nil t)
! (concat "To:" (nnheader-header-value)) "To:(nobody)"))
! (t (goto-char p)
! (if (search-forward "\nfrom: " nil t)
! (nnheader-header-value) "(nobody)"))))
;; Date.
(progn
(goto-char p)
(I know the "from" header should only be checked once, but I am a total
elisp illiterate.) Is there any reason why this is a bad idea? If not, is it
worth making this behavior an option?
--
Mark Moll
next reply other threads:[~1998-03-03 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-03 15:59 Mark Moll [this message]
1998-03-03 16:04 ` Stefan Waldherr
1998-03-03 16:42 ` Wes Hardaker
1998-03-03 17:37 ` Per Abrahamsen
1998-03-03 19:55 ` hack of .overview files [take 2] Mark Moll
1998-03-04 11:16 ` Per Abrahamsen
1998-03-05 11:20 ` threading emails (Was: hack of .overview...) Steinar Bang
1998-03-05 13:07 ` Per Abrahamsen
1998-03-07 12:59 ` hack of .overview files [take 2] 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=uttbtvnkbof.fsf@gs236.sp.cs.cmu.edu \
--to=mmoll@cs.cmu.edu \
/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).