From: Bill White <billw@wolfram.com>
Cc: ding@gnus.org
Subject: problem with fix-transposed-characters/sig-quote/gnus
Date: 11 Feb 2000 14:55:14 -0600 [thread overview]
Message-ID: <ruosnyzfoi5.fsf@g.wolfram.com> (raw)
Hi John -
Just a note to let you know of a potential problem (and solution) when
fix-transpose-characters mixes with packages that parse email headers.
I found a problem sending mail to local folks with gnus when using
your fix-transpose-characters and Trey Jackson's sig-quote mode. When
my To: line looks like this
To: Ryan Tokarek <tokarek>
it's changed to this just before it's mailed:
To: Ryan Tokarek <tokare>k
Trey's package parses the headers using functions in sendmail.el,
including, in this case, 'mail-to', which executes (expand-abbrev):
,----
| (defun mail-to ()
| "Move point to end of To-field."
| (interactive)
| (expand-abbrev)
| (mail-position-on-field "To"))
`----
Since I'm using fix-transpose-characters by hooking into abbrev:
,----
| (add-hook 'pre-abbrev-expand-hook 'fix-transposed-characters)
`----
that makes mail-to run fix-transpose-characters with point at the end
of the To: line. That winds up changing <tokarek> to <tokare>k.
I'm getting around the problem with this advice in my .gnus:
(defadvice message-send-and-exit (around transpose-toggle activate compile)
"Turn off John Wiegley's fix-transposed-characters when sending mail."
(remove-hook 'pre-abbrev-expand-hook 'fix-transposed-characters)
ad-do-it
(add-hook 'pre-abbrev-expand-hook 'fix-transposed-characters))
In other news, eshell is a heck of a lot of fun. Thanks!
Take care -
bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."
reply other threads:[~2000-02-11 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ruosnyzfoi5.fsf@g.wolfram.com \
--to=billw@wolfram.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).