New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard shortcuts for copy / paste into console #235

Closed
MattiasFestin opened this Issue Apr 20, 2016 · 80 comments

Comments

Projects
None yet
@MattiasFestin

It would be nice to have keyboard shortcut for pasting into console instead of right clicking (Or window menu -> edit -> paste).

I tend to use my keyboard as much as possible. So it would be nice to have a shortcut like git bash:

  • copy = ctrl + insert
  • paste = shift + insert
@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Apr 20, 2016

Member

Agreed, this feedback is more general Windows cmd.exe than bash-specific. Here's a workaround to make copying and pasting easier for you:

Launch cmd.exe
Right click title bar, click Properties
Options Tab
Enable QuickEdit mode

Now you can highlight text with your mouse cursor, right click to copy, right click again to paste.

Member

benhillis commented Apr 20, 2016

Agreed, this feedback is more general Windows cmd.exe than bash-specific. Here's a workaround to make copying and pasting easier for you:

Launch cmd.exe
Right click title bar, click Properties
Options Tab
Enable QuickEdit mode

Now you can highlight text with your mouse cursor, right click to copy, right click again to paste.

@Birssan

This comment has been minimized.

Show comment
Hide comment
@Birssan

Birssan Apr 21, 2016

Agreed, this feedback is more general Windows cmd.exe than bash-specific

That's not entirely true, by default the new cmd.exe accepts text pasted with CTRL + V, it's only once you're in bash mode you can't paste anything with CTRL + V (not even CTRL + Shift + V like in Ubuntu terminal).

bash-copy

That's just an option in the properties (Enable shortcuts with Ctrl or something like that, my interface is not in English :) )

Birssan commented Apr 21, 2016

Agreed, this feedback is more general Windows cmd.exe than bash-specific

That's not entirely true, by default the new cmd.exe accepts text pasted with CTRL + V, it's only once you're in bash mode you can't paste anything with CTRL + V (not even CTRL + Shift + V like in Ubuntu terminal).

bash-copy

That's just an option in the properties (Enable shortcuts with Ctrl or something like that, my interface is not in English :) )

@mgleadow

This comment has been minimized.

Show comment
Hide comment
@mgleadow

mgleadow Apr 22, 2016

I think using the Ubuntu Style Ctrl-Shift-C would make sense, especially as Ctrl-C is a common interrupt

I'd also like to see things like emacs mode honoured where Ctrl-A / Ctrl-K work as expected

I think using the Ubuntu Style Ctrl-Shift-C would make sense, especially as Ctrl-C is a common interrupt

I'd also like to see things like emacs mode honoured where Ctrl-A / Ctrl-K work as expected

@mobluse

This comment has been minimized.

Show comment
Hide comment
@mobluse

mobluse May 1, 2016

AFAIK Ctrl+A and Ctrl+K already works as expected.

mobluse commented May 1, 2016

AFAIK Ctrl+A and Ctrl+K already works as expected.

@mgleadow

This comment has been minimized.

Show comment
Hide comment
@mgleadow

mgleadow May 3, 2016

@mobluse So they do. They didn't work for me the other day though, odd.

mgleadow commented May 3, 2016

@mobluse So they do. They didn't work for me the other day though, odd.

@MattiasFestin

This comment has been minimized.

Show comment
Hide comment
@MattiasFestin

MattiasFestin May 10, 2016

I think using the Ubuntu Style Ctrl-Shift-C would make sense, especially as Ctrl-C is a common interrupt

My toughs where the same with the Ctrl-C (and also Ctrl-V, not that common) interrupt signals.

That is why I suggested Ctrl + insert and Shift + insert. They work in windows now, so it is nothing new.
And they are compatible with the Linux keyboard interrupts.

I think using the Ubuntu Style Ctrl-Shift-C would make sense, especially as Ctrl-C is a common interrupt

My toughs where the same with the Ctrl-C (and also Ctrl-V, not that common) interrupt signals.

That is why I suggested Ctrl + insert and Shift + insert. They work in windows now, so it is nothing new.
And they are compatible with the Linux keyboard interrupts.

@mirao

This comment has been minimized.

Show comment
Hide comment
@mirao

mirao Jun 4, 2016

I vote for Ubuntu terminal shortcuts Ctrl + Shift + C/X/V as a primary ones and maybe an alternative Ctrl/Shift + Insert. But that's only my preference because I use bash on Linux in most cases.

mirao commented Jun 4, 2016

I vote for Ubuntu terminal shortcuts Ctrl + Shift + C/X/V as a primary ones and maybe an alternative Ctrl/Shift + Insert. But that's only my preference because I use bash on Linux in most cases.

@XaviTorello

This comment has been minimized.

Show comment
Hide comment
@XaviTorello

XaviTorello Jun 4, 2016

Why not to provide a way to configure the terminal shortcuts for this app? I'm not a win user, i'm just reviewing it

If not, @mirao proposal +1. I'm a *nix user in most cases too, and would be great maintain the default terminal shortcuts for the major distros.

Why not to provide a way to configure the terminal shortcuts for this app? I'm not a win user, i'm just reviewing it

If not, @mirao proposal +1. I'm a *nix user in most cases too, and would be great maintain the default terminal shortcuts for the major distros.

@GrimTheReaper

This comment has been minimized.

Show comment
Hide comment
@GrimTheReaper

GrimTheReaper Jun 20, 2016

I would like to have CTRL + Shift + C/X/V, although if possible my vote would be for it to be configurable.

I would like to have CTRL + Shift + C/X/V, although if possible my vote would be for it to be configurable.

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Jul 3, 2016

Collaborator

This is a current limitation in the Windows Console.

Console currently supports two input modes: 'processed' and 'raw'. In 'processed' mode, Windows Console pre-processes all keystrokes, handling several well-known chords consistently across cmd, PowerShell and elsewhere.

