From: Darrell Stitt <darrellstitt@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] python indent acme proportional fonts ah joy
Date: Fri, 5 Jan 2007 21:56:51 +1100 [thread overview]
Message-ID: <459E2EF3.7010608@gmail.com> (raw)
In-Reply-To: <599f06db0701050242r25680c35j26d7763efb49545f@mail.gmail.com>
mixing tabs and spaces is kind of like hitting your head against the
wall: causes unnecessary headaches.
the solution? don't do that.
You either chase semicolons and {} in C or just make the whitespace neat
in python.
Gorka guardiola wrote:
> ¿Isn't cut & paste fun in python?, specially if you have half of the
> files with code
> indented with tabs and the other half with spaces like the Xen stuff did
> the last time I looked into it. Invisible syntax rocks!!.
>
>
> On 1/5/07, ron minnich <rminnich@gmail.com> wrote:
>> reminiscent of the 'free your mind Luke' discussion a few years ago on
>> indents in code and Acme and fonts and ...
>>
>> I'm finding that I am counting spaces in acme when I get the
>> occasional python 'unindent' error. You may think those columns are
>> aligned, but that's just the proportional font showing.
>>
>> Guess I gotta find a fixed font for editing in acme.
next prev parent reply other threads:[~2007-01-05 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 3:41 ron minnich
2007-01-05 5:26 ` Russ Cox
2007-01-05 6:44 ` Skip Tavakkolian
2007-01-05 6:59 ` Bruce Ellis
2007-01-05 10:42 ` Gorka guardiola
2007-01-05 10:56 ` Darrell Stitt [this message]
2007-01-05 14:30 ` Brantley Coile
2007-01-05 17:44 ` geoff
2007-01-05 17:52 ` Paul Lalonde
2007-01-05 17:54 ` Gorka guardiola
2007-01-05 14:15 mattmobile
2007-01-05 14:32 ` Brantley Coile
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=459E2EF3.7010608@gmail.com \
--to=darrellstitt@gmail.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).