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 terry.reedy
Recipients Saimadhav.Heblikar, asvetlov, cheryl.sabella, ggenellina, gpolo, louielu, markroseman, mcepl, mrabarnett, rhettinger, terry.reedy, veganaiZe, wolma
Date 2019-06-03.04:59:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559537956.91.0.22818412698.issue5680@roundup.psfhosted.org>
In-reply-to
Content
Two design issues:

1. As I said 2017-06-20, msg296499, I expect to add more alternatives to the standard run to this menu option and dialog.  (Cheryl, I should have pointed you to this post as well as the later ones.)  I want to add just one new option to have only 1 new key to learn.  I already cannot remember all of them and I expect I am not the only one.  They need to be together on one dialog so that uses can conveniently pick multiple options when that makes sense.  Running in a console with args is completely sensible.  And exclusionary logic, such as 'Cannot supply arguments if no restart' should be easier on one dialog.

The configuration and pseudoevent names, perhaps 'run-custom', should be changed to reflect that now.  For the menu, I am less sure.  Perhaps 'Run Custom', 'Run Setup', 'Run with Alternatives', 'Alternate Runs'?

2. I am pretty sure I prefer shift-F5 for the key.  (But cannot be sure until I try it.)  Easier to learn I think.
History
Date User Action Args
2019-06-03 04:59:16terry.reedysetrecipients: + terry.reedy, rhettinger, ggenellina, gpolo, mcepl, mrabarnett, asvetlov, markroseman, wolma, Saimadhav.Heblikar, louielu, cheryl.sabella, veganaiZe
2019-06-03 04:59:16terry.reedysetmessageid: <1559537956.91.0.22818412698.issue5680@roundup.psfhosted.org>
2019-06-03 04:59:16terry.reedylinkissue5680 messages
2019-06-03 04:59:16terry.reedycreate