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.
:-=)
ron
You can toggle a window into and out of fixed width mode
by typing Font in the tag and then executing it (middle click).
Also, as long as the lines only contain leading spaces you should see
alignment the same in the variable-width font -- the width of a space
is still constant. It is just a smaller constant in the variable-width font,
so sometimes it is hard to see whether you are looking at six spaces or seven.
Also, try acme -a. It really helps in cases like these.
It takes about a day to get used to, but then you won't go anywhere without it.
Russ
does python require a character in the 6th column for line
continuation? perhaps somebody could write ratpy (by analogy to
ratfor) to work around these limitations.
brucee
--
- curiosity sKilled the cat
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 <rmin...@gmail.com> wrote:
What retrograde reasoning led to abandoning free form input
to a parser.
(That's not meant to be demeaning to thee Python folks, but
what else can you call being column aware in a parser but
retrograde.)
Is this the first purposal for `dark-space.' :)
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It certainly is reactionary.
"Hateful in the eyes of God" is how I've come to see it.
On 5-Jan-07, at 9:44 AM, ge...@plan9.bell-labs.com wrote:
> I believe the intent was to force indentation to match block
> structure, in reaction to badly-formatted code in other languages.
>
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFFnpAypJeHo/Fbu1wRAol7AJ95r0JwEFfKK2YrJopkBk1foauVqACfVHou
ysP1fnE5OgC0gj+psET++z4=
=8dtu
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFFnpBFpJeHo/Fbu1wRAoCLAJ9VopepIB4qQh5sFHUmn7KpCuviHwCbBE7x
Z2U/3p+lQoqzUqyXbNQi2k4=
=Qds1
-----END PGP SIGNATURE-----
The way to hell is paved with good intentions :-). Anyway, at least they
should have chosen tabs OR spaces. I agree in indenting right, but
syntax should be visible.