From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 15 Jul 2009 14:41:34 -0600 From: Lyndon Nerenberg To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <9ab217670907151314n4e5c5855oda60cc527bb83422@mail.gmail.com> Message-ID: References: <7d3530220907151000s60671d2gfdb18cdf12c55097@mail.gmail.com> <0009e18319f5c60dc890463505286c1c@quintile.net> <3e1162e60907151159g5b031e99k2ad8171c9c268392@mail.gmail.com> <9ab217670907151314n4e5c5855oda60cc527bb83422@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [9fans] Why does Acme only show text? Topicbox-Message-UUID: 21d0e89c-ead5-11e9-9d60-3106f5b1d025 > On that note, my personal experience has found it to be a lot easier > to find and correct scope issues in Python than it has to find missing > braces or semicolons in other languages, sometimes even with matching > enabled. This usually is the case for awful spaghetti-ish code. I find Python's whitespace rules annoying, but I can live with them. Where the whitespace flow control always screws me is when I'm working on a particular chunk of code using different editors that have different semantics for interpreting . You have to remember if the editor of the moment interprets as: 1) HT passed through, displays to next col%8 2) HT passed through, displays to next col%user_defined_tabstop setting 3) As for (1) and (2), but also expanded to corresponding n* to match display interpretation. As soon as you mix 8 and non-8 tabstop rails, any remnants of sanity exit stage left. Because of this I far-too-often find myself running acme-edited code through [un]expand to ensure sane tab behaviour. (Not acme's falut per se -- it's just the editor I most commonly use that does non-8 tabstops by default.) --lyndon