From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: Oort Gnus v0.17 is released
Date: Tue, 01 Apr 2003 10:44:56 -0500 [thread overview]
Message-ID: <m33cl2usqv.fsf@peorth.gweep.net> (raw)
In-Reply-To: <uistyn6oc.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Mon, 31 Mar 2003 23:11:15 -0600")
* Kevin Greiner <kgreiner@xpediantsolutions.com> on Tue, 01 Apr 2003
| Actually, it appears that this is an XEmacs incompatibility (you did, I
| believe, mention using XEmacs). In Emacs, the read method handles
| newline characters as either ignorable whitespace or a literal character
| (when part of a string). It would seem, from your comments, that XEmacs
| uses a different rule.
21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
compiled with
--with-scrollbars=lucid --with-dialogs=no --with-toolbars=no
--with-menubars=no --with-database=no --with-ldap=no --with-gpm=no
--with-xpm=no --with-xface=no --with-gif=no --with-jpeg=no --with-png=no
--with-tiff=no --with-sound=no --with-mule=no
which is about as stripped down as XEmacs can get without lots of things
breaking.
| I've bound print-escape-newlines to t so that the newline characters
| are now replaced by \n escape sequences.
Hm. print-escape-newlines is t in my current Oort v0.15 session. I will
try forcing that against v0.17.
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball contains a liquid core,
Minion of Nathan - Nathan says Hi! \ which, if exposed due to rupture, should
PGP Key: at a key server near you! \ not be touched, inhaled, or looked at.
That and five bucks will get you a small coffee at Starbucks.
next prev parent reply other threads:[~2003-04-01 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 18:09 Lars Magne Ingebrigtsen
2003-03-31 21:58 ` Stainless Steel Rat
2003-03-31 22:20 ` Kevin Greiner
2003-03-31 22:34 ` Jack Twilley
2003-04-01 2:07 ` Stainless Steel Rat
2003-04-01 5:11 ` Kevin Greiner
2003-04-01 15:44 ` Stainless Steel Rat [this message]
2003-04-01 16:07 ` Stainless Steel Rat
2003-04-01 16:50 ` Kevin Greiner
2003-04-01 19:04 ` Stainless Steel Rat
2003-04-03 2:51 ` Kevin Greiner
2003-04-04 3:22 ` Stainless Steel Rat
2003-04-01 2:43 ` Lars Magne Ingebrigtsen
2003-03-31 22:53 ` Vasily Korytov
2003-04-01 2:43 ` Lars Magne Ingebrigtsen
2003-04-02 10:20 ` Zack Weinberg
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=m33cl2usqv.fsf@peorth.gweep.net \
--to=ratinox@peorth.gweep.net \
/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).