This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients eryksun, paul.moore, steve.dower, tim.golden, zach.ware, 零欸特
Date 2018-11-29.22:03:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543529036.12.0.788709270274.issue35217@psf.upfronthosting.co.za>
In-reply-to
Content
The Windows console has a fixed number of history buffers. In Windows 7 the default maximum is four history buffers. In this case, if we run a script via cmd.exe -> py.exe -> python.exe, then only one history buffer remains for a child process. As you've observed, no history buffer is available for the fifth process if we run cmd.exe -> python.exe. 

You can increase the default maximum in the console's Alt+Space+D defaults dialog, under "Command History" -> "Number of Buffers". This corresponds to the "NumberOfHistoryBuffers" value in the registry key "HKCU\Console". 

You can increase the maximum for the current window in the console's Alt+Space+P properties dialog. If the current console was allocated by an application that was launched from a shortcut (i.e. a .LNK file), this property gets persisted in the shortcut itself. Otherwise it gets persisted in a registry key under "HKCU\Console" that's named for the startup window title. If no title was specified, the default title is the path to the executable, with backslashes replaced by underscore and the Windows directory as %SystemRoot%. For example, if you run cmd.exe from the Win+R run dialog, its console properties are stored in the registry key "HKCU\Console\%SystemRoot%_system32_cmd.exe".
History
Date User Action Args
2018-11-29 22:03:56eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, 零欸特
2018-11-29 22:03:56eryksunsetmessageid: <1543529036.12.0.788709270274.issue35217@psf.upfronthosting.co.za>
2018-11-29 22:03:56eryksunlinkissue35217 messages
2018-11-29 22:03:56eryksuncreate