unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: Gnus <ding@gnus.org>
Subject: Re: hard-newline changes in lisp/gnus/message.el
Date: Sat, 19 Nov 2005 14:07:11 -0500	[thread overview]
Message-ID: <87sltstq1s.fsf@stupidchicken.com> (raw)
In-Reply-To: <v9k6f5sw13.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 18 Nov 2005 18:31:04 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> 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.

Sorry, I wasn't aware of the synching.

> 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'.

Why not:

(if (not (boundp hard-newline))
    (defvar hard-newline (propertize "\n" 'hard t 'rear-nonsticky '(hard))))

  parent reply	other threads:[~2005-11-19 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 17:31 hard-newline changes in lisp/gnus/message.el Reiner Steib
2005-11-19 11:20 ` Romain Francoise
2005-11-20  2:51   ` Sam Steingold
2005-11-20  3:33   ` Chong Yidong
2005-11-19 19:07 ` Chong Yidong [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sltstq1s.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).