From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme tabs to spaces
Date: Tue, 6 Dec 2005 12:37:40 -0800 [thread overview]
Message-ID: <3a99f85f52ccb40cae843d2b3de9063a@9netics.com> (raw)
In-Reply-To: <20051206190637.GB4200@sigint.cs.purdue.edu>
>> Is there some automatic tab conversion code somewhere in Acme? Where
>> would be the sane place to put such a thing? (yes, I already know
>> there is no sane place for such a thing...)
>
> Okay, I'll ask the obvious-- why not an en- and de-tabbing file server?
Kwel!!! it should read emacs style headers and figure out what the
tabbing should be on reads and on writes it should reduce multiple
consecutive spaces to one, to save space! perhaps it could have
auto-capitalization for '\.([0-9]|man)$' files!
i'm joking of course.
next prev parent reply other threads:[~2005-12-06 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 19:06 plan9
2005-12-06 20:37 ` Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 18:43 Paul Lalonde
2005-12-06 18:46 ` andrey mirtchovski
2005-12-06 18:54 ` Russ Cox
2005-12-06 18:55 ` Rob Pike
2005-12-06 20:25 ` David Leimbach
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=3a99f85f52ccb40cae843d2b3de9063a@9netics.com \
--to=9nut@9netics.com \
--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).