l...@gnu.org (Ludovic Courtès) writes:
>>> 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 O
On Sat 05 Mar 2011 14:26, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo writes:
>
>> On Mon 21 Feb 2011 07:02, Mike Gran writes:
>>
>>> I find that the backtrace output in the REPL is too constrained
>>> my verbose code. The attached patch would let one set the
>>>
>>> width of the backt
Hi,
Andy Wingo writes:
> On Mon 21 Feb 2011 07:02, Mike Gran writes:
>
>> I find that the backtrace output in the REPL is too constrained
>> my verbose code. The attached patch would let one set the
>>
>> width of the backtrace and locals meta-commands.
>>
>> What do you think?
>
> Applied, t
Hi Mike,
On Mon 21 Feb 2011 07:02, Mike Gran writes:
> I find that the backtrace output in the REPL is too constrained
> my verbose code. The attached patch would let one set the
>
> width of the backtrace and locals meta-commands.
>
> What do you think?
Applied, thanks. I hemmed and hawed a
l...@gnu.org (Ludovic Courtès) writes:
>> [...] 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-R
> From:Ludovic Courtès
> 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?
The lightweight way is to just check for the COLUMNS environment variable.
Most of the xterm-like terminals set COLUMNS when a p
Hi,
Mike Gran writes:
>> From:Mark H Weaver
>
>>
>> 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
>> > record, no? See "repl-default-options" in
>> repl/common.scm.
[...]
>
> From:Mark H Weaver
>
> 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
> > record, no? See "repl-default-options" in
> repl/common.scm.
For my personal case, when I run the REPL
I 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
> record, no? See "repl-default-options" in repl/common.scm.
Better yet, maybe it should be an optional attribute of the output port,
which wo
Mike Gran writes:
> I find that the backtrace output in the REPL is too constrained
> my verbose code. The attached patch would let one set the
> width of the backtrace and locals meta-commands.
> index d4b3e4a..40d720d 100644
> --- a/module/system/repl/command.scm
> +++ b/module/system/repl/co
Hi-
I find that the backtrace output in the REPL is too constrained
my verbose code. The attached patch would let one set the
width of the backtrace and locals meta-commands.
What do you think?
-MikeFrom 781bcc2783709e76591cd354f4976f02eb284526 Mon Sep 17 00:00:00 2001
From: Michael Gran
Dat
11 matches
Mail list logo