To better handle *NIX behavior, however Bash requests raw, un-pre-processed keyboard input. We do have a task on our backlog to add a "mildly-pre-processed" mode wherein Console will translate copy and paste key chords into the VT sequences expected by *NIX tools, shells, etc.

Collaborator

bitcrazed commented Jul 3, 2016

This is a current limitation in the Windows Console.

Console currently supports two input modes: 'processed' and 'raw'. In 'processed' mode, Windows Console pre-processes all keystrokes, handling several well-known chords consistently across cmd, PowerShell and elsewhere.

To better handle *NIX behavior, however Bash requests raw, un-pre-processed keyboard input. We do have a task on our backlog to add a "mildly-pre-processed" mode wherein Console will translate copy and paste key chords into the VT sequences expected by *NIX tools, shells, etc.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Aug 8, 2016

You can run REG.EXE add HKCU\Console /v QuickEdit /t REG_DWORD /d 1 /f as administrator in the Windows Command Prompt to enable QuickEdit by default.

This would let you:

  • copy text by highlighting text (left clicking) and then right clicking.
  • paste text by right clicking

To disable QuickEdit run REG.EXE add HKCU\Console /v QuickEdit /t REG_DWORD /d 0 /f as administrator in the Windows Command Prompt to disable it by default.

ghost commented Aug 8, 2016

You can run REG.EXE add HKCU\Console /v QuickEdit /t REG_DWORD /d 1 /f as administrator in the Windows Command Prompt to enable QuickEdit by default.

This would let you:

  • copy text by highlighting text (left clicking) and then right clicking.
  • paste text by right clicking

To disable QuickEdit run REG.EXE add HKCU\Console /v QuickEdit /t REG_DWORD /d 0 /f as administrator in the Windows Command Prompt to disable it by default.

@Pixinn

This comment has been minimized.

Show comment
Hide comment
@Pixinn

Pixinn Aug 15, 2016

I just installed "Bash on Windows" and I can copy / paste by doing

  • CTRL + SHIFT + C
  • Right Click

Pixinn commented Aug 15, 2016

I just installed "Bash on Windows" and I can copy / paste by doing

  • CTRL + SHIFT + C
  • Right Click
@brnelsons

This comment has been minimized.

Show comment
Hide comment
@brnelsons

brnelsons Oct 18, 2016

ctrl+shift+c
ctrl+shift+v
is what is preferred

ctrl+shift+c
ctrl+shift+v
is what is preferred

@konnichimade

This comment has been minimized.

Show comment
Hide comment
@konnichimade

konnichimade Oct 18, 2016

Here's another vote for Ctrl+Ins/Shift+Ins. This seems to be the standard for TTY apps, which is how I usually interact with Linux when in Windows.

Here's another vote for Ctrl+Ins/Shift+Ins. This seems to be the standard for TTY apps, which is how I usually interact with Linux when in Windows.

@jskopek

This comment has been minimized.

Show comment
Hide comment
@jskopek

jskopek Oct 28, 2016

+1 to Ctrl-V or some variant. Right clicking to paste works, but taking my hands off the keyboard is far from ideal.

jskopek commented Oct 28, 2016

+1 to Ctrl-V or some variant. Right clicking to paste works, but taking my hands off the keyboard is far from ideal.

@farahfa

This comment has been minimized.

Show comment
Hide comment
@farahfa

farahfa Oct 28, 2016

I agree that this should be configurable.. I, for one, would like to have either CTRL+SHIFT+C/X/Vor ALT+C/X/V (to simulate how things are done in Mac; the Command + C/X/V)... Also, it would be preferable to configure the "right click" behaviour as I'd expect it to give me a menu (to copy/cut/paste.. etc) as opposed to the "right click to paste" behaviour.. This is especially noticeable when using VIM.. ☹️

farahfa commented Oct 28, 2016

I agree that this should be configurable.. I, for one, would like to have either CTRL+SHIFT+C/X/Vor ALT+C/X/V (to simulate how things are done in Mac; the Command + C/X/V)... Also, it would be preferable to configure the "right click" behaviour as I'd expect it to give me a menu (to copy/cut/paste.. etc) as opposed to the "right click to paste" behaviour.. This is especially noticeable when using VIM.. ☹️

@brennanmh

This comment has been minimized.

Show comment
Hide comment
@brennanmh

brennanmh Feb 6, 2017

Another vote for gnome-terminal style cut and paste.

The main problem is that it is using the Windows Console app, which, at least from a linux guy, sucks, and always has.

If you really want to cater to linux folks, you need a much better terminal emulator.

Another vote for gnome-terminal style cut and paste.

The main problem is that it is using the Windows Console app, which, at least from a linux guy, sucks, and always has.

If you really want to cater to linux folks, you need a much better terminal emulator.

@TestSmirk

This comment has been minimized.

Show comment
Hide comment
@TestSmirk

TestSmirk Mar 7, 2017

mouse right click is not better than ctrl+shift+c\v.hope ASAP to support this function.

mouse right click is not better than ctrl+shift+c\v.hope ASAP to support this function.

@n3rd4i

This comment has been minimized.

Show comment
Hide comment
@n3rd4i

n3rd4i Apr 1, 2017

There is a workaround to the WSL Bash, paste issue:

One can simply do the following steps:

  1. open cmd.exe
  2. bash -c "pasted command here" ( this works because you are in cmd.exe )

The bash will exit after the command, I don't know how, yet, to keep it running after, like, "variable assign" from the cmd console. e.g. 'bash -ic "command and remain'

n3rd4i commented Apr 1, 2017

There is a workaround to the WSL Bash, paste issue:

One can simply do the following steps:

  1. open cmd.exe
  2. bash -c "pasted command here" ( this works because you are in cmd.exe )

