From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Cc: k.s.matheussen@notam02.no
Subject: \r\n confuses #! !#
Date: Wed, 10 Mar 2004 06:23:45 -0800 [thread overview]
Message-ID: <404F24F1.6000301@ccrma> (raw)
read.c (line 271 in 1.6.4, 286 in CVS):
in skip_scsh_block_comment (SCM port)
if (history == (('\n' << 24) | ('!' << 16) | ('#' << 8) | '\n'))
gets confused if the text editor uses \r\n rather than \n.
(This is possible with emacs, though I'm not sure how).
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2004-03-10 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 14:23 Bill Schottstaedt [this message]
2004-03-21 2:02 ` \r\n confuses #! !# 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=404F24F1.6000301@ccrma \
--to=bil@ccrma.stanford.edu \
--cc=k.s.matheussen@notam02.no \
/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).