From: Eric Mangold <eric@oaktech.net>
To: "zsh-users@sunsite.dk" <zsh-users@sunsite.dk>
Subject: Re: [OT]Python/zsh/perl [was: named directory expansion on strings]
Date: Tue, 16 Mar 2004 21:03:09 -0700 [thread overview]
Message-ID: <opr4zmvjgr55xoqp@mail.oaktech.net> (raw)
In-Reply-To: <20040315070400.81487.qmail@web12405.mail.yahoo.com>
On Sun, 14 Mar 2004 23:04:00 -0800 (PST), Bob Schmertz
<rschmertz@yahoo.com> wrote:
> --- Vincent Stemen <zsh@hightek.org> wrote:
> [quoted text "juggled around" a bit]
>
>> I agree. This surprising discovery is the primary reason I never put
>> any serious consideration into learning Python.
>
>> I use the auto indentation features of xemacs all the time. I see no
>> way you could do that without code block delimiters. Seems like a step
>> backward in time.
>
> Emacs seems to be the most popular editor for Python programmers. It
> knows when to start a new indent level, because the if, while, class,
> etc. lines all end with a colon. It can't tell when you want to close
> the
> block, of course, but if you're typing new code, that's a simple matter
> of
> hitting the backspace key once for every block you want to close out. I
> wouldn't /think/ of coding in Python if I didn't have Emacs or something
> equally smart.
>
>> Seems like it would be a nightmare to fix if you get your indentation
>> messed up (which is extremely common when juggling code around).
>
> Not sure exactly what you mean by "juggling around"; if you mean cutting
> a
> section from a file and moving it elsewhere in the file, or to a
> different
> file, at a point that starts out at a different indent level, there's a
> key sequence to add or subtract an indent level from that entire block of
> code, so that the pasted code will be consisent with itself as well as
> fitting all under the appropriate if statement or whatever. If you're
> talking about code from someone else, esp. via email and things like
> that,
> then there are more variables, of course.
>
> Do I think blocking by indentation is the greatest thing since sliced
> bread? No. But I've been surprised to find that it has rarely, if ever,
> been a problem for me
Yeah. It's a complete non-issue. There are much better things to fault
python for. (not that having faults makes it a bad choice for various
things)
next prev parent reply other threads:[~2004-03-17 3:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 3:29 named directory expansion on strings Thorsten Kampe
2004-03-13 6:41 ` Bart Schaefer
2004-03-13 17:48 ` Thorsten Kampe
2004-03-14 18:54 ` Bart Schaefer
2004-03-14 21:24 ` Thorsten Kampe
2004-03-14 21:57 ` Python/zsh/perl [was: named directory expansion on strings] Vincent Stemen
2004-03-15 4:00 ` Jos Backus
2004-03-15 7:04 ` [OT]Python/zsh/perl " Bob Schmertz
2004-03-15 23:37 ` [OT]Python/zsh/perl Vincent Stemen
2004-03-17 4:03 ` Eric Mangold [this message]
2004-03-14 22:19 ` named directory expansion on strings Thorsten Kampe
2004-03-14 23:19 ` Bart Schaefer
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=opr4zmvjgr55xoqp@mail.oaktech.net \
--to=eric@oaktech.net \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).