The bash will exit after the command, I don't know how, yet, to keep it running after, like, "variable assign" from the cmd console. e.g. 'bash -ic "command and remain'

@florianmonfort

This comment has been minimized.

Show comment
Hide comment
@florianmonfort

florianmonfort Apr 13, 2017

So @bitcrazed this is in you guys backlog right? Any expectation on release date/time? Coming to a next major version or just simple Windows Update?

I actually "assumed" this would be solved with the Creators Update, and to my surprise it's not actually there. So wondering if we're expecting a time frame in years or in weeks lol

So @bitcrazed this is in you guys backlog right? Any expectation on release date/time? Coming to a next major version or just simple Windows Update?

I actually "assumed" this would be solved with the Creators Update, and to my surprise it's not actually there. So wondering if we're expecting a time frame in years or in weeks lol

@kavdev

This comment has been minimized.

Show comment
Hide comment
@kavdev

kavdev Apr 17, 2017

Agreed; @bitcrazed some sort of release timeframe would be awesome.

kavdev commented Apr 17, 2017

Agreed; @bitcrazed some sort of release timeframe would be awesome.

@plagov

This comment has been minimized.

Show comment
Hide comment
@plagov

plagov Apr 19, 2017

I was unpleasantly surprised that Bash on Windows doesn't support Shirt-Insert shortcut. This missing feature is the one that preventing me from switching from the Cygwin. Hope it will really be implemented soon.

plagov commented Apr 19, 2017

I was unpleasantly surprised that Bash on Windows doesn't support Shirt-Insert shortcut. This missing feature is the one that preventing me from switching from the Cygwin. Hope it will really be implemented soon.

@mobluse

This comment has been minimized.

Show comment
Hide comment
@mobluse

mobluse Apr 19, 2017

@plagov You could use WSLTTY to get Shift+Insert now: https://github.com/mintty/wsltty

mobluse commented Apr 19, 2017

@plagov You could use WSLTTY to get Shift+Insert now: https://github.com/mintty/wsltty

@plagov

This comment has been minimized.

Show comment
Hide comment
@plagov

plagov Apr 19, 2017

@mobluse just installing wsltty-0.7.6-install.exe and that's it?
Installed it, but still, Shift-Insert doesn't work. Or some extra configuration is required?

plagov commented Apr 19, 2017

@mobluse just installing wsltty-0.7.6-install.exe and that's it?
Installed it, but still, Shift-Insert doesn't work. Or some extra configuration is required?

@mobluse

This comment has been minimized.

Show comment
Hide comment
@mobluse

mobluse Apr 19, 2017

@plagov I think I didn't configure it, but it can be configured in Options/Keys (Alt+Space O Shift+Tab K).

mobluse commented Apr 19, 2017

@plagov I think I didn't configure it, but it can be configured in Options/Keys (Alt+Space O Shift+Tab K).

@stenrose

This comment has been minimized.

Show comment
Hide comment
@stenrose

stenrose Jun 2, 2017

Another vote for Ctrl-Shift-C and Ctrl-Shift-V copy/paste style.

stenrose commented Jun 2, 2017

Another vote for Ctrl-Shift-C and Ctrl-Shift-V copy/paste style.

@loxal

This comment has been minimized.

Show comment
Hide comment
@loxal

loxal Jul 19, 2017

This is a really critical issue. Can you prioritize please?

I already installed ConEmu to workaround this issue but ConEmu's bloated pseudo-feature set is just broken-by-design in so many other ways...

loxal commented Jul 19, 2017

This is a really critical issue. Can you prioritize please?

I already installed ConEmu to workaround this issue but ConEmu's bloated pseudo-feature set is just broken-by-design in so many other ways...

@sgoranson

This comment has been minimized.

Show comment
Hide comment
@sgoranson

sgoranson Jul 19, 2017

For now, I have been working around the issue with the following AutoHotkey script:

#IfWinActive, ahk_class ConsoleWindowClass
^+v::Rbutton
#ifWinActive

For now, I have been working around the issue with the following AutoHotkey script:

#IfWinActive, ahk_class ConsoleWindowClass
^+v::Rbutton
#ifWinActive
@loxal

This comment has been minimized.

Show comment
Hide comment
@loxal

loxal Jul 20, 2017

@sgoranson I've installed https://autohotkey.com/download/ compiled your-script.ahk and started the created your-script.exe file but still Bash keeps receiving ^V.

loxal commented Jul 20, 2017

@sgoranson I've installed https://autohotkey.com/download/ compiled your-script.ahk and started the created your-script.exe file but still Bash keeps receiving ^V.

@loxal

This comment has been minimized.

Show comment
Hide comment
@loxal

loxal Jul 20, 2017

What actually worked for me, was:

#IfWinActive ahk_class ConsoleWindowClass
^V::
SendInput {Raw}%clipboard%
return
#IfWinActive

loxal commented Jul 20, 2017

What actually worked for me, was:

#IfWinActive ahk_class ConsoleWindowClass
^V::
SendInput {Raw}%clipboard%
return
#IfWinActive
@sgoranson

This comment has been minimized.

Show comment
Hide comment
@sgoranson

sgoranson Jul 20, 2017

@loxal Good call. My version will do annoying things if the cursor is not over cmd.exe.

If anyone wants to use loxal's script with ConEmu, just change ConsoleWindowClass to VirtualConsoleClass

Personally, I prefer cmd.exe because it has far fewer issues for me with color and control characters. For example, I could not get CTRL-W working in ConEmu VIM, so I couldn't switch windows.

sgoranson commented Jul 20, 2017

@loxal Good call. My version will do annoying things if the cursor is not over cmd.exe.

