From: tomas@fabula.de
Cc: Paul Jarc <prj@po.cwru.edu>, guile-devel@gnu.org
Subject: Re: Unrecognized \ sequences and Elisp
Date: Tue, 27 Jan 2004 17:26:46 +0100 [thread overview]
Message-ID: <20040127162646.GB27194@www> (raw)
In-Reply-To: <1075207814.23541.1113.camel@localhost>
On Tue, Jan 27, 2004 at 01:50:14PM +0100, Roland Orre wrote:
> On Tue, 2004-01-27 at 10:04, Paul Jarc wrote:
> > Then portable programs cannot use other escape sequences, which means
> > that implementations can invent meanings for other escape sequences
> > without breaking portable programs.
[...]
> When I (define foobar "foo\nbar") do I want it to really evaluate to
> "foo
> bar"
> or do I just want it to print a newline when passed through a certain
> write command? For my own I consider the latter the more useful
> approach.
Hmm. I'd rather expect the former (that's what ``all others'', from
C through Elisp settled on).
[...]
Regards
-- tomás
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-27 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 3:37 Fwd: Re: Unrecognized \ sequences and Elisp Roland Orre
2004-01-27 9:04 ` Paul Jarc
2004-01-27 12:50 ` Roland Orre
2004-01-27 16:26 ` tomas [this message]
2004-01-27 17:43 ` Stephen Compall
2004-01-28 17:03 ` Neil Jerram
2004-02-08 19:16 ` Neil Jerram
2004-02-08 22:06 ` Marius Vollmer
2004-02-10 19:27 ` Neil Jerram
2004-02-18 21:10 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2004-01-26 23:26 Neil Jerram
2004-01-27 2:45 ` Paul Jarc
2004-01-27 6:44 ` Stephen Compall
2004-01-27 8:55 ` Paul Jarc
2004-01-28 16:32 ` Neil Jerram
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=20040127162646.GB27194@www \
--to=tomas@fabula.de \
--cc=guile-devel@gnu.org \
--cc=prj@po.cwru.edu \
/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).