From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam's protocol description?
Date: Sat, 10 Jan 2004 18:20:38 +0400 [thread overview]
Message-ID: <200401101420.i0AEKcfJ018210@adat.davidashen.net> (raw)
In-Reply-To: <052401c3d7d7$67989820$0a01a8c0@SOMA>
> > 2 spaces good. 8 spaces better.
>
> s/8 spaces/tab/
You did not understand my intent.
autoindent is not a space smashing stuff. Autoindent is a feature which
places the cursor under the first non-space character of the previous line.
It works with any way of indents' styling; whether they are 8 or 2 or tabs
or spaces.
The 'space smashing stuff' you see in the patch is meant to decrease the traffic
between sam and samterm, while your proposal does the opposite. Hope this helps.
I find it convenient to have editor do it for me; samterm does a handful
of similar things, such as Ctrl-U, Ctrl-W and parentheses matching. I think
it is natural to have autoindent too.
Hope this helps.
David Tolpin
http://davidashen.net/
next prev parent reply other threads:[~2004-01-10 14:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 23:31 David Tolpin
2004-01-09 23:58 ` rob pike, esq.
2004-01-10 0:01 ` David Tolpin
2004-01-10 0:21 ` Scott Schwartz
2004-01-10 7:01 ` Rob Pike
2004-01-10 15:46 ` [9fans] acme vdharani
2004-01-10 16:07 ` rob pike, esq.
2004-01-10 13:01 ` [9fans] Sam's protocol description? David Tolpin
2004-01-10 23:15 ` boyd, rounin
2004-01-10 13:31 ` David Tolpin
2004-01-10 23:44 ` boyd, rounin
2004-01-10 13:53 ` David Tolpin
2004-01-11 0:11 ` boyd, rounin
2004-01-10 14:20 ` David Tolpin [this message]
2004-01-11 0:27 ` boyd, rounin
2004-01-10 15:54 ` boyd, rounin
2004-01-10 6:44 ` Scott Schwartz
2004-01-10 16:54 ` boyd, rounin
2004-01-10 6:49 ` Lucio De Re
2004-01-10 6:59 ` Rob Pike
2004-01-10 17:03 ` boyd, rounin
2004-01-10 16:07 ` rob pike, esq.
2004-01-10 2:30 ddj
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=200401101420.i0AEKcfJ018210@adat.davidashen.net \
--to=dvd@davidashen.net \
--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).