From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Set debug output width in REPL
Date: Fri, 25 Feb 2011 00:28:19 +0100 [thread overview]
Message-ID: <87bp21qagc.fsf@gnu.org> (raw)
In-Reply-To: 309828.81527.qm@web37907.mail.mud.yahoo.com
Hi,
Mike Gran <spk121@yahoo.com> writes:
>> From:Mark H Weaver <mhw@netris.org>
>
>>
>> Mark wrote:
>> > It seems to me that *width* should not be a global variable, but rather
>> > a per-repl setting. It probably belongs in the options field of the
>> > <repl> record, no? See "repl-default-options" in
>> repl/common.scm.
[...]
> How common is the use case where REPLs for a single Guile session appear
> in terminals of different width?
Think of ‘--listen’.
>> Mark also wrote:
>> Better yet, maybe it should be an optional attribute of the output port,
>> which would allow pretty-print and truncated-print to use it as well.
>> Output ports attached to terminals could determine the terminal width
>> from the OS, on systems that support it.
I like the idea of using the terminal’s width, but I dislike the idea of
having it a property of the port, since it really seems orthogonal to me.
> [...] If one wanted to have a port automatically
> query its terminal for the width, one could either (IIRC) catch the SIGWINCH
> signalor could call a getenv/tget function before printing a pretty-print or
> truncated-print.
How about having a per-REPL setting that’s automatically set to the
terminal’s width by default?
What’s the exact call to get the width?
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-02-24 23:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 22:55 Set debug output width in REPL Mike Gran
2011-02-24 23:28 ` Ludovic Courtès [this message]
2011-02-26 9:17 ` Mark H Weaver
2011-03-05 19:18 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2011-02-25 1:43 Mike Gran
2011-02-21 6:02 Mike Gran
2011-02-21 16:12 ` Mark H Weaver
2011-02-21 16:36 ` Mark H Weaver
2011-03-04 10:17 ` Andy Wingo
2011-03-05 13:26 ` Ludovic Courtès
2011-03-05 19:01 ` 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=87bp21qagc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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).