On Thursday 20 June 2002 12:01 pm, Edmund Lian wrote: > Ian and Tavis, thanks for the quick reply regarding single versus > double quoted triplets. Seems to me though, that if the issue is > Emacs can't understand triple quoted strings that use apostrophes, > then Emacs should be fixed, not Python source code. > > Once everybody starts going down the path of adapting coding habits > to the limitations and idiosyncracies of editors, there'll be no end > of trouble. E.g., "oh, editor X doesn't handle Y well, so let's not > use Y either, since we did the same for Emacs". I can't see any > particular reason why one should favor helping Emacs over another > editor...
Amen, brother! I totally agree, but as a minor concession, I yielded to the emacs zealots and gave the green light to switch to """. I hope the death threats stop now! ;-) The other change agreed upon, but probably not yet implemented is wrapping class and method doc strings to column 72 (in edits where tabs=4; col 80 whe tabs=8) in order for easier reading. On Thursday 20 June 2002 12:27 pm, Edmund Lian wrote: > Here's a cheeky comment (meant in fun): if Emacs has such a large > constituency amongst Python coders, and if it is so extensible, why > hasn't the problem been fixed? �:-) �OK, no flame wars please! �:-) I love it! Edmund, these were the same things I was saying a while back when our emacs-abilities vs. python-syntax flamewar reached the kind of proportions where we lost subscribers. Not that I loved that last part. But it is interesting to note that Emacs being open source and both products having been around for years, Emacs still can't handle a proper Python file. On Thursday 20 June 2002 12:36 pm, Edmund Lian wrote: > The thing that bugs me more, actually, is the tabs vs spaces issue > since this actually has semantic implications. I've been caught out > more than once by someone else's code using tabs, (or worse, a > mixture of tabs and spaces). Now, this is worth a good fight or two! Ah, but that's the one I didn't concede. Also, note that we do NOT use a mixture, which is the ultimate Python sin. > Actually, up until about a year ago, I used Emacs 100% of the time. I > eventually got tired of the bloat and need to do finger-gymnastics on > the keyboard to get anything done. It was quite hard to switch to > vim, but I'm glad that I took the time. But now you have let me down! VIM???? ;-) I personally recommend: Kate on linux UltraEdit on windows or: SciTE on * And of course, don't forget to support the WingIDE guys! http://archaeopteryx.com/ -Chuck ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
