From taleinat at gmail.com  Wed Jul  5 13:34:14 2006
From: taleinat at gmail.com (Tal Einat)
Date: Wed, 5 Jul 2006 14:34:14 +0300
Subject: [Idle-dev] Coloration bug fixes
Message-ID: <7afdee2f0607050434t2a69120fu498dd37bc8db04b5@mail.gmail.com>

Hi all,

I've just joined this list and I noticed a posting about wrong coloration of
'#set'.

This is a general bug in IDLE coloration which doesn't recognize comments
which have a keyword immediatly following the '#' character.

This is one of several bugs fixed by a patch I posted in SF some time back,
which hasn't recieved any attention :(

- Tal

-- 
How many roads must a man travel down before he admits he is lost?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060705/fabc0d85/attachment.html 

From ronaldoussoren at mac.com  Wed Jul  5 17:26:05 2006
From: ronaldoussoren at mac.com (Ronald Oussoren)
Date: Wed, 05 Jul 2006 17:26:05 +0200
Subject: [Idle-dev] Coloration bug fixes
In-Reply-To: <7afdee2f0607050434t2a69120fu498dd37bc8db04b5@mail.gmail.com>
References: <7afdee2f0607050434t2a69120fu498dd37bc8db04b5@mail.gmail.com>
Message-ID: <9181414.1152113165745.JavaMail.ronaldoussoren@mac.com>

What is the number of that patch? 

Ronald
 
On Wednesday, July 05, 2006, at 01:35PM, Tal Einat <taleinat at gmail.com> wrote:

>
><<Original Attached>>_______________________________________________
>IDLE-dev mailing list
>IDLE-dev at python.org
>http://mail.python.org/mailman/listinfo/idle-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060705/19d5a141/attachment.html 

From taleinat at gmail.com  Wed Jul  5 17:39:27 2006
From: taleinat at gmail.com (Tal Einat)
Date: Wed, 5 Jul 2006 18:39:27 +0300
Subject: [Idle-dev] Coloration bug fixes
In-Reply-To: <9181414.1152113165745.JavaMail.ronaldoussoren@mac.com>
References: <7afdee2f0607050434t2a69120fu498dd37bc8db04b5@mail.gmail.com>
	<9181414.1152113165745.JavaMail.ronaldoussoren@mac.com>
Message-ID: <7afdee2f0607050839m1fad90f9yc74db320277c567e@mail.gmail.com>

1479219<http://sourceforge.net/tracker/?func=detail&aid=1479219&group_id=5470&atid=305470>

On 7/5/06, Ronald Oussoren <ronaldoussoren at mac.com> wrote:
>
> What is the number of that patch?
>
> Ronald
>
> On Wednesday, July 05, 2006, at 01:35PM, Tal Einat <taleinat at gmail.com>
> wrote:
>
> >
> ><<Original Attached>>_______________________________________________
> >IDLE-dev mailing list
> >IDLE-dev at python.org
> >http://mail.python.org/mailman/listinfo/idle-dev
> >
> >
>
>
>
> Hi all,
>
> I've just joined this list and I noticed a posting about wrong coloration
> of '#set'.
>
> This is a general bug in IDLE coloration which doesn't recognize comments
> which have a keyword immediatly following the '#' character.
>
> This is one of several bugs fixed by a patch I posted in SF some time
> back, which hasn't recieved any attention :(
>
> - Tal
>
> --
> How many roads must a man travel down before he admits he is lost?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060705/d78fd49f/attachment.htm 

From glingl at aon.at  Thu Jul 13 00:15:41 2006
From: glingl at aon.at (Gregor Lingl)
Date: Thu, 13 Jul 2006 00:15:41 +0200
Subject: [Idle-dev] firewall warning
Message-ID: <44B5748D.2050200@aon.at>

The firewall warning message in the Pythonshell window
was introduced  in Python 2.3 (IDLE 1.0 or something similar?)

I remember well the problems, which have been occurred then, and
to which it was the answer. (If I remember correctly I was
involved in the discussion thread which led to the introduction
of that message.)

Since more than three years I've used IDLE on many different
systems and I didn't encounter a single Firewall warning since
then. (It seems that firewalls nowadays are not offended by
the use of 127.0.0.1)

Therefore, and because the message is long and ugly, I'd like to
suggest to delete it from the Python Shell window
and - if considered necessary - for instance to put
it into the IDLE Help - "About IDLE" submenu or
in a special IDLE-Firewall warning submenu of IDLE-Help.

