9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.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 00:26:21 -0500	[thread overview]
Message-ID: <ee9e417a0701042126o6cd149a4xee1fd1fe164678d2@mail.gmail.com> (raw)
In-Reply-To: <13426df10701041941k6954773g671210b1d107c264@mail.gmail.com>

> 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.

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


  reply	other threads:[~2007-01-05  5:26 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 [this message]
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
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=ee9e417a0701042126o6cd149a4xee1fd1fe164678d2@mail.gmail.com \
    --to=rsc@swtch.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).