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

Alignment problem while using Vim Airline #1096

Closed
ajmathews opened this Issue Apr 8, 2017 · 8 comments

Comments

Projects
None yet
2 participants
@ajmathews

Versions

ConEmu build: 161206 x64
OS version: Windows Version 10.0.15058 Build 15058 x64
Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): Bash subsystem for Windows

Problem description

Whenever I open Vim with vim-airline enabled, the positioning of the bottom row seems misplaced. The colon ':' always appears on the second last line at the end. The typing cursor also appears 1 character away from the actual position. Please see the screenshot below,

image

Expected results

This is the expected behaviour. I see this when I disable airline.

image

With airline enabled, it works on the Windows bash terminal,

image

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Apr 10, 2017

Owner

Why did you crop the screenshot? Where is the StatusBar?

Owner

Maximus5 commented Apr 10, 2017

Why did you crop the screenshot? Where is the StatusBar?

@Maximus5 Maximus5 added the other-wsl label Apr 10, 2017

@ajmathews

This comment has been minimized.

Show comment
Hide comment
@ajmathews

ajmathews Apr 11, 2017

No reason. Is this what you want?

image

ajmathews commented Apr 11, 2017

No reason. Is this what you want?

image

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Apr 11, 2017

Owner

Almost. What is shown by "Terminal modes" status bar column?

Owner

Maximus5 commented Apr 11, 2017

Almost. What is shown by "Terminal modes" status bar column?

@ajmathews

This comment has been minimized.

Show comment
Hide comment
@ajmathews

ajmathews Apr 11, 2017

Says XTerm.

image

Says XTerm.

image

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Apr 11, 2017

Owner

Two notes.

  1. Seems like you are not using connector: http://conemu.github.io/en/CygwinMsysConnector.html
  2. Actual build at the moment is 170402.

Anyway, I think that it's not a ConEmu bug.

Owner

Maximus5 commented Apr 11, 2017

Two notes.

  1. Seems like you are not using connector: http://conemu.github.io/en/CygwinMsysConnector.html
  2. Actual build at the moment is 170402.

Anyway, I think that it's not a ConEmu bug.

@ajmathews

This comment has been minimized.

Show comment
Hide comment
@ajmathews

ajmathews Apr 11, 2017

Thanks @Maximus5 . I moved to the preview build now and it looks better. Couple of points id you don't mind commenting,
1) There is a blank line at the end though (screenshot) I get why this happens.
2) Also, would you be able to tell me which connector I would need to install, Cygwin, MSYS or MSYS2?
3) I have lost the ability to press up and down to go through the command history. I believe this is because the Terminal Mode has shifted to Windows after I installed the new build. It works when I change it to XTerm.

image

ajmathews commented Apr 11, 2017

Thanks @Maximus5 . I moved to the preview build now and it looks better. Couple of points id you don't mind commenting,
1) There is a blank line at the end though (screenshot) I get why this happens.
2) Also, would you be able to tell me which connector I would need to install, Cygwin, MSYS or MSYS2?
3) I have lost the ability to press up and down to go through the command history. I believe this is because the Terminal Mode has shifted to Windows after I installed the new build. It works when I change it to XTerm.

image

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Apr 11, 2017

Owner

Generally you need connector for cygwin/msys when you face cygwin/msys bug. The WSL is expected to be working properly without it. If not, you shall report the problem on the WSL issue tracker.

I believe if you would use predefined {bash} Task you will not see keyboard problem.

Owner

Maximus5 commented Apr 11, 2017

Generally you need connector for cygwin/msys when you face cygwin/msys bug. The WSL is expected to be working properly without it. If not, you shall report the problem on the WSL issue tracker.

I believe if you would use predefined {bash} Task you will not see keyboard problem.

@ajmathews

This comment has been minimized.

Show comment
Hide comment
@ajmathews

ajmathews Apr 11, 2017

For now when I switch it to Xterm it is working fine for me. That is all I need :)
Really appreciate the help! I will close the issue.

For now when I switch it to Xterm it is working fine for me. That is all I need :)
Really appreciate the help! I will close the issue.

@ajmathews ajmathews closed this Apr 11, 2017

Maximus5 added a commit that referenced this issue May 15, 2017

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