Please observe that it pops up thousands of times and it's
read at most once.

Additional remark (about my personal interest):
I have to do a lot of IDLE-screenshots for a textbook
on programming and I really don't like it to occur on
all those screenshots.

Regards,
Gregor

From glingl at aon.at  Thu Jul 13 00:40:50 2006
From: glingl at aon.at (Gregor Lingl)
Date: Thu, 13 Jul 2006 00:40:50 +0200
Subject: [Idle-dev] Idle 1.1.2
In-Reply-To: <b348a0850606221502k6b29bc96y5c7076fead3526c8@mail.gmail.com>
References: <74a945120606220832x270e042cxefe838ce348ac78a@mail.gmail.com>
	<b348a0850606221502k6b29bc96y5c7076fead3526c8@mail.gmail.com>
Message-ID: <44B57A72.1040002@aon.at>

Noam Raphael schrieb:
> Hello,
>
> There's no special meaning to "#set" or "# set" - they are just comments.
> What you describe is a bug in the syntax colouring system.
>   
Unfortunately this bug is still present in IDLE 1.2b2
Gregor
> Noam
>
> 2006/6/22, spotter . <talonspotter at gmail.com>:
>   
>> Hi,
>>
>> I am not sure if this is the right place to ask this, but here goes.
>> I am using python 2.4.2 and idle version 1.1.2. When I was typing some code,
>> I realized that when I typed #set, the syntax highlighting was off.
>> The color of the # was black and the set was a maroon color, but if I
>> put a space between # set, then the syntax highlight changed to all
>> red, as comments usually appear.
>>
>> Is this normal behavior for that? Does set have special meaning? I was
>> just wondering.
>>
>> Thanks,
>> spot .
>> _______________________________________________
>> IDLE-dev mailing list
>> IDLE-dev at python.org
>> http://mail.python.org/mailman/listinfo/idle-dev
>>
>>     
> _______________________________________________
> IDLE-dev mailing list
> IDLE-dev at python.org
> http://mail.python.org/mailman/listinfo/idle-dev
>
>
>   


From taleinat at gmail.com  Mon Jul 17 00:26:51 2006
From: taleinat at gmail.com (Tal Einat)
Date: Mon, 17 Jul 2006 00:26:51 +0200
Subject: [Idle-dev] firewall warning
In-Reply-To: <44B5748D.2050200@aon.at>
References: <44B5748D.2050200@aon.at>
Message-ID: <7afdee2f0607161526sfe140c8r9b0349d5cef1c37c@mail.gmail.com>

+1

Moving the firewall warning to an entry in the "Help" menu sounds good to
me.
It would definitely make IDLE's interpreter cleaner, which could help
improve IDLE's image.

BTW Gregor, meanwhile you can just remove the warning yourself in
PyShell.py- just set firewallmessage to en empty string.

- Tal


On 7/13/06, Gregor Lingl <glingl at aon.at> wrote:
>
> The firewall warning message in the Pythonshell window
> was introduced  in Python 2.3 (IDLE 1.0 or something similar?)
>
> I remember well the problems, which have been occurred then, and
> to which it was the answer. (If I remember correctly I was
> involved in the discussion thread which led to the introduction
> of that message.)
>
> Since more than three years I've used IDLE on many different
> systems and I didn't encounter a single Firewall warning since
> then. (It seems that firewalls nowadays are not offended by
> the use of 127.0.0.1)
>
> Therefore, and because the message is long and ugly, I'd like to
> suggest to delete it from the Python Shell window
> and - if considered necessary - for instance to put
> it into the IDLE Help - "About IDLE" submenu or
> in a special IDLE-Firewall warning submenu of IDLE-Help.
>
> Please observe that it pops up thousands of times and it's
> read at most once.
>
> Additional remark (about my personal interest):
> I have to do a lot of IDLE-screenshots for a textbook
> on programming and I really don't like it to occur on
> all those screenshots.
>
> Regards,
> Gregor
> _______________________________________________
> IDLE-dev mailing list
> IDLE-dev at python.org
> http://mail.python.org/mailman/listinfo/idle-dev
>



-- 
How many roads must a man travel down before he admits he is lost?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060717/77824ed3/attachment.html 

