unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Set debug output width in REPL
Date: Sat, 05 Mar 2011 14:18:31 -0500	[thread overview]
Message-ID: <87mxl91im0.fsf@netris.org> (raw)
In-Reply-To: <87bp21qagc.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 25 Feb 2011 00:28:19 +0100")

ludo@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 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.

I agree that it's not a perfect solution, but can you propose a better
one that might reasonably be adopted in practice?

Unfortunately, if we punt on this for want of perfection, we're likely
to end up with a nearly pessimal solution: each individual module that
needs to format output for fixed-width character displays will end up
with its own half-baked solution, such as the one just applied.

Ports are already very far from the simple and elegant ideas that
comprise most of Scheme, and they already include much functionality
that should be orthogonal.  Which is worse?  To add one more optional
attribute to ports, or to have several inconsistent and inflexible
notions of terminal width floating around the rest of the system?

     Mark



  parent reply	other threads:[~2011-03-05 19:18 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
2011-02-26  9:17   ` Mark H Weaver
2011-03-05 19:18   ` Mark H Weaver [this message]
  -- 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=87mxl91im0.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).