Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: mail-extract-address-components vs gnus-...
Date: 03 Nov 1997 14:40:43 -0500	[thread overview]
Message-ID: <glmd8khix50.fsf@linus.mitre.org> (raw)
In-Reply-To: <kigd8knjlnp.fsf@jagor.srce.hr>

Hrvoje Niksic <hniksic@srce.hr> writes:

> My conclusion, too.  If you can produce a patch to mail-extr.el that
> removes this "feature" without breaking anything else, the XEmacers
> will apply it, I think.

Done.  This will leave `&' alone in most cases, instead of
substituting.  In order to make anyone who thinks that we should
perpetuate old UNIX brokenness happy, it will do the substitution iff
the `&' is the last word in the Full Name.

e.g. (with this patch):

(mail-extract-address-components "Charlie & <root@notcom.com>")
("Charlie Root" "root@notcom.com")

(mail-extract-address-components "Charlie & Joe <root@notcom.com>")
("Charlie & Joe" "root@notcom.com")
 
If anyone sees anything wrong with this behavior, or with the patch
itself, please let me know.  Otherwise, I would like to suggest that
this be incorporated into Emacs and XEmacs.

*** mail-extr.el.orig	Mon Nov  3 12:59:15 1997
--- mail-extr.el	Mon Nov  3 14:37:12 1997
***************
*** 118,123 ****
--- 118,127 ----
  
  ;;; Change Log: 
  ;; 
+ ;; Mon Nov  3 14:35:24 1997  Justin Sheehy (justin@linus.mitre.org)
+ ;;
+ ;;      * only substitute for & when at end of Full Name
+ ;;
  ;; Thu Feb 17 17:57:33 1994  Jamie Zawinski (jwz@lucid.com)
  ;;
  ;;	* merged with jbw's latest version
***************
*** 1593,1606 ****
  	 ((and (or (bobp)
  		   (eq ?\  (preceding-char)))
  	       (looking-at "&\\( \\|\\'\\)"))
! 	  (mail-extr-delete-char 1)
! 	  (capitalize-region
! 	   (point)
! 	   (progn
! 	     (insert-buffer-substring canonicalization-buffer
! 				      mbox-beg mbox-end)
! 	     (point)))
! 	  (setq disable-initial-guessing-flag t)
  	  (setq word-found-flag t))
  	 
  	 ;; Handle *Stupid* VMS date stamps
--- 1597,1613 ----
  	 ((and (or (bobp)
  		   (eq ?\  (preceding-char)))
  	       (looking-at "&\\( \\|\\'\\)"))
!           (if (looking-at "&$")
!               (progn
!                 (mail-extr-delete-char 1)
!                 (capitalize-region
!                  (point)
!                  (progn
!                    (insert-buffer-substring canonicalization-buffer
!                                             mbox-beg mbox-end)
!                    (point)))
!                 (setq disable-initial-guessing-flag t))
!             (forward-char))
  	  (setq word-found-flag t))
  	 
  	 ;; Handle *Stupid* VMS date stamps


-- 
Justin Sheehy

In a cloud bones of steel.
  



      parent reply	other threads:[~1997-11-03 19:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-26  0:01 Justin Sheehy
1997-10-30 13:00 ` Hrvoje Niksic
1997-10-30 14:36   ` Justin Sheehy
1997-10-30 22:04     ` Joe Wells
1997-10-30 22:09       ` Justin Sheehy
1997-10-30 23:10       ` Hrvoje Niksic
1997-10-31 15:08         ` Joe Wells
1997-10-31 15:13           ` Hrvoje Niksic
1997-10-31  9:28       ` Per Abrahamsen
     [not found]     ` <kigd8knjlnp.fsf@jagor.srce.hr>
1997-11-03 19:40       ` Justin Sheehy [this message]

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=glmd8khix50.fsf@linus.mitre.org \
    --to=justin@linus.mitre.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).