From taleinat at gmail.com  Thu Jul 20 18:17:06 2006
From: taleinat at gmail.com (Tal Einat)
Date: Thu, 20 Jul 2006 19:17:06 +0300
Subject: [Idle-dev] Key bindings
Message-ID: <7afdee2f0607200917ue09d13do5ba8978da6e1cd5d@mail.gmail.com>

IDLE currently only supports basic key bindings, but not Emacs-like keybings
which consist of sequences of several keys (such as <Ctrl-x> <Ctrl-s>, or
C-x C-s in Emacs key-binding syntax).

Has any work been done to add support for these kind of bindings in IDLE?

Personally, I fell adding support for Emacs-like bindings (the simpler ones)
will be a welcome feature for many Emacs users, and can help widen our user
base.

- Tal
How many roads must a man travel down before he admits he is lost?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060720/63b75583/attachment.html 

From michael at d2m.at  Sun Jul 23 00:47:07 2006
From: michael at d2m.at (Michael Haubenwallner)
Date: Sun, 23 Jul 2006 00:47:07 +0200
Subject: [Idle-dev] IDLE extension: IDLE2HTML
Message-ID: <e9u9uu$p5$1@sea.gmane.org>

I created this extension to color-print the contents of my IDLE file and 
shell windows.

IDLE2HTML
========
This extension saves the contents of your IDLE shell or editor window
as XHTML (using Stylesheets to preserve all color and formatting 
information).

Source is here: http://trac.d2m.at/d2m/browser/IDLE/IDLE2HTML/trunk/

Hope it is useful for you too.
Michael

-- 
http://zope.org/Members/d2m
http://planetzope.org


From taleinat at gmail.com  Wed Jul 26 16:21:03 2006
From: taleinat at gmail.com (Tal Einat)
Date: Wed, 26 Jul 2006 16:21:03 +0200
Subject: [Idle-dev] firewall warning
In-Reply-To: <7afdee2f0607161526sfe140c8r9b0349d5cef1c37c@mail.gmail.com>
References: <44B5748D.2050200@aon.at>
	<7afdee2f0607161526sfe140c8r9b0349d5cef1c37c@mail.gmail.com>
Message-ID: <7afdee2f0607260721m6dc5e609pf302f4d50107be6c@mail.gmail.com>

I implemented this change and posted a patch on SF.

Patch #1529018 <https://sourceforge.net/support/tracker.php?aid=1529018>

On 7/17/06, Tal Einat <taleinat at gmail.com> wrote:
>
>  +1
>
> Moving the firewall warning to an entry in the "Help" menu sounds good to
> me.
> It would definitely make IDLE's interpreter cleaner, which could help
> improve IDLE's image.
>
> BTW Gregor, meanwhile you can just remove the warning yourself in
> PyShell.py - just set firewallmessage to en empty string.
>
> - Tal
>
>
>  On 7/13/06, Gregor Lingl <glingl at aon.at> wrote:
> >
> > The firewall warning message in the Pythonshell window
> > was introduced  in Python 2.3 (IDLE 1.0 or something similar?)
> >
> > I remember well the problems, which have been occurred then, and
> > to which it was the answer. (If I remember correctly I was
> > involved in the discussion thread which led to the introduction
> > of that message.)
> >
> > Since more than three years I've used IDLE on many different
> > systems and I didn't encounter a single Firewall warning since
> > then. (It seems that firewalls nowadays are not offended by
> > the use of 127.0.0.1)
> >
> > Therefore, and because the message is long and ugly, I'd like to
> > suggest to delete it from the Python Shell window
> > and - if considered necessary - for instance to put
> > it into the IDLE Help - "About IDLE" submenu or
> > in a special IDLE-Firewall warning submenu of IDLE-Help.
> >
> > Please observe that it pops up thousands of times and it's
> > read at most once.
> >
> > Additional remark (about my personal interest):
> > I have to do a lot of IDLE-screenshots for a textbook
> > on programming and I really don't like it to occur on
> > all those screenshots.
> >
> > Regards,
> > Gregor
> > _______________________________________________
> > IDLE-dev mailing list
> > IDLE-dev at python.org
> > http://mail.python.org/mailman/listinfo/idle-dev
> >
>
>
>
> --
> How many roads must a man travel down before he admits he is lost?
>



-- 
How many roads must a man travel down before he admits he is lost?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060726/ff16930c/attachment.htm 

