broken vertical line char #285

Closed
opened 2026-01-30 21:47:59 +00:00 by claunia · 8 comments
Owner

Originally created by @Ansuel on GitHub (May 26, 2018).

  • Your Windows build number: Microsoft Windows [Versione 10.0.17677.1000]

  • What you're doing and what's happening: make menuconfig command

cattura

  • What's wrong / what should be happening instead: as you can see from the screen, the vertical line char is broken and not displayed. Trying to paste it to a nano editor doesn't show anything, trying with other works... For example this is displayed ├ but this not ─
Originally created by @Ansuel on GitHub (May 26, 2018). * Your Windows build number: Microsoft Windows [Versione 10.0.17677.1000] * What you're doing and what's happening: make menuconfig command ![cattura](https://user-images.githubusercontent.com/20289090/40575412-ea9f10ae-60e4-11e8-885d-13b9059d1724.PNG) * What's wrong / what should be happening instead: as you can see from the screen, the vertical line char is broken and not displayed. Trying to paste it to a nano editor doesn't show anything, trying with other works... For example this is displayed ├ but this not ─
claunia added the Resolution-Duplicate label 2026-01-30 21:47:59 +00:00
Author
Owner

@zadjii-msft commented on GitHub (May 29, 2018):

What font is that?

This certainly smells like a dupe of #189 to me.

@zadjii-msft commented on GitHub (May 29, 2018): What font is that? This certainly smells like a dupe of #189 to me.
Author
Owner

@Ansuel commented on GitHub (May 29, 2018):

@zadjii-msft stock console font Consolas

in my case resize window doesn't fix the problem

@Ansuel commented on GitHub (May 29, 2018): @zadjii-msft stock console font Consolas in my case resize window doesn't fix the problem
Author
Owner

@Ansuel commented on GitHub (Jun 6, 2018):

any news for this?

@Ansuel commented on GitHub (Jun 6, 2018): any news for this?
Author
Owner

@zadjii-msft commented on GitHub (Jun 6, 2018):

Nope, I'll post an update when I make progress on this.

@zadjii-msft commented on GitHub (Jun 6, 2018): Nope, I'll post an update when I make progress on this.
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 3, 2018):

Oh, this is another case of #240. Marking duplicated!

@DHowett-MSFT commented on GitHub (Oct 3, 2018): Oh, this is another case of #240. Marking duplicated!
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 3, 2018):

As a workaround, you can set your TERM to vt100 or putty (if your distribution provides a putty termcap.) The putty terminal definition is almost exactly xterm-256color but it doesn't offer "repeat graphic character", the behavior dialog is using.

@DHowett-MSFT commented on GitHub (Oct 3, 2018): As a workaround, you can set your `TERM` to `vt100` or `putty` (if your distribution provides a putty termcap.) The `putty` terminal definition is _almost exactly `xterm-256color`_ but it doesn't offer "repeat graphic character", the behavior _dialog_ is using.
Author
Owner

@Ansuel commented on GitHub (Oct 3, 2018):

sorry but where should i set the TERM variable?

@Ansuel commented on GitHub (Oct 3, 2018): sorry but where should i set the TERM variable?
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 3, 2018):

Right before you launch menuconfig. Try this:

TERM=putty make menuconfig

(or:

export TERM=putty
make menuconfig

)

To determine if putty is a valid termcap, you can check whether /usr/share/terminfo/p/putty exists. If not, use vt100.

@DHowett-MSFT commented on GitHub (Oct 3, 2018): Right before you launch menuconfig. Try this: ``` TERM=putty make menuconfig ``` (or: ``` export TERM=putty make menuconfig ``` ) To determine if `putty` is a valid termcap, you can check whether `/usr/share/terminfo/p/putty` exists. If not, use `vt100`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#285