Skip to content
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

Malformed paste on Cmder/ConEmu #191

Closed
Apjue opened this issue May 23, 2018 · 8 comments
Closed

Malformed paste on Cmder/ConEmu #191

Apjue opened this issue May 23, 2018 · 8 comments
Labels
Area-Interaction Interacting with the vintage console window (as opposed to driving via API or hooks) Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Conhost For issues in the Console codebase Resolution-External For issues that are outside this codebase

Comments

@Apjue
Copy link

Apjue commented May 23, 2018

  • Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [version 10.0.17134.48]

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

(I am using Cmder v1.3.5, itself being a wrapper around ConEmu)
I'm copying some text into a bash.exe tab, for example dircolors --print-database > ~/.mydircolors and pasting it into Cmder

  • What's wrong / what should be happening instead:

The paste is malformed, for example I only have dircolors when pasting the command above
This problem only occurs when using bash.exe in Cmder, when using wslbridge* the paste is okay

*: This is wslbridge task command:
set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe --wsl -cur_console:pm:/mnt

(See also Maximus5/ConEmu#1314)

When pasting the same text into bash.exe without Cmder (standard windows's cmd), everything is fine
I don't know if I should create the issue here or on ConEmu's github, but the issue I linked is a bit dead

I can use wslbridge task (the "connector") but it behaves weirdly, I would like to stay with bash

@zadjii-msft
Copy link
Member

When pasting the same text into bash.exe without Cmder (standard windows's cmd), everything is fine

Then this definitely sounds like an issue with ConEmu then :) I'd follow up either on that issue or file a new one on the conemu repo, whetever's in line with their contribution policies.

@zadjii-msft zadjii-msft added Issue-Question For questions or discussion Resolution-External For issues that are outside this codebase labels May 23, 2018
@Maximus5
Copy link

It's not a ConEmu issue, but definitely a conhost and WinAPI problem.
I've reported this several times by mail to console team but it's still there.

Brief:

  1. ConEmu calls WriteConsoleInput to put text into conhost input buffer. There is no another way to do that.
  2. I don't know what does WSL/Bash, but when it runs directly in ConEmu (without wslbridge) input is always malformed.

With connector - everything is OK.
ConEmu uses the same method to transfer text.
I see only one conclusion from these facts.

@miniksa
Copy link
Member

miniksa commented May 23, 2018

@Maximus5, can you bump the mail thread? I'm sorry if you sent it to us in mail and we lost track of it.

@miniksa miniksa reopened this May 23, 2018
@miniksa miniksa added Product-Conhost For issues in the Console codebase and removed Resolution-External For issues that are outside this codebase Issue-Question For questions or discussion labels May 23, 2018
@miniksa
Copy link
Member

miniksa commented May 23, 2018

I think I found the mail thread. Is this Maximus5/ConEmu#760? I think I filed that as MSFT:8105691.
It is still on our backlog, we just haven't had time for it yet.

@Maximus5
Copy link

I'm really sorry, but I just realised that @S6066 uses old ConEmu build (18.02.06).
And there was fixed issue Maximus5/ConEmu#1545.
Malformed output was result of immediate reject from WriteConsoleInput if any item from lpBuffer has EventType=0.
Perhaps, this issue should be closed indeed.

@Apjue
Copy link
Author

Apjue commented May 24, 2018

I should have updated before creating the issues, sorry.
Does it mean it can be closed?

Edit: The issue no longer reproduces

@DHowett
Copy link
Member

DHowett commented May 25, 2018

If you've updated and the issue no longer reproduces, then yes.

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label May 17, 2019
@miniksa miniksa added Area-Interaction Interacting with the vintage console window (as opposed to driving via API or hooks) Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-External For issues that are outside this codebase and removed Mass-Chaos labels May 17, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 18, 2019
@miniksa
Copy link
Member

miniksa commented May 18, 2019

Closing as this appears to have solved itself over time.

@miniksa miniksa closed this as completed May 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Interaction Interacting with the vintage console window (as opposed to driving via API or hooks) Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Conhost For issues in the Console codebase Resolution-External For issues that are outside this codebase
Projects
None yet
Development

No branches or pull requests

5 participants