At 13:13 -0500 7/27/11, David Kelly wrote:
>On Wed, Jul 27, 2011 at 12:04:32PM -0600, Doug McNutt wrote:
>>
>> Just in case anyone at Bare Bones cares:
>>
>> While you're making tab width adjustable on a per file basis it would
>> really be great if you could arrange for tab stops as in a real
>> typewriter. I am continually frustrated with columnar data that
>> demands a wide column on the left side - full names for example -
>> followed by a couple of small width columns like date and $. Multiple
>> tab characters cannot be used because the final destination of the
>> file won't accept them.
>>
>> The alternative is a full fledged spreadsheet but I really don't need
>> that just to look at, yeah and modify, the data.
>
>Sounds as if you are asking to further blur the difference between a
>text editor and a word processor.
>
>Am not sure if Nisus still behaves the way it originally did, but it was
>a word processor that left the data fork as pure text while putting all
>formatting metadata in the resource fork. Originators of QUED/M, which
>for me was replaced by BBEdit.
I still use Nisus 5 or so on this OS 9 box. As of OS 10 Nisus became just
another markup based word processor. Really good for right to left Arabic with
included left to right Arabic numbers..
I even have a preset resource file into which I can redirect a data fork that
is an assembly language listing for a 68HC11 microprocessor. Variable width
tabs are really nice for that. I can even word wrap comments into new lines
that begin at the rightmost tab.
I'd really rather use BBEdit on Apple's OS 10. (Which sort of keeps this on
topic.)
--
Fe++
// \
Fe++ Fe++
| ||
Fe++ Fe++
\\ /
Fe++
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