From kbk at shore.net  Thu Jul 27 05:24:15 2006
From: kbk at shore.net (Kurt B. Kaiser)
Date: Wed, 26 Jul 2006 23:24:15 -0400
Subject: [Idle-dev] Key bindings
In-Reply-To: <7afdee2f0607200917ue09d13do5ba8978da6e1cd5d@mail.gmail.com> (Tal
	Einat's message of "Thu, 20 Jul 2006 19:17:06 +0300")
References: <7afdee2f0607200917ue09d13do5ba8978da6e1cd5d@mail.gmail.com>
Message-ID: <87odvbafxc.fsf@hydra.bayview.thirdcreek.com>

"Tal Einat" <taleinat at gmail.com> writes:

> IDLE currently only supports basic key bindings, but not Emacs-like
> keybings which consist of sequences of several keys (such as <Ctrl-x>
> <Ctrl-s>, or C-x C-s in Emacs key-binding syntax).
>
> Has any work been done to add support for these kind of bindings in
> IDLE?

Actually, the "Classic Unix" keybinding does support that.  The
implementation is rather subtle.  In config-keybindings.def, note the
'do-nothing' and 'save-window' bindings.  Note in the latter there is no
space between the two bindings, that syntax indicates a combination.

>
> Personally, I feel adding support for Emacs-like bindings (the simpler
> ones) will be a welcome feature for many Emacs users, and can help
> widen our user base.

Right.  The 'classic' set isn't especially emacsish (emacish?). I've
been thinking about a new binding set, 'IDLE Emacs'.  Personally, I
use a modification of 'IDLE Classic Unix'.

-- 
KBK

From kbk at shore.net  Thu Jul 27 05:26:46 2006
From: kbk at shore.net (Kurt B. Kaiser)
Date: Wed, 26 Jul 2006 23:26:46 -0400
Subject: [Idle-dev] Coloration bug fixes
In-Reply-To: <7afdee2f0607050839m1fad90f9yc74db320277c567e@mail.gmail.com>
	(Tal Einat's message of "Wed, 5 Jul 2006 18:39:27 +0300")
References: <7afdee2f0607050434t2a69120fu498dd37bc8db04b5@mail.gmail.com>
	<9181414.1152113165745.JavaMail.ronaldoussoren@mac.com>
	<7afdee2f0607050839m1fad90f9yc74db320277c567e@mail.gmail.com>
Message-ID: <87k65zaft5.fsf@hydra.bayview.thirdcreek.com>

"Tal Einat" <taleinat at gmail.com> writes:

> 1479219<http://sourceforge.net/tracker/?func=detail&aid=1479219&group_id=5470&atid=305470>

Implemented. Thanks!

-- 
KBK

From taleinat at gmail.com  Thu Jul 27 14:40:42 2006
From: taleinat at gmail.com (Tal Einat)
Date: Thu, 27 Jul 2006 15:40:42 +0300
Subject: [Idle-dev] Key bindings
In-Reply-To: <87odvbafxc.fsf@hydra.bayview.thirdcreek.com>
References: <7afdee2f0607200917ue09d13do5ba8978da6e1cd5d@mail.gmail.com>
	<87odvbafxc.fsf@hydra.bayview.thirdcreek.com>
Message-ID: <7afdee2f0607270540v3a1187a3vfa4e409bc6808fdf@mail.gmail.com>

On 7/27/06, Kurt B. Kaiser <kbk at shore.net> wrote:
>
> "Tal Einat" <taleinat at gmail.com> writes:
>
> > IDLE currently only supports basic key bindings, but not Emacs-like
> > keybings which consist of sequences of several keys (such as <Ctrl-x>
> > <Ctrl-s>, or C-x C-s in Emacs key-binding syntax).
> >
> > Has any work been done to add support for these kind of bindings in
> > IDLE?
>
> Actually, the "Classic Unix" keybinding does support that.  The
> implementation is rather subtle.  In config-keybindings.def, note the
> 'do-nothing' and 'save-window' bindings.  Note in the latter there is no
> space between the two bindings, that syntax indicates a combination.


Hmm... Tricky stuff! Is this a built-in feature of Tk key bindings?

>
> > Personally, I feel adding support for Emacs-like bindings (the simpler
> > ones) will be a welcome feature for many Emacs users, and can help
> > widen our user base.
>
> Right.  The 'classic' set isn't especially emacsish (emacish?). I've
> been thinking about a new binding set, 'IDLE Emacs'.  Personally, I
> use a modification of 'IDLE Classic Unix'.


Well then - what are we waiting for? ... I'm on it :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060727/e483cf37/attachment.html 

From soura_jagat at yahoo.com  Sat Jul 29 09:27:47 2006
From: soura_jagat at yahoo.com (Sourav Datta)
Date: Sat, 29 Jul 2006 00:27:47 -0700 (PDT)
Subject: [Idle-dev] A possible bug in IDLE 1.2b2
Message-ID: <20060729072747.91624.qmail@web38915.mail.mud.yahoo.com>

 
  The IDLE that comes with Python 1.5 beta has a problem. While the Alt+p retrieves the previous command issued to the prompt, there was another way to do that in IDLE v1.1.2 that came with Python 2.4. If I just clicked on a previous command and hit ENTER, the command would appear again in the new prompt. As follows,
   
  IDLE 1.1.2      
  >>> def hello(name):
              if name=='me':
                          print 'Hello you!'
              else:
                          print 'Hello '+name
   
                          
  >>> hello('James')
  Hello James
   
  Now clicking on the line hello(
) and hitting ENTER, we get the following again.
  >>> def hello(name):
              if name=='me':
                          print 'Hello you!'
              else:
                          print 'Hello '+name
   
   
   
  But with the new IDLE it is not so. Doing the same would yield the following,
   
  IDLE 1.2b2      
  >>> def hello(name):
              if name=='me':
                          print 'Hello you'
              else:
                          print 'Hello '+name
   
                          
  >>> hello('me')
  Hello you
   
  Now, again clicking on hello(...) definition line and hitting ENTER, we get the following
  >>> def hello(name):
              if name=='me':
                          print 'Hello you'
                          else:
                                      print 'Hello '+name
   
                                      
  SyntaxError: invalid syntax
   


---------------------------------------------------------------------------------------------
  "WYNINNWYWG"
   Sourav Datta

 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060729/b63119ae/attachment.html 

From taleinat at gmail.com  Sun Jul 30 10:08:31 2006
From: taleinat at gmail.com (Tal Einat)
Date: Sun, 30 Jul 2006 11:08:31 +0300
Subject: [Idle-dev] A possible bug in IDLE 1.2b2
In-Reply-To: <20060729072747.91624.qmail@web38915.mail.mud.yahoo.com>
References: <20060729072747.91624.qmail@web38915.mail.mud.yahoo.com>
Message-ID: <7afdee2f0607300108y2e13115fnd801a1c0cd7b4e5@mail.gmail.com>

Several days ago I submitted a patch which addresses this issue: SF patch
1528468<http://sourceforge.net/tracker/index.php?func=detail&aid=1528468&group_id=5470&atid=305470>
.

This will probably be included in Python 2.6.


On 7/29/06, Sourav Datta <soura_jagat at yahoo.com> wrote:
>
>
> The IDLE that comes with Python 1.5 beta has a problem. While the Alt+p
> retrieves the previous command issued to the prompt, there was another way
> to do that in IDLE v1.1.2 that came with Python 2.4. If I just clicked on
> a previous command and hit ENTER, the command would appear again in the new
> prompt. As follows,
>
> IDLE 1.1.2
> >>> def hello(name):
>             if name=='me':
>                         print 'Hello you!'
>             else:
>                         print 'Hello '+name
>
>
> >>> hello('James')
> Hello James
>
> Now clicking on the line hello(?) and hitting ENTER, we get the following
> again.
> >>> def hello(name):
>             if name=='me':
>                         print 'Hello you!'
>             else:
>                         print 'Hello '+name
>
>
>
> But with the new IDLE it is not so. Doing the same would yield the
> following,
>
> IDLE 1.2b2
> >>> def hello(name):
>             if name=='me':
>                         print 'Hello you'
>             else:
>                         print 'Hello '+name
>
>
> >>> hello('me')
> Hello you
>
> Now, again clicking on hello(...) definition line and hitting ENTER, we
> get the following
> >>> def hello(name):
>             if name=='me':
>                         print 'Hello you'
>                         else:
>                                     print 'Hello '+name
>
>
> SyntaxError: invalid syntax
>
>
>
> *
> ---------------------------------------------------------------------------------------------
> *
> *"WYNINNWYWG"*
>   *Sourav Datta*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/idle-dev/attachments/20060730/84548f0f/attachment.html