From: prj@po.cwru.edu (Paul Jarc)
Cc: Guile Development <guile-devel@gnu.org>,
Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Unrecognized \ sequences and Elisp
Date: Tue, 27 Jan 2004 03:55:47 -0500 [thread overview]
Message-ID: <m3isixepna.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <xfy65exnb5o.fsf@csserver.evansville.edu>
Stephen Compall <s11@member.fsf.org> wrote:
> BTW, the old \ behavior *is* documented in the manual, see Info node
> `(guile)Backslash Escapes'.
>
> Unrecognized escape sequences are ignored: if the characters `\*'
> appear in a string, they will be translated to the single
> character `*'.
Since that appears in the section on regular expression syntax, not
string syntax, it seems more like description than specification. I
think it'd be best to change that to match the new code.
> To speed up the operation, we changed Emacs to assume that any
> opening delimiter at the left margin is the start of a defun.
So it sounds like this would work, then:
"foo...\
\n(bar...)"
paul
_______________________________________________
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 8:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 23:26 Unrecognized \ sequences and Elisp Neil Jerram
2004-01-27 2:45 ` Paul Jarc
2004-01-27 6:44 ` Stephen Compall
2004-01-27 8:55 ` Paul Jarc [this message]
2004-01-28 16:32 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 3:37 Fwd: " Roland Orre
2004-01-27 9:04 ` Paul Jarc
2004-01-27 12:50 ` Roland Orre
2004-01-27 16:26 ` tomas
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
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=m3isixepna.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.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 read-only IMAP folder(s) and NNTP newsgroup(s).