[Idle-dev] Serious problems getting idlefork to display on multiple xservers

[Bruce Sherwood]

> - And it would be nice to F5/"import module/"run" a module without  
>   saving it. What idlefork presumably does is save somewhere in     
/tmp.                                                                 
                                                                      
Indeed, every time you run (F5), idlefork saves the current file      
(somewhere). Once you do an actual named save operation, later saves  
go to that named file. The huge advantage is that if there is a crash 
of any kind, you are very unlikely to lose any work. The importance is
that novices aren't likely to think of saving their work periodically.
In two years of class use ONE student ONCE lost some edits! At the    
same time, idlefork supports infinite un-dos.                         
                                                                      
My only regret is that I personally know far too little to help you   
with your technical problem. But here's an uninformed thought of a    
possible temporary work-around: Could you set up multiple copies of   
Python and idlefork for your multiple users?                          
                                                                      
Bruce Sherwood                                                        
Joining the NCSU Dept. of Physics June 1, 2002