From mboxrd@z Thu Jan 1 00:00:00 1970 From: chris@hollis-locke.com To: 9fans@cse.psu.edu In-Reply-To: <653c7bb3bdcf917cbe19bdad820368aa@plan9.bell-labs.com> Subject: Re: [9fans] acme fonts User-Agent: Demon-WebMail/2.0 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: Date: Tue, 14 Oct 2003 17:04:19 +0100 Topicbox-Message-UUID: 6e9b8f5a-eacc-11e9-9e20-41e7f4b1d025 presotto@closedmind.org wrote: > Proportionally spaced fonts could be liberating, but don't > seem so in practice. I find that all of the code lines up > nicely when I use the same font as the author (Rob included). > Perhaps we just need more time to liberate ourselves. > The main problem I've seen here is how acme handles tabs. Obviously there are other bits of code layout that will line up in a CW font that wont in a VW font but for the most part I use tabs for alignment. Most important to me is 'leading edge' alignment I am not too bothered about ragged trailing edges. Maybe something like: When doing tab calculation dont use the current character pos, instead treat every preceeding char on the line as width 1em even if it is less. Set your tab width to 4em and I think you'll get quite nice results irrespective of CW/VW font. Obviously this only goes for newly written code - those extra tabs to line up old code under the old tabbing scheme will throw it out, but once prettied up, it will stay prettied up for everyone.