[Pythonmac-SIG] Advanced Editor patch

Joseph J. Strout joe@strout.net
Thu, 30 Sep 1999 15:47:08 -0700


At 6:33 PM -0400 09/30/99, Richard Gordon wrote:

>I trashed everything from earlier today and reinstalled Python from 
>scratch, then got your revised printing patch as well as the editor 
>patch. This time everything went very well, tho I still had to use 
>BuildApplet to get where I wanted to be (the PythonIDE icon that was 
>left from all of the patching had a generic document icon).

The generic document icon is probably just a Finder database issue; 
you probably could have got by rebuilding the desktop (or possibly 
just closing the Python folder and opening it again).

> The only other catch was that I had to get rid of unix line endings 
>after downloading your stuff, but that's no big deal.

OK, this comes from the way your browser was configured and how you 
downloaded the files; it's a pretty common problem.  I like to put 
the Python source right on the web page so you can view it before 
saving it, but it does cause this little difficulty with some 
browsers... I'll try to come up with a clever solution that doesn't 
involve me updating a Stuffit archive every time I update the files. 
;)

> Anyway, I'm pleased with your efforts and really appreciate these 
>enhancements.

Thanks.  I'm glad to hear it's working for you!

FYI, I'm now working on improving the double-click behavior, so that 
it selects a "word" based on proper Python delimiters, and if you 
double-click a grouping character (like '(', '[', '{', or a quotation 
mark), it selects the whole group (i.e., to the corresponding 
character).  Coming along nicely so far, though quotation marks are 
going to be tricky, since there's no way to tell whether a particular 
quote you're looking at is the starting or ending quote without 
analyzing the whole file.

On that topic, does anyone understand what command-clicking currently 
does?  It selects a range of text, but I can't see any rhyme or 
reason to the range it selects.

MCL has a very cool feature when you command-click somewhere, rather 
than moving the text cursor, it copies the "block" of text where you 
clicked to the current insertion point.  Extremely handy, saves your 
fingers a lot of work.  (A "block" of text is what you would have 
gotten by double-clicking that same location.)  I'd like to add this 
feature too.

Cheers,
-- Joe

,------------------------------------------------------------------.
|    Joseph J. Strout           Biocomputing -- The Salk Institute |
|    joe@strout.net             http://www.strout.net              |
`------------------------------------------------------------------'