If anyone wants to use loxal's script with ConEmu, just change ConsoleWindowClass to VirtualConsoleClass

Personally, I prefer cmd.exe because it has far fewer issues for me with color and control characters. For example, I could not get CTRL-W working in ConEmu VIM, so I couldn't switch windows.

@nimitbhargava

This comment has been minimized.

Show comment
Hide comment
@nimitbhargava

nimitbhargava Jul 30, 2017

Please do it! I can't click right always to paste. This is not how it should be. Using Bash on Ubuntu on Windows

Isn't this something that should come out of box and without requesting.
Also I find
image
but heck they don't work!

nimitbhargava commented Jul 30, 2017

Please do it! I can't click right always to paste. This is not how it should be. Using Bash on Ubuntu on Windows

Isn't this something that should come out of box and without requesting.
Also I find
image
but heck they don't work!

@avonar

This comment has been minimized.

Show comment
Hide comment
@avonar

avonar Jan 8, 2018

i really cant understand why so important thing doesnot fix.
WSL must help linux users and administrators to work in the windows wokspace. @iamakulov said ctrl+c is a good way cause he frequently switch between powershell and bash , so, i freqently switch between linux console and wsl. Changing mind from shift+insert to ctrl+c every time, makes me crazy, this ticket opened more than one year, its just ticket about fix control characters. But the greatest injustice is that in cmd shift+insert works!

avonar commented Jan 8, 2018

i really cant understand why so important thing doesnot fix.
WSL must help linux users and administrators to work in the windows wokspace. @iamakulov said ctrl+c is a good way cause he frequently switch between powershell and bash , so, i freqently switch between linux console and wsl. Changing mind from shift+insert to ctrl+c every time, makes me crazy, this ticket opened more than one year, its just ticket about fix control characters. But the greatest injustice is that in cmd shift+insert works!

@pinich

This comment has been minimized.

Show comment
Hide comment
@pinich

pinich Jan 8, 2018

If you'r using Git-Bash and the 'MINGW64' terminal emulator I found out that you can enable the linux terminal shortcuts like CTR+Shift+C/V:

  1. Open the option by clicking the left window icon on the left of the window and selecting options
  2. Select 'keys' from the tree.
  3. Check the CTR+SHift+letter shortcuts
  4. Click Save or Apply

2018-01-08 14_14_43-mingw64__c_users_pinich_desktop_tmp_tttttt

pinich commented Jan 8, 2018

If you'r using Git-Bash and the 'MINGW64' terminal emulator I found out that you can enable the linux terminal shortcuts like CTR+Shift+C/V:

  1. Open the option by clicking the left window icon on the left of the window and selecting options
  2. Select 'keys' from the tree.
  3. Check the CTR+SHift+letter shortcuts
  4. Click Save or Apply

2018-01-08 14_14_43-mingw64__c_users_pinich_desktop_tmp_tttttt

@eromoe

This comment has been minimized.

Show comment
Hide comment
@eromoe

eromoe Jan 31, 2018

@pinich Any idea for ctrl + u or ctrl + w cut word to windows clipboard ?

eromoe commented Jan 31, 2018

@pinich Any idea for ctrl + u or ctrl + w cut word to windows clipboard ?

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Jan 31, 2018

Collaborator

@avonar "I really cant understand why so important thing doesnot fix."

Appreciate your feedback. We're just as frustrated as you - this issue affects us all day long too!

However, we're a small team with a long prioritized backlog, but this item has been lower priority than some other critical work during the last several release cycles. However, we're hopeful that you won't have to wait much longer to see this ask make it above the 'cut' line ;)

Bear with us.

Collaborator

bitcrazed commented Jan 31, 2018

@avonar "I really cant understand why so important thing doesnot fix."

Appreciate your feedback. We're just as frustrated as you - this issue affects us all day long too!

However, we're a small team with a long prioritized backlog, but this item has been lower priority than some other critical work during the last several release cycles. However, we're hopeful that you won't have to wait much longer to see this ask make it above the 'cut' line ;)

Bear with us.

@hendrics

This comment has been minimized.

Show comment
Hide comment
@hendrics

hendrics Feb 26, 2018

oh, and i thought i was doing something wrong... i found an not idea workaround: configure bash.exe to be a terminal inside vscode. Then i found ctrl+v to work well and it also gets better colours out of the box. Ofc it is not ideal if you don't use vscode, but might save your some time if you have it installed.

oh, and i thought i was doing something wrong... i found an not idea workaround: configure bash.exe to be a terminal inside vscode. Then i found ctrl+v to work well and it also gets better colours out of the box. Ofc it is not ideal if you don't use vscode, but might save your some time if you have it installed.

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Feb 27, 2018

Collaborator

@DarthSpock Appreciate your analysis of how difficult it is (or is not) to modify the Console and/or WSL codebase. Sorry you think we're not putting much effort into our work, but I can attest from the insanely long hours the entire team has been pouring into these products over the last 3+ years, that you couldn't be further from the truth.

Fact remains that this feature hasn't been prioritized higher because there is an acceptible work-around (right click mouse/trackpad), and because we've had a MOUNTAIN of important, stretegic and tactical work that was of MUCH higher priority for many solid reasons.

We really do appreciate everyone's passion and enthusiasm - it literally fuels us every day - and we greatly appreciate your patience while we overhaul and modify a 30+ year old old, very fragile, utterly critical code-base. We're nearing the point where we can start delivering exciting UX features again - please bear with us just a little longer.

Collaborator

bitcrazed commented Feb 27, 2018

@DarthSpock Appreciate your analysis of how difficult it is (or is not) to modify the Console and/or WSL codebase. Sorry you think we're not putting much effort into our work, but I can attest from the insanely long hours the entire team has been pouring into these products over the last 3+ years, that you couldn't be further from the truth.

