From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Miles Bader <miles@gnu.org>, Gnus <ding@gnus.org>,
Emacs development <emacs-devel@gnu.org>
Subject: hard-newline changes in lisp/gnus/message.el
Date: Fri, 18 Nov 2005 18:31:04 +0100 [thread overview]
Message-ID: <v9k6f5sw13.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
when changing lisp/gnus/*.el, please keep in mind that this directory
is synced by Miles Bader with the (primary) Gnus repository on
gnus.org in order to simplify the process of including a new stable
Gnus version in Emacs. The stable version of Gnus (the v5-10 branch
in Gnus CVS) should be identical[1] to the version in Emacs CVS and it
should work with Emacs 20.7 and up and XEmacs 21.1 and up.
It would be nice to discuss possibly controversial changes on
emacs-devel and ding@gnus.org (Gnus development list) before
committing.
As for `hard-newline': Obviously `hard-newline' is not defined in
Emacs < 22. I'm not sure what's the best way to deal with this. I'd
suggest to define `message-hard-newline' in `message.el' as follows
and use it instead of `hard-newline'.
(defvar message-hard-newline
(if (featurep 'xemacs)
"\n" ;; Or better code for XEmacs
(if (boundp 'hard-newline)
hard-newline
(propertize "\n" 'hard t 'rear-nonsticky '(hard)))))
Or:
(defvar message-hard-newline
(cond ((boundp 'hard-newline) hard-newline)
((fboundp 'propertize)
(propertize "\n" 'hard t 'rear-nonsticky '(hard)))
(t "\n")))
BTW, maybe `hard-newline' should have a doc string?
Bye, Reiner.
[1] Exception: Version number.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next reply other threads:[~2005-11-18 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 17:31 Reiner Steib [this message]
2005-11-19 11:20 ` hard-newline changes in lisp/gnus/message.el Romain Francoise
2005-11-20 2:51 ` Sam Steingold
2005-11-20 3:33 ` Chong Yidong
2005-11-19 19:07 ` Chong Yidong
2005-11-19 20:47 ` 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=v9k6f5sw13.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.