From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: David Z Maze <dmaze@MIT.EDU>
Subject: Re: smtpmail.el: set-buffer-file-coding-system takes too many args
Date: Sat, 06 Jan 2007 21:11:25 +0100 [thread overview]
Message-ID: <v9vejjrk42.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87d55svxxu.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sat\, 06 Jan 2007 18\:59\:09 +0100")
On Sat, Jan 06 2007, Simon Josefsson wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> IIRC, smtpmail.el is also included with XEmacs. Simon, is
>> `smtpmail.el' (from Emacs CVS) supposed to work with XEmacs without
>> modifications?
>
> No. There are several modifications between XEmacs and Emacs
> smtpmail.el, alas.
>
>> If so `smtpmail.el' should probably not use the NOMODIFY argument or
>> provide some compatibility code.
>
> XEmacs users should use the smtpmail.el from mail-lib, there should be
> no reason to use the Emacs CVS stuff (if there is, a bug report would
> be most welcome!).
What do you suggest for contrib/smtpmail.el? As `contrib/smtpmail.el'
should only be used with Emacs 21, we probably can simply remove the
NOMODIFY argument (and add a comment to explain it).
Suggestion (similar for the second location):
--8<---------------cut here---------------start------------->8---
--- smtpmail.el 04 Dec 2006 23:32:00 +0100 7.5
+++ smtpmail.el 06 Jan 2007 20:58:24 +0100
@@ -248,7 +248,11 @@
;; buffer, otherwise any write-region invocations (e.g., in
;; mail-do-fcc below) will annoy with asking for a suitable
;; encoding.
- (set-buffer-file-coding-system smtpmail-code-conv-from nil t)
+ ;; (set-buffer-file-coding-system smtpmail-code-conv-from nil t)
+ (set-buffer-file-coding-system smtpmail-code-conv-from nil)
+ ;; This file (`gnus/contrib/smtpmail.el') is only useful for Emacs
+ ;; which doesn't support the thried argument (NOMODIFY) of
+ ;; `set-buffer-file-coding-system'.
(insert-buffer-substring mailbuf)
(goto-char (point-max))
;; require one newline at the end.
--8<---------------cut here---------------end--------------->8---
BTW: Is NOMODIFY really useful here? In both cases,
`set-buffer-file-coding-system' is followed by
`insert-buffer-substring' which will mark the buffer modified anyhow.
What am I missing?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-01-06 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 15:30 David Z Maze
2007-01-06 14:50 ` Reiner Steib
2007-01-06 17:59 ` Simon Josefsson
2007-01-06 20:11 ` Reiner Steib [this message]
2007-01-07 10:12 ` Simon Josefsson
2007-01-07 12:07 ` Reiner Steib
2007-01-08 8:54 ` Simon Josefsson
2007-01-07 12:09 ` Reiner Steib
2007-03-24 12:30 ` Reiner Steib
2007-03-24 17:07 ` Eli Zaretskii
2007-03-24 19:18 ` Reiner Steib
2007-03-25 2:14 ` Miles Bader
2007-03-31 21:18 ` Reiner Steib
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=v9vejjrk42.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=dmaze@MIT.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).