Fact remains that this feature hasn't been prioritized higher because there is an acceptible work-around (right click mouse/trackpad), and because we've had a MOUNTAIN of important, stretegic and tactical work that was of MUCH higher priority for many solid reasons.

We really do appreciate everyone's passion and enthusiasm - it literally fuels us every day - and we greatly appreciate your patience while we overhaul and modify a 30+ year old old, very fragile, utterly critical code-base. We're nearing the point where we can start delivering exciting UX features again - please bear with us just a little longer.

@iamakulov

This comment has been minimized.

Show comment
Hide comment
@iamakulov

iamakulov Feb 27, 2018

@bitcrazed Hey! I wanted to say you folks thank you for working on WSL and console and doing your job. Seriously, WSL is an amazing piece of work I love using every day.

It might be easy to lose enthusiasm when your job is criticized so often. I just wanted to remind that many-many more users don’t say anything because they like using your product and don’t have any issues with it. (And they like it because you did your job great.)

@bitcrazed Hey! I wanted to say you folks thank you for working on WSL and console and doing your job. Seriously, WSL is an amazing piece of work I love using every day.

It might be easy to lose enthusiasm when your job is criticized so often. I just wanted to remind that many-many more users don’t say anything because they like using your product and don’t have any issues with it. (And they like it because you did your job great.)

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Feb 28, 2018

Collaborator

Many thanks @iamakulov - I and the entire team appreciate your (and everyone else's) support :) We LITERALLY couldn't have made WSL & Console as good as they are today without all the support, bugs, and feedback. And we've still got a lot to do yet, so please do keep the feedback coming!

We much prefer to know what you need us to build, and/or how something should work, not how we should implement it. The latter requires a comprehensive understanding of many factors which few outside the team fully grasp, including:

  • the complexity, fragility, modernity, etc. of the code involved
  • the built & test infrastructure required to build, package and deliver the bits
  • the processes required to effect the necessary changes
  • the timescales during which changes can be made during a release cycle
  • the availability of the staff with the domain knowledge, and skills required to correctly implement the feature

Heck, it's hard enough for those inside the team to figure much of this out ;)

So, please do keep the feedback coming, continue to work with us & help us define, build, and deliver a WSL & Console that meets all our needs and gives us the crazy-powerful platform we all want so very much 😁

Collaborator

bitcrazed commented Feb 28, 2018

Many thanks @iamakulov - I and the entire team appreciate your (and everyone else's) support :) We LITERALLY couldn't have made WSL & Console as good as they are today without all the support, bugs, and feedback. And we've still got a lot to do yet, so please do keep the feedback coming!

We much prefer to know what you need us to build, and/or how something should work, not how we should implement it. The latter requires a comprehensive understanding of many factors which few outside the team fully grasp, including:

  • the complexity, fragility, modernity, etc. of the code involved
  • the built & test infrastructure required to build, package and deliver the bits
  • the processes required to effect the necessary changes
  • the timescales during which changes can be made during a release cycle
  • the availability of the staff with the domain knowledge, and skills required to correctly implement the feature

Heck, it's hard enough for those inside the team to figure much of this out ;)

So, please do keep the feedback coming, continue to work with us & help us define, build, and deliver a WSL & Console that meets all our needs and gives us the crazy-powerful platform we all want so very much 😁

@ankitkk

This comment has been minimized.

Show comment
Hide comment

ankitkk commented Mar 14, 2018

upvote.

@n3rd4i

This comment has been minimized.

Show comment
Hide comment
@n3rd4i

n3rd4i Mar 15, 2018

There is a way to paste into WSL console using only keyboard, procedure is as follows:
Requirement: needs to be only ONE WSL window open (at least in combined taskbar buttons)

  1. WIN + T -- use this key shortcut until you reach to the WSL window (assuming there is at least one)
  2. SHIFT + F10 -- bring-up context menu for this window
  3. E + P -- Edit and Paste (context menu entries)

n3rd4i commented Mar 15, 2018

There is a way to paste into WSL console using only keyboard, procedure is as follows:
Requirement: needs to be only ONE WSL window open (at least in combined taskbar buttons)

  1. WIN + T -- use this key shortcut until you reach to the WSL window (assuming there is at least one)
  2. SHIFT + F10 -- bring-up context menu for this window
  3. E + P -- Edit and Paste (context menu entries)
@FredyC

This comment has been minimized.

Show comment
Hide comment
@FredyC

FredyC Mar 15, 2018

@n3rd4i Sadly, the Shift + F10 doesn't work in Powershell window. If there would be another binding for that, this would be a viable approach, although I am not sure you have mentioned Win+T, that's unrelated :)

FredyC commented Mar 15, 2018

@n3rd4i Sadly, the Shift + F10 doesn't work in Powershell window. If there would be another binding for that, this would be a viable approach, although I am not sure you have mentioned Win+T, that's unrelated :)

@jesseconnell

This comment has been minimized.

Show comment
Hide comment
@jesseconnell

jesseconnell Mar 15, 2018

@FredyC It works for me - the Win+T cycles focus through the task bar mini-windows (or whatever you call them) - those windows accept Shift+F10. It opens the little shortcut window thingy that Alt+Space normally does (or right-clicking the top left corner of the window).

BTW, It would be a usable workaround if Alt+Space could optionally be configured to actually get processed normally. I would guess some action had to be taken to supersede the usual Windows handling of that. If so, seems like a registry key hack could make it skip that action.

@FredyC It works for me - the Win+T cycles focus through the task bar mini-windows (or whatever you call them) - those windows accept Shift+F10. It opens the little shortcut window thingy that Alt+Space normally does (or right-clicking the top left corner of the window).

