9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] handling tabs in text frames
Date: Mon, 27 Aug 2007 05:58:41 +0200	[thread overview]
Message-ID: <63330f0266e7f46008a594acba9415ec@proxima.alt.za> (raw)
In-Reply-To: <8ccc8ba40708261333k4b5c5a38me30920ef188c0f06@mail.gmail.com>

> I'd like to hear what others think regarding this behaviour before
> actually implementing
> it.

I think you ought to just go for it.  I know that the present
implementation of tabs is inadequate, but enough of a convention for
everyone to have adjusted to it.  A new implementation will either be
easier or more difficult to get tuned into and only time will tell
which one applies.  That's what happens when the object of one's
attention is capable of extraordinary feats of adaptability.

As for the proposal itself, it sounds useful, very much so.  Is it
likely that you'll be able to default the traditional tab expansion
(8-space _equivalent_ I have to partially agree with Erik) for
fixed-width font and the new technique for variable width font, with a
switch to select the alternative?

++L

PS: Personally, I think my next "alphabet" will have no such concept
as "tabs", when last did anyone get a typewriter to work properly with
those in the first place?  So why do we carry the concept where it
belongs even less?



  parent reply	other threads:[~2007-08-27  3:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 20:33 Francisco J Ballesteros
2007-08-26 21:15 ` erik quanstrom
2007-08-27  1:15   ` Anthony Sorace
2007-08-27  1:24     ` erik quanstrom
2007-08-27  1:38       ` Uriel
2007-08-27  2:54       ` Anthony Sorace
2007-08-27  3:58 ` lucio [this message]
2007-09-03 15:26 ` y i y u s 

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63330f0266e7f46008a594acba9415ec@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).