Duplicate line down has changed behavior with Duplicate line up
See original GitHub issuePreviously when you duplicate line down
the newly created line was also selected. This is imo prefered behaviour because you could immediately move the newly copied lines with move line down
.
In Spyder 4.1.1 this has changed and the original lines stay selected, which is the old duplicate line up
behaviour. Thus, one has to move the original lines through the newly copied ones and then to the location where you want them.
Maybe this is the wanted behaviour, so I’m not sure about reporting it, and there’s an easy workaround - switch the current shortcuts between the two commands to retain the old behaviour 😄
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Duplicate Line behavior change - PSPad forum
If I select something in a line and I choose Duplicate line (for me it is the shortcut ctrl+D) it duplicates the line...
Read more >How do I duplicate a line or selection within Visual Studio Code?
4. I was frustrated by "copy lines down" shortcut which did not exactly behave like Sublime Text/Intellij Ctrl+D feature (it copied the entire...
Read more >change duplicate line shortcut · Issue #91789 · microsoft/vscode
change duplicate line shortcut to CTRL + SHIFT + Up/Down instead of ALT + SHIFT + Up/ Down because the ALT + SHIFT...
Read more >Duplicate Line (Copy Line Down) Shortcut in VS Code
In this video we'll go over the VS Code Keyboard Shortcut: Duplicate Line ( Copy Line Down ) -- spoiler alert -- it's...
Read more >Mac keyboard shortcuts - Apple Support
For example, to use Command-C (copy), press and hold the Command key, ... Some keys on some Apple keyboards have special symbols and ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes I think I inverted things by mistake. I can submit a PR that will switch this back to the original behaviour, this is very simple to achieve.
I just need to inverse the
after_current_line
argument inself.__duplicate_line_or_selection
calls and update the tests probably.Yeah I really wanted to make that gif 😄