9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] handling tabs in text frames
Date: Sun, 26 Aug 2007 22:33:26 +0200	[thread overview]
Message-ID: <8ccc8ba40708261333k4b5c5a38me30920ef188c0f06@mail.gmail.com> (raw)

Hi,

I'm considering an alternative to the current tab behaviour in text frames.
I'm tired of adding/removing tabs to keep adt declarations aligned, and I think
the machine should do it, not me. Thus, for a experimental implementation
for text frames I'm playing with now, I plan
to implement tab handling  as follows:

1.
Tabs get a default width, say 4 chars, but their actual width depends
on what is found
on lines of text before and after the tab considered. That is, their
width will grow to
actually tabulate the text shown.
For example, the tabs in
a \t b
c \t d
e \t f \t g
will make three aligned columns, no matter the widths of a ... g.

2.
Tabs right after a new line will be a exception in that why will have
a fixed width and will
not be subject to this rule.

One minor detail is that my aim is to make empty lines boundaries
regarding tabulation,
so that not all the file has to be tabulated according to the same widths.

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

thanks


             reply	other threads:[~2007-08-26 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 20:33 Francisco J Ballesteros [this message]
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
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=8ccc8ba40708261333k4b5c5a38me30920ef188c0f06@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).