BTW, It would be a usable workaround if Alt+Space could optionally be configured to actually get processed normally. I would guess some action had to be taken to supersede the usual Windows handling of that. If so, seems like a registry key hack could make it skip that action.

@FredyC

This comment has been minimized.

Show comment
Hide comment
@FredyC

FredyC Mar 15, 2018

Ah, I see now, that works indeed, but honestly, it might be just faster to grab that mouse and click instead of cycling through all windows with Win+T :)

It seems you don't even need to click on corner icon, right clicking on titlebar works and then you just hit E + P and done. Definitely easier :) Only wish it would be some other letters as to hit P I have to move away from mouse ... oh well.

FredyC commented Mar 15, 2018

Ah, I see now, that works indeed, but honestly, it might be just faster to grab that mouse and click instead of cycling through all windows with Win+T :)

It seems you don't even need to click on corner icon, right clicking on titlebar works and then you just hit E + P and done. Definitely easier :) Only wish it would be some other letters as to hit P I have to move away from mouse ... oh well.

@jesseconnell

This comment has been minimized.

Show comment
Hide comment
@jesseconnell

jesseconnell Mar 15, 2018

"might be faster to grab that mouse..." Oh right! That's a great workaround - I suggest closing the issue. :trollface:

"might be faster to grab that mouse..." Oh right! That's a great workaround - I suggest closing the issue. :trollface:

@xdfil

This comment has been minimized.

Show comment
Hide comment
@xdfil

xdfil Mar 16, 2018

xdfil commented Mar 16, 2018

@zerocool4u2

This comment has been minimized.

Show comment
Hide comment
@zerocool4u2

zerocool4u2 Mar 16, 2018

Hi, three months ago I posted a zip file with scripts for a workaround on ctrl+v and ctrl+shift+v on console, they are really easy to use and honestly they are the more easy workaround I found, thanks again to @sgoranson and @loxal who share how to do this before me.

  1. choose an exe file from the zip, ctrl or ctrl+shift
  2. test it on bash, you will also get a tray icon to know that it is open, if everything works go to step 5
  3. something went wrong or you are using another shell, install autohotkey and edit the files with extension ahk, above are comments about this that might be helpful
  4. if you don't want an extra program on your system, you can compile your code to an exe file on autohotkey and uninstall it
  5. everything working? perfect add it to a startup program, to not have to open it every time.
  6. here are some bat files to do so
@echo off
SET bashPaste=your path to exe here

rem add on start
@reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run" /t REG_SZ /v "bash paste" /d "\"%bashPaste%\"" /f
pause
  1. when this is officially implemented, here is the bat to clean the startup program
@echo off

rem remove
@reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run" /v "bash paste" /f
pause

I know that is annoying to not have it natively yet, but I'm sure there is a good reason behind it, I share the sentiment of @xdfil if you are a hardcore DevOps or a Pentester, they are a lot of important things that are not implemented yet, but for others who work on back ends like rails for example or many many others fields, this is a game changer, my life has been a lot easier for the past 2 years (06-2016 I believe), when pretty much all I need it was working as expected, been able to not have to jump between OS's is priceless for me, sincerely. Nowadays, I love my console, It could be better?, sure, but every patch I found something new to take advantage and hopefully soon, everything would work and I will be able to hack my neighbor with aircrack.

My current console after some tweaks

imagen

Hi, three months ago I posted a zip file with scripts for a workaround on ctrl+v and ctrl+shift+v on console, they are really easy to use and honestly they are the more easy workaround I found, thanks again to @sgoranson and @loxal who share how to do this before me.

  1. choose an exe file from the zip, ctrl or ctrl+shift
  2. test it on bash, you will also get a tray icon to know that it is open, if everything works go to step 5
  3. something went wrong or you are using another shell, install autohotkey and edit the files with extension ahk, above are comments about this that might be helpful
  4. if you don't want an extra program on your system, you can compile your code to an exe file on autohotkey and uninstall it
  5. everything working? perfect add it to a startup program, to not have to open it every time.
  6. here are some bat files to do so
@echo off
SET bashPaste=your path to exe here

rem add on start
@reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run" /t REG_SZ /v "bash paste" /d "\"%bashPaste%\"" /f
pause
  1. when this is officially implemented, here is the bat to clean the startup program
@echo off

rem remove
@reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run" /v "bash paste" /f
pause

I know that is annoying to not have it natively yet, but I'm sure there is a good reason behind it, I share the sentiment of @xdfil if you are a hardcore DevOps or a Pentester, they are a lot of important things that are not implemented yet, but for others who work on back ends like rails for example or many many others fields, this is a game changer, my life has been a lot easier for the past 2 years (06-2016 I believe), when pretty much all I need it was working as expected, been able to not have to jump between OS's is priceless for me, sincerely. Nowadays, I love my console, It could be better?, sure, but every patch I found something new to take advantage and hopefully soon, everything would work and I will be able to hack my neighbor with aircrack.

My current console after some tweaks

imagen

@zadjii-msft

This comment has been minimized.

Show comment
Hide comment
@zadjii-msft

zadjii-msft Mar 20, 2018

Member

No need for people to get salty, a little patience goes a long way:

image

Just checked it in. See y'all in skip-ahead.


Before people ask, there is a plan in play for more customizable and configurable keyboard shortcuts, but that's more than a release away from here. This is a stopgap until we can complete that work.

Member

zadjii-msft commented Mar 20, 2018

No need for people to get salty, a little patience goes a long way:

image

Just checked it in. See y'all in skip-ahead.


Before people ask, there is a plan in play for more customizable and configurable keyboard shortcuts, but that's more than a release away from here. This is a stopgap until we can complete that work.

@loxal

This comment has been minimized.

Show comment
Hide comment
@loxal

loxal Mar 21, 2018

