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

Bug: Terminal width on Windows command is off by 1 #20

Closed
1 of 2 tasks
ivarstange opened this issue May 11, 2020 · 4 comments
Closed
1 of 2 tasks

Bug: Terminal width on Windows command is off by 1 #20

ivarstange opened this issue May 11, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@ivarstange
Copy link

ivarstange commented May 11, 2020

Is this a BUG REPORT or FEATURE REQUEST?:

  • bug
  • feature

Description of Bug or Feature

When generating the report, the last "|"-char for the table is on the next line, causing the output to look really weird. Expanding the windows command (terminal) width by 1 makes everything look nice again.

Environment

  • interrogate version(s): 1.1.4
  • Operating System(s): Windows 10
  • Python version(s): 3.7.6

I have not been able to check if it works with other versions of interrogate, OS or Python.

What happened

Last "|" char in the table goes to the next line.

What you expected to happen

Expect every output line to not be wrapped like this to the next line.

How to reproduce it (as minimally and precisely as possible)

Open Windows Command and run interrogate to produce results.

Anything else we need to know?

I've checked that this is not due to the output requiring this due to long outputs. There is plenty of available padding in each cell of the output.

Thank you for this awesome tool! :)

@econchick
Copy link
Owner

Hey @ivarstange - thanks so much for the bug! My apologies for the annoying issue - I'll take a look in the next couple of days.

@econchick econchick added the bug Something isn't working label May 11, 2020
@hectormz
Copy link

I noticed this too, but couldn't find the pattern. If I use Windows Terminal, it always correctly. And if I use any terminal inside VS Code, it's fine. But cmd/cmder/powershell on their own don't work.

Let me know if I can help check things out on Windows.

@econchick
Copy link
Owner

@hectormz @ivarstange if either of you have a moment, would you mind trying out #23 to see if that addresses the issue you both are seeing?

@econchick
Copy link
Owner

@ivarstange @hectormz I released version 1.1.5 in hopes that I've fixed the off-by-1 issue. Please feel free to re-open this ticket if you still experience issues!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants