Re: [9fans] frames & tabs

Re: [9fans] frames & tabs

[Fco.J.Ballesteros]

For cal, dir listings in acme, etc.

Re: [9fans] frames & tabs

[okamoto]

[-- Attachment #1: Type: text/plain, Size: 80 bytes --]

When do you feel it is neccessary?
Sorry, I have enough point yet.

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 2233 bytes --]

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
Message-ID: <20011011080833.A8E9019A41@mail.cse.psu.edu>

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?

[9fans] frames & tabs

[Fco.J.Ballesteros]

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?