Nice but when can we expect this feature in the Windows release? Many people got salty because this most basic feature is supported in macOS since a decade whereas Windows took "a bit" longer. Legacy should not be an excuse. I suppose that macOS had to solve similar problems and legacy implementations can be always resolved with explicit opt-in implementations.

loxal commented Mar 21, 2018

Nice but when can we expect this feature in the Windows release? Many people got salty because this most basic feature is supported in macOS since a decade whereas Windows took "a bit" longer. Legacy should not be an excuse. I suppose that macOS had to solve similar problems and legacy implementations can be always resolved with explicit opt-in implementations.

@zadjii-msft

This comment has been minimized.

Show comment
Hide comment
@zadjii-msft

zadjii-msft Mar 21, 2018

Member

The next full release of Windows with this enabled will be whatever comes after Spring Creator's Update (2Fall2Creators Update?).

Member

zadjii-msft commented Mar 21, 2018

The next full release of Windows with this enabled will be whatever comes after Spring Creator's Update (2Fall2Creators Update?).

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Mar 21, 2018

Collaborator

@loxal & @ALL

We understand the frustration - we feel it all day too because, unsurprisingly, we all live in the Console all day long.

However, simple physics have prevented this feature from bubbling high-enough up our prioritized bug list to receive attention until recently: Console has a small team of 3 who've been working at breakneck speed to add the MANY feature improvements you've all seen over the last 2+ years, adding masses of VT support, 24-bit color, etc. while re-engineering & modernizing a complex 30+ year old code-base.

Legacy may not be an excuse in your mind, but it's a reality that's unavoidable. If we "break" the Console's existing Windows behaviors, we hear from 1000x more users than if we "break" a Linux user's workflow.

So, understand if there's an issue that appears to be "simple to fix" and it hasn't been, then it's safe to assume that there's a very good reason it's not yet been fixed, frustrating though the delays may be at times.

We greatly appreciate everyone's continued patience and continued feedback & encourage y'all to keep it coming: It helps us find & fix the issues that matter in a sane prioritized order.

Collaborator

bitcrazed commented Mar 21, 2018

@loxal & @ALL

We understand the frustration - we feel it all day too because, unsurprisingly, we all live in the Console all day long.

However, simple physics have prevented this feature from bubbling high-enough up our prioritized bug list to receive attention until recently: Console has a small team of 3 who've been working at breakneck speed to add the MANY feature improvements you've all seen over the last 2+ years, adding masses of VT support, 24-bit color, etc. while re-engineering & modernizing a complex 30+ year old code-base.

Legacy may not be an excuse in your mind, but it's a reality that's unavoidable. If we "break" the Console's existing Windows behaviors, we hear from 1000x more users than if we "break" a Linux user's workflow.

So, understand if there's an issue that appears to be "simple to fix" and it hasn't been, then it's safe to assume that there's a very good reason it's not yet been fixed, frustrating though the delays may be at times.

We greatly appreciate everyone's continued patience and continued feedback & encourage y'all to keep it coming: It helps us find & fix the issues that matter in a sane prioritized order.

@kavdev

This comment has been minimized.

Show comment
Hide comment
@kavdev

kavdev Mar 21, 2018

"Legacy should not be an excuse"

@loxal That's actually a pretty damn good excuse in my book. A small team trying to modernize 30+ years of legacy code is a massive undertaking. I wouldn't wish it upon my worst enemy lol

Just think of how many global enterprise users of windows there are. Breaking compatibility in something so foundational as the console framework would be an SLA nightmare.

It's a lot to ask from all of us, but patience is key here. I think we're just all glad to see bash make its way into windows in the first place; look at how far we've come in 2 years!

All that said, @bitcrazed: do you see the Console team getting more resources any time soon or are you guys at optimal stride with 3 people?

kavdev commented Mar 21, 2018

"Legacy should not be an excuse"

@loxal That's actually a pretty damn good excuse in my book. A small team trying to modernize 30+ years of legacy code is a massive undertaking. I wouldn't wish it upon my worst enemy lol

Just think of how many global enterprise users of windows there are. Breaking compatibility in something so foundational as the console framework would be an SLA nightmare.

It's a lot to ask from all of us, but patience is key here. I think we're just all glad to see bash make its way into windows in the first place; look at how far we've come in 2 years!

All that said, @bitcrazed: do you see the Console team getting more resources any time soon or are you guys at optimal stride with 3 people?

@zadjii-msft

This comment has been minimized.

Show comment
Hide comment
@zadjii-msft

zadjii-msft Mar 21, 2018

Member

do you see the Console team getting more resources any time soon or are you guys at optimal stride with 3 people?

@kavdev I don't think resource allocation is really something any of us on the Console team are at the pay scale to discuss. I think we'd all love to have more resources, more devs, to be able to churn out more features. Obviously, though - we're all on this team because of how passionate we are about it so of course we want more resources to be able to deliver more features.

It probably doesn't help that we keep rocking it with only 3 devs - what other team has that kind of feature/dev ratio? 😝

Member

zadjii-msft commented Mar 21, 2018

do you see the Console team getting more resources any time soon or are you guys at optimal stride with 3 people?

@kavdev I don't think resource allocation is really something any of us on the Console team are at the pay scale to discuss. I think we'd all love to have more resources, more devs, to be able to churn out more features. Obviously, though - we're all on this team because of how passionate we are about it so of course we want more resources to be able to deliver more features.

It probably doesn't help that we keep rocking it with only 3 devs - what other team has that kind of feature/dev ratio? 😝

@DarthSpock

This comment has been minimized.

Show comment
Hide comment
@DarthSpock

DarthSpock Mar 21, 2018

