From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: plan9port: recent changes
Date: Mon, 14 Feb 2005 13:03:08 -0800 [thread overview]
Message-ID: <66d43fa513e8fedebd08c3e847848313@9netics.com> (raw)
In-Reply-To: <ee9e417a050214124956d47a0b@mail.gmail.com>
Is anyone working on a win32 port? 9pm is showing
its age (but still better than cmd or cygwin).
>> i don't like autoindent ... it always seems to do what i don't
>> want it to do, the tab key is big, and i don't write deeply
>> nested code. but if you do - fine ... make it an option (i hate
>> thousands of options too).
>
> it's not the usual "guess where my cursor should be" autoindent.
> when you type newline, it initializes the new line by copying the
> leading white space from the previous line. it's more of a
> persistent indent than autoindent. in any case, it's the first one
> i've ever used that felt natural.
next prev parent reply other threads:[~2005-02-14 21:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 0:41 [9fans] " Russ Cox
2005-02-14 19:09 ` [9fans] " Russ Cox
2005-02-14 20:31 ` Bruce Ellis
2005-02-14 20:49 ` Russ Cox
2005-02-14 21:03 ` Skip Tavakkolian [this message]
2005-02-15 3:28 ` Andrew Simmons
2005-02-15 3:39 ` Russ Cox
2005-02-15 7:20 ` Tiit Lankots
2005-02-15 9:51 ` David Tolpin
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=66d43fa513e8fedebd08c3e847848313@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).