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

Better support for long commands #127

Open
scotthovestadt opened this issue Mar 4, 2016 · 5 comments
Open

Better support for long commands #127

scotthovestadt opened this issue Mar 4, 2016 · 5 comments

Comments

@scotthovestadt
Copy link
Contributor

After executing a long command, it appears on the next line and overlaps with the command prompt. Typing removes it, but you can't effectively see your previous command.

@dthree
Copy link
Owner

dthree commented Mar 4, 2016

kk. We should look at Inqurier to see if this is a problem there as well.

@milesj
Copy link
Contributor

milesj commented May 25, 2017

@scotthovestadt This is usually a problem with your terminal settings. Is this an isolated Vorpal problem?

@willclarktech
Copy link

willclarktech commented Nov 16, 2017

Not sure if I'm experiencing the same issue, but I'm also having problems with long commands:
vorpal_wrap_issue

Issues experienced above:

  1. Backspace deletes characters, but they remain displayed on lines beyond the first (when the cursor moves backwards I'm pressing backspace not an arrow key)
  2. Prompt jumping up to top line without clearing/cutting
  3. Weird pyramids of letters

I'm on:

  • OSX 10.12.6
  • Node 6.11.1 (but I also tried with 8.9.0)
  • iTerm 3.1.5 (but I also tried with Mac Terminal)
  • zsh 5.2 (but I also tried starting with bash)
  • Vorpal 1.11.4 (but I also tried with 1.12.0 and had the same issue)

Edit: Tried in tmux and the problem doesn't occur.

@parthms
Copy link

parthms commented Jun 12, 2018

Any updates on this bug?

@LeftoverChineseFood
Copy link

Hi, Inquirer user here. Looking at alternatives to try to find a fix, as I have this issue in my program as well. I am having these problems when I use Inquirer. They won't fix it for some reason.

If this project is based off of Inquirer, this is likely an Inquirer problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
6 participants