Idea here: Open-source the console. If Microsoft doesn't want to hire more console devs, then get devs to do it for free! Pretty sure there's been enough enthusiasm gone around to get a bit of help. Of course to avoid legal hassle, they'd probably have to reduce the cost of the OS by X amount since they probably wouldn't want to compensate anyone for their service to a product that they sell that uses the work. Probably still much more complex than that but they've open-sourced Powershell and there's VS Code..plus you've got the ColorTool which is open-source. I would think it's less of a stretch to open-source the console than it is to open-source WSL or especially Windows (as great as that would be) but who knows? Maybe it IS a big stretch in MS's mind.

DarthSpock commented Mar 21, 2018

Idea here: Open-source the console. If Microsoft doesn't want to hire more console devs, then get devs to do it for free! Pretty sure there's been enough enthusiasm gone around to get a bit of help. Of course to avoid legal hassle, they'd probably have to reduce the cost of the OS by X amount since they probably wouldn't want to compensate anyone for their service to a product that they sell that uses the work. Probably still much more complex than that but they've open-sourced Powershell and there's VS Code..plus you've got the ColorTool which is open-source. I would think it's less of a stretch to open-source the console than it is to open-source WSL or especially Windows (as great as that would be) but who knows? Maybe it IS a big stretch in MS's mind.

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Mar 21, 2018

Collaborator

@DarthSpock Open-sourcing the console is something we discuss regularly. While it's not on the cards in the near term, it's not entirely out of the realm of possibility. One of the biggest challenges, however, is that the Console is FARRRRR from being in a useful shape for others to rapidly comprehend and contribute to in a meaningful way. Even internally!!

As @zadjii-msft points out above - we'd love to have "some more dev resources" on the team, but at the same time, be they full-time employees or community contributors, additional resources will decrease productivity of an established team - a team who've spent the last 3 years unpicking and understanding, and mastering every corner of a large, old, messy, confusing, but utterly essential code-base.

And as @zadjii-msft points out - though it may not be apparent from the outside - the 3 devs we have keep overachieving in every release. Maybe if they struggled and complained more, we might get more resources.

We'll bear that strategy in mind for the future ;)

Collaborator

bitcrazed commented Mar 21, 2018

@DarthSpock Open-sourcing the console is something we discuss regularly. While it's not on the cards in the near term, it's not entirely out of the realm of possibility. One of the biggest challenges, however, is that the Console is FARRRRR from being in a useful shape for others to rapidly comprehend and contribute to in a meaningful way. Even internally!!

As @zadjii-msft points out above - we'd love to have "some more dev resources" on the team, but at the same time, be they full-time employees or community contributors, additional resources will decrease productivity of an established team - a team who've spent the last 3 years unpicking and understanding, and mastering every corner of a large, old, messy, confusing, but utterly essential code-base.

And as @zadjii-msft points out - though it may not be apparent from the outside - the 3 devs we have keep overachieving in every release. Maybe if they struggled and complained more, we might get more resources.

We'll bear that strategy in mind for the future ;)

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Mar 21, 2018

Collaborator

@kavdev - many thanks :)

We're excited to come into work to improve the Console in tiny/unmeasurable, huge/significant ways each and every day. We're all passionate command-line nerds and do this work because we believe Windows users (including us) deserve a kick-a$$ command-line experience. We'll get there - just stick with us while we wrestle this beast into shape :)

Collaborator

bitcrazed commented Mar 21, 2018

@kavdev - many thanks :)

We're excited to come into work to improve the Console in tiny/unmeasurable, huge/significant ways each and every day. We're all passionate command-line nerds and do this work because we believe Windows users (including us) deserve a kick-a$$ command-line experience. We'll get there - just stick with us while we wrestle this beast into shape :)

@FredyC

This comment has been minimized.

Show comment
Hide comment
@FredyC

FredyC Mar 21, 2018

It must be a really amazing experience to be on such team, sounds like a well-oiled machine so to speak. Keep up great work!

FredyC commented Mar 21, 2018

It must be a really amazing experience to be on such team, sounds like a well-oiled machine so to speak. Keep up great work!

@renzok

This comment has been minimized.

Show comment
Hide comment
@renzok

renzok Mar 21, 2018

renzok commented Mar 21, 2018

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Mar 22, 2018

Collaborator

@FredyC & @renzok - It is genuinely humbling to work with the awesome WSL and Console engineering teams, and with so many of you in the community. I've learned SO MUCH in the last couple of years and continue to do so daily.

We're like swans - we appear calm and collected up-top, but are paddling like fury underneath 😁

Collaborator

bitcrazed commented Mar 22, 2018

@FredyC & @renzok - It is genuinely humbling to work with the awesome WSL and Console engineering teams, and with so many of you in the community. I've learned SO MUCH in the last couple of years and continue to do so daily.

We're like swans - we appear calm and collected up-top, but are paddling like fury underneath 😁

@bitcrazed

This comment has been minimized.

Show comment
Hide comment
@bitcrazed

bitcrazed Apr 13, 2018

Collaborator

Excited (relieved?) to finally be able to announce that this issue is now fixed (by @zadjii-msft)! Copy and Paste arrives for Linux/WSL Consoles

Marked as fixed in insiders build 17643. Will ship in Win10 18H2 release.

Closing since the work is now done.

Collaborator

bitcrazed commented Apr 13, 2018

Excited (relieved?) to finally be able to announce that this issue is now fixed (by @zadjii-msft)! Copy and Paste arrives for Linux/WSL Consoles

Marked as fixed in insiders build 17643. Will ship in Win10 18H2 release.

Closing since the work is now done.

@bitcrazed bitcrazed closed this Apr 13, 2018

@Pixinn

This comment has been minimized.

Show comment
Hide comment
@Pixinn

Pixinn Apr 14, 2018

That's a great news! Thanks for all the hard work! 👍

Pixinn commented Apr 14, 2018

That's a great news! Thanks for all the hard work! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment