From: Kevin Ryde <user42@zip.com.au>
Subject: port-column and carriage return
Date: Fri, 27 Aug 2004 11:29:22 +1000 [thread overview]
Message-ID: <87vff5weq5.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
* ports.c (scm_getc, scm_lfwrite): Reset port-column for \r.
This will be good for printing an updating status on a tty, where you
use #\cr to go back and rewrite the line.
Bell and backspace might be good too.
[-- Attachment #2: ports.c.cr.diff --]
[-- Type: text/plain, Size: 520 bytes --]
--- ports.c.~1.193.~ 2004-08-20 11:00:31.000000000 +1000
+++ ports.c 2004-08-23 15:18:44.000000000 +1000
@@ -1013,6 +1013,9 @@
case '\n':
SCM_INCLINE (port);
break;
+ case '\r':
+ SCM_ZEROCOL (port);
+ break;
case '\t':
SCM_TABCOL (port);
break;
@@ -1056,6 +1059,9 @@
if (*ptr == '\n') {
SCM_INCLINE(port);
}
+ else if (*ptr == '\r') {
+ SCM_ZEROCOL(port);
+ }
else if (*ptr == '\t') {
SCM_TABCOL(port);
}
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-08-27 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 1:29 Kevin Ryde [this message]
2004-09-07 0:22 ` port-column and carriage return Kevin Ryde
2004-09-07 19:51 ` Rob Browning
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=87vff5weq5.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).