[Python-bugs-list] [Bug #110660] IDLE-0.5 ctrl-F5 (PR#355)

noreply@sourceforge.net noreply@sourceforge.net
Wed, 23 Aug 2000 10:25:57 -0700


Bug #110660, was updated on 2000-Jul-31 21:11
Here is a current snapshot of the bug.

Project: Python
Category: IDLE
Status: Open
Resolution: None
Bug Group: None
Priority: 3
Summary: IDLE-0.5  ctrl-F5 (PR#355)

Details: Jitterbug-Id: 355
Submitted-By: gpk@bell-labs.com
Date: Tue, 13 Jun 2000 11:30:14 -0400 (EDT)
Version: yesterday's CVS
OS: Solaris 2.6


If you type ctrl-f5 to run a script twice in sucession,
IDLE will incorrectly pop up a window saying
"Not Saved.  Please Save First."

If you save (even though you haven't changed anything,
and even though there are no asterisks around the window
title), then ctrl-f5 will work again.

This *doesn't* happen if you run the script twice in
succession from the menu.



====================================================================
Audit trail:
Tue Jul 11 08:26:00 2000	guido	moved from incoming to open

Follow-Ups:

Date: 2000-Aug-01 21:01
By: none

Comment:
From: "Tim Peters" <tim_one@email.msn.com>
Subject: RE: [Python-bugs-list] IDLE-0.5  ctrl-F5 (PR#355)
Date: Tue, 13 Jun 2000 11:55:09 -0400

Pretty mysterious!  Doesn't happen under IDLE 0.5 for me.  Running under
Windows, but darned hard to see why that would matter.  Can anyone else try
this under Solaris 2.6?  May have something to do with the specific script
you're running, Greg; e.g., does it happen if the script file contains just

print "Hi!"

?

> -----Original Message-----
> From: python-bugs-list-admin@python.org
> [mailto:python-bugs-list-admin@python.org]On Behalf Of gpk@bell-labs.com
> Sent: Tuesday, June 13, 2000 11:30 AM
> To: python-bugs-list@python.org
> Cc: bugs-py@python.org
> Subject: [Python-bugs-list] IDLE-0.5 ctrl-F5 (PR#355)
>
>
> Full_Name: Greg Kochanski
> Version: yesterday's CVS
> OS: Solaris 2.6
> Submission from: h-135-104-33-130.research.bell-labs.com (135.104.33.130)
>
>
> If you type ctrl-f5 to run a script twice in sucession,
> IDLE will incorrectly pop up a window saying
> "Not Saved.  Please Save First."
>
> If you save (even though you haven't changed anything,
> and even though there are no asterisks around the window
> title), then ctrl-f5 will work again.
>
> This *doesn't* happen if you run the script twice in
> succession from the menu.
>
>
>
> _______________________________________________
> Python-bugs-list maillist  -  Python-bugs-list@python.org
> http://www.python.org/mailman/listinfo/python-bugs-list
>




-------------------------------------------------------

Date: 2000-Aug-01 21:01
By: none

Comment:
From: Guido van Rossum <guido@python.org>
Subject: Re: [Python-bugs-list] IDLE-0.5 ctrl-F5 (PR#355)
Date: Tue, 20 Jun 2000 16:42:57 -0500

I think I understand this.  It's happened to me too.  Pressing ^F5
changes the focus to the PyShell window.  Pressing ^F5 again then
indeed complains about that window being unsaved.

--Guido van Rossum (home page: http://www.python.org/~guido/)

[Tim]
> Pretty mysterious!  Doesn't happen under IDLE 0.5 for me.  Running under
> Windows, but darned hard to see why that would matter.  Can anyone else try
> this under Solaris 2.6?  May have something to do with the specific script
> you're running, Greg; e.g., does it happen if the script file contains just
> 
> print "Hi!"
> 
> ?
> 
> > -----Original Message-----
> > From: python-bugs-list-admin@python.org
> > [mailto:python-bugs-list-admin@python.org]On Behalf Of gpk@bell-labs.com
> > Sent: Tuesday, June 13, 2000 11:30 AM
> > To: python-bugs-list@python.org
> > Cc: bugs-py@python.org
> > Subject: [Python-bugs-list] IDLE-0.5 ctrl-F5 (PR#355)
> >
> >
> > Full_Name: Greg Kochanski
> > Version: yesterday's CVS
> > OS: Solaris 2.6
> > Submission from: h-135-104-33-130.research.bell-labs.com (135.104.33.130)
> >
> >
> > If you type ctrl-f5 to run a script twice in sucession,
> > IDLE will incorrectly pop up a window saying
> > "Not Saved.  Please Save First."
> >
> > If you save (even though you haven't changed anything,
> > and even though there are no asterisks around the window
> > title), then ctrl-f5 will work again.
> >
> > This *doesn't* happen if you run the script twice in
> > succession from the menu.
> >
> >
> >
> > _______________________________________________
> > Python-bugs-list maillist  -  Python-bugs-list@python.org
> > http://www.python.org/mailman/listinfo/python-bugs-list
> >
> 
> 
> 
> _______________________________________________
> Python-bugs-list maillist  -  Python-bugs-list@python.org
> http://www.python.org/mailman/listinfo/python-bugs-list



-------------------------------------------------------

Date: 2000-Aug-01 21:01
By: none

Comment:
From: Greg Kochanski <gpk@bell-labs.com>
Subject: Re: [Python-bugs-list] IDLE-0.5 ctrl-F5 (PR#355)
Date: Tue, 20 Jun 2000 17:25:37 -0400

Guido van Rossum wrote:
> 
> I think I understand this.  It's happened to me too.  Pressing ^F5
> changes the focus to the PyShell window.  Pressing ^F5 again then
> indeed complains about that window being unsaved.
> 
> --Guido van Rossum (home page: http://www.python.org/~guido/)

Ah. Sure enough.   Perhaps the best thing to do
is just to have the little error message explain
which window is unsaved.  Include the title
of the unsaved window in the error box, maybe.

I'd be happy to send a patch, but the paperwork
would be terrible...


-------------------------------------------------------

Date: 2000-Aug-01 21:01
By: none

Comment:
From: Guido van Rossum <guido@python.org>
Subject: Re: [Python-bugs-list] IDLE-0.5 ctrl-F5 (PR#355)
Date: Tue, 20 Jun 2000 18:10:35 -0500

> > I think I understand this.  It's happened to me too.  Pressing ^F5
> > changes the focus to the PyShell window.  Pressing ^F5 again then
> > indeed complains about that window being unsaved.
> > 
> > --Guido van Rossum (home page: http://www.python.org/~guido/)
> 
> Ah. Sure enough.   Perhaps the best thing to do
> is just to have the little error message explain
> which window is unsaved.  Include the title
> of the unsaved window in the error box, maybe.
> 
> I'd be happy to send a patch, but the paperwork
> would be terrible...

No need for paperwork, just the disclaimer text.

But I think the better patch would be to make PyShell a special case
and make it rerun the last window that had the focus.

--Guido van Rossum (home page: http://www.python.org/~guido/)



-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110660&group_id=5470