[lug] Running a mixed Python environment

[Rob Nagler]

On Wed, Sep 16, 2020 at 6:29 PM Zan Lynx wrote:
> I'm on the side of tabs for indentation. If you use spaces then people
> go around wasting time trying to line up their parentheses and argument
> lists.

No tabs for us, and no alignment madness either. I don't see how they are
related.

In Emacs or VIM, you can hit tab, and have it convert to spaces,
appropriately. Tab just means move over an indent level. (Emacs cycles so
you unindent by hitting tab, too.)

> Nothing bugs me more than a six argument function call slammed all the
> way to the right side of the screen because someone thought things
> should line up.

AFAIK, Ousterhout was the first to use fixed width alignment for continued
lines:

https://core.tcl-lang.org/tips/doc/trunk/tip/352.md#toc-24


*You should use continuation lines to make sure that no single line exceeds
80 characters in length. Continuation lines should be indented 8 spaces so
that they won't be confused with an immediately-following nested block.
Pick clean places to break your lines for continuation, so that the
continuation doesn't obscure the structure of the statement. For example,
if a procedure call requires continuation lines, try to avoid situations
where a single argument spans multiple lines. If the test for an if or
while command spans lines, try to make each line have the same nesting
level of parentheses and/or brackets if possible. I try to start each
continuation line with an operator such as *, &&, or ||; this makes it
clear that the line is a continuation, since a new statement would never
start with such an operator.*


Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20200917/1c8bcca7/attachment.html>