9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] frames & tabs
Date: Thu, 11 Oct 2001 10:08:33 +0200	[thread overview]
Message-ID: <20011011080833.A8E9019A41@mail.cse.psu.edu> (raw)

Since tabs are meant to tabulate and I think that means
keeping clear columns, I was thinking about a change for libframe
to handle tabs like follows:

1. Keep an array of tab positions per frame, each one pointing to the x
where the respective column should start.

2. Adjust each tab position as text gets inserted.


So that if you insert:
	a\tb\tc\n
You get
	a b c
And when later  you insert:
	ab\tcde\n
You get
	a  b   c
	ab cde

The first bad thing is that text before the insertion gets `changed'
by inserting tabs in the following lines.

The second bad thing is that tabs on the left of the line (eg. source code)
would still be handled by inserting N spaces.

Does it all make sense?



             reply	other threads:[~2001-10-11  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  8:08 Fco.J.Ballesteros [this message]
2001-10-11 10:14 okamoto
2001-10-11 11:12 Fco.J.Ballesteros

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=20011011080833.A8E9019A41@mail.cse.psu.edu \
    --to=nemo@gsyc.escet.urjc.es \
    --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).