[issue27603] Migrate IDLE context menu items to shell extension
Shane Smith added the comment: Would it be possible to allow the user to select whether they'd prefer a nested or flat context menu at install? I believe it went to nested as a result of issue23546. Unless there are a large number of installations (arbitrarily... perhaps 4 or more), the nested menu is a pain for a user like me who wants to open .py files in IDLE more than any other action. (If I may quote the fifth line of The Zen of Python... "Flat is better than nested.") With a little research, it was a fairly easy registry hack to de-nest the context menu. Still, a lot of people don't like to mess around in the registry, and user choice is usually a good thing. Thoughts? ------ nosy: +Shane Smith ___ Python tracker <http://bugs.python.org/issue27603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27603] Migrate IDLE context menu items to shell extension
Shane Smith added the comment: Hi Vedran, that seems to now be the default behavior, regardless of previous installs (my 3.6 was a clean install, and it's still nested). Kind of a pain if you want to edit with IDLE frequently. While we wait for a more integrated solution, the hackish way to restore desired behavior is to run a .bat file containing: REG DELETE "HKEY_CLASSES_ROOT\Python.File\shell\editwithidle" Then run a .reg file (also just a text file with altered extension so windows knows what to do with it) with: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Python.File\shell\Edit with IDLE 3.6\command] @="\"C:\\Program Files\\Python36\\pythonw.exe\" -m idlelib \"%L\" %*" -- ___ Python tracker <http://bugs.python.org/issue27603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27603] Migrate IDLE context menu items to shell extension
Shane Smith added the comment: I'm fine with a single implementation, so long as the implementation is what's best for the majority of users. Not my intent to increase the burden of work. So, let me ask the question alluded to in my first post: when is a nested menu actually desirable? I would argue that the vast majority of users have one or two versions of Python installed at any given time. And for that number, a flat menu is certainly preferred. The X.Y version numbering in the context menu introduced as a result of issue23546 solves said issue. I'm merely suggesting de-nesting the menu. -- ___ Python tracker <http://bugs.python.org/issue27603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27603] Migrate IDLE context menu items to shell extension
Shane Smith added the comment: Since you're a developer, I'm sure you need a lot of versions installed so you can check for backwards combatibility (spelling intentional). But until recently, only the most recent IDLE was in the context menu, so I'm guessing your workflow for that checking doesn't depend on the context menu. (I liked the old way, BTW, but I can see how someone might not). But so long as you're doing it the current way, it remains easily hacked back to the way I like it, so I don't have a whole lot to complain about. Carry on, good sir. -- ___ Python tracker <http://bugs.python.org/issue27603> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
