From f508000f99b6a065be6f80045e3ad23c70800f0d Mon Sep 17 00:00:00 2001 From: "Jules Lasne (jlasne)" Date: Tue, 3 Mar 2020 21:56:58 +0100 Subject: [PATCH 1/2] Fixed double Options in idle.rst --- Doc/library/idle.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/idle.rst b/Doc/library/idle.rst index f15f46b788b36a..afc2bd6a4650f8 100644 --- a/Doc/library/idle.rst +++ b/Doc/library/idle.rst @@ -689,7 +689,7 @@ When IDLE first starts, it attempts to read user configuration files in ``~/.idlerc/`` (~ is one's home directory). If there is a problem, an error message should be displayed. Leaving aside random disk glitches, this can be prevented by never editing the files by hand, using the configuration -dialog, under Options, instead Options. Once it happens, the solution may +dialog, under Options. Once it happens, the solution may be to delete one or more of the configuration files. If IDLE quits with no message, and it was not started from a console, try From 43f8320eefb834b92b7d6eef8ee6866170a06136 Mon Sep 17 00:00:00 2001 From: Terry Jan Reedy Date: Thu, 5 Mar 2020 20:11:29 -0500 Subject: [PATCH 2/2] Update idle.rst Make additional small changes in the preceding and following paragraphs. --- Doc/library/idle.rst | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/Doc/library/idle.rst b/Doc/library/idle.rst index afc2bd6a4650f8..fd6e309567de39 100644 --- a/Doc/library/idle.rst +++ b/Doc/library/idle.rst @@ -681,19 +681,22 @@ clash, or cannot or does not want to run as admin, it might be easiest to completely remove Python and start over. A zombie pythonw.exe process could be a problem. On Windows, use Task -Manager to detect and stop one. Sometimes a restart initiated by a program -crash or Keyboard Interrupt (control-C) may fail to connect. Dismissing -the error box or Restart Shell on the Shell menu may fix a temporary problem. +Manager to check for one and stop it if there is. Sometimes a restart +initiated by a program crash or Keyboard Interrupt (control-C) may fail +to connect. Dismissing the error box or using Restart Shell on the Shell +menu may fix a temporary problem. When IDLE first starts, it attempts to read user configuration files in ``~/.idlerc/`` (~ is one's home directory). If there is a problem, an error message should be displayed. Leaving aside random disk glitches, this can -be prevented by never editing the files by hand, using the configuration -dialog, under Options. Once it happens, the solution may -be to delete one or more of the configuration files. +be prevented by never editing the files by hand. Instead, use the +configuration dialog, under Options. Once there is an error in a user +configuration file, the best solution may be to delete it and start over +with the settings dialog. If IDLE quits with no message, and it was not started from a console, try -starting from a console (``python -m idlelib``) and see if a message appears. +starting it from a console or terminal (``python -m idlelib``) and see if +this results in an error message. Running user code ^^^^^^^^^^^^^^^^^