Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Oort Gnus v0.17 is released
Date: Wed, 02 Apr 2003 20:51:45 -0600	[thread overview]
Message-ID: <u4r5gqon2.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <m3of3q3uql.fsf@peorth.gweep.net>

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> * Kevin Greiner <kgreiner@xpediantsolutions.com>  on Tue, 01 Apr 2003
> | It's in gnus-start.el (CVS rev 6.70), it's post 0.17.
>
> I was just making sure that it was not being set explicitly somewhere in
> 0.17 or earlier.  It is not.  The default value in XEmacs is `t'.  This
> confuses me, because I cannot determine why the the newlines are not being
> escaped.
>
> | When I evaluate the following form, I see "a\nb" inserted after the
> | form.  What do you see?  Better yet, what do you need to do to make
> | prin1 echo the string just as it was typed in the form?
>
> | (let ((print-escape-newlines t))
> |   (prin1 "a\nb" (current-buffer))
> |   nil)
>
> From *scratch*, C-j at the end of each form:
>
> ,-----
> | (let ((print-escape-newlines t))
> |   (prin1 "a\nb" (current-buffer))
> |   nil)
> | "a\nb"nil
> | 
> | (let ((print-escape-newlines nil))
> |   (prin1 "a\nb" (current-buffer))
> |   nil)
> | "a
> | b"nil
> `-----
>
> | BTW, I found print-escape-newlines using apropos <RET> print-
> | <RET>. If you do a similar search, you may find other formatting
> | controls that are local to XEmacs.
>

OK, I'll admit that I'm completely confused.  The new code uses prin1
with print-escape-newlines set so the problem must not be literal
newline characters in the strings.  I'm going to download the 0.15 to
see if I can ID the differences before reverting my prior post.

As a fallback, could you post a sample from your .newsrc.eld
highlighting the 0.17 discrepency for me.

Thanks
Kevin




  reply	other threads:[~2003-04-03  2:51 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
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 [this message]
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=u4r5gqon2.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).