From: Neil Jerram <neil@ossau.uklinux.net>
To: Ian Price <ianprice90@googlemail.com>
Cc: guile-devel@gnu.org
Subject: Re: WRITE & linefeed
Date: Wed, 22 Jun 2011 22:49:55 +0100 [thread overview]
Message-ID: <87fwn1r0xo.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <m3ei2pmrze.fsf@Kagami.home> (Ian Price's message of "Sun, 19 Jun 2011 22:27:49 +0100")
Ian Price <ianprice90@googlemail.com> writes:
> Hello guilers,
>
> There's a small aesthetic issue that's been bothering me for a
> while. Namely, newlines aren't treated like other escape sequences when
> printed with WRITE.
>
> scheme@(guile-user)> (write "\n")
> "
> "scheme@(guile-user)>
>
> Now, I can see why this would be useful when printing multiple line
> strings, but the inconsistency with e.g. "\t\f" irks me. What do the
> rest of you think?
I agree, but I can imagine that there is a case for the current
behaviour too, and it's nice to preserve back-compatibility. Emacs has
`print-escape-newlines', and I guess we need something like that here -
an addition to `print-options'?
Neil
next prev parent reply other threads:[~2011-06-22 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 21:27 WRITE & linefeed Ian Price
2011-06-22 21:49 ` Neil Jerram [this message]
2011-12-04 21:37 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwn1r0xo.fsf@neil-laptop.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.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 read-only IMAP folder(s) and NNTP newsgroup(s).