Line of text breaks to new line well past the end of screen space when using non-monospace fonts

[Maximus5]

Originally reported on Google Code with ID 1948

OS version:Win7 x64
ConEmu version: 150209[64]

When using a non-monospace Font like Verdana the linebreak happens too late (or too
early for some other fonts).

*Steps to reproduction*
1. Choose Font Verdana
2. type until line break

Reported by cmonsrslywtf on 2015-03-17 16:48:31

[Maximus5]

And what do you suggest?

That is a terminal with fixed cell-counted width. This is not a Word or SublimeText.

Reported by ConEmu.Maximus5 on 2015-03-17 17:02:52

• Labels added: Type-Other
• Labels removed: Type-Defect

[Maximus5]

Windows 8.1, ConEmu 150621 [64]

I use a fixed width font, and when entering text, the line breaks 2 characters too
early. This prevents "Detect line ends" from working.

Note, line breaking of text-output from commands works fine.  The line only breaks
too early when entering text.

My ConEmu.xml is attached, together with a screenshot showing the problem

Reported by m.gritsch on 2015-07-23 09:07:29

---

• Attachment: ConEmu.xml
• Attachment: Screenshot.png
  

[Maximus5]

@m.gritsch
ConEmu doesn't "break" lines, the OS itself is doing that.
You may check RealConsole to view what is there.
Also, there is "Bash margin" option designed for those shells which break line before
the edge.

Reported by ConEmu.Maximus5 on 2015-07-23 09:35:14

[Maximus5]

Ok, thanks for your quick answer.  So after displaying RealConsole, and seeing that
the line changes there also 2 characters too early, what can I do about it?  Thinks
are fine in the normal cmd window -- see attachments.

Reported by m.gritsch on 2015-07-23 11:41:26

---

• Attachment: RealConsole.png
  
• Attachment: cmd.png
  

[Maximus5]

1. You are using OldBuild.
2. Clink?
3. Attach this cmd.exe into ConEmu (Win-G) and show screenshots of Settings/Info pages
for both consoles.

Reported by ConEmu.Maximus5 on 2015-07-23 13:03:08

[Maximus5]

ad 1. as mentioned in Comment #2: ConEmu 150621 [64] so not that old.
ad 2. Yes, it seems Clink is the culprit! If I disable the checkbox "Use Clink in prompt"
and restart ConEmu, the line breaks correctly.

That's sad. Do I really have to ditch Clink?  I really like its reverse-i-search feature...
 Any idea, why Clink causes this problem?

Reported by m.gritsch on 2015-07-23 13:23:55

[Maximus5]

As I said, OldBuild. Current preview is 707 and alpha 722.

Clink related question must be posted on the project tracker. I'm not an author of
this third-party application and can't help you with its configuration.

Reported by ConEmu.Maximus5 on 2015-07-23 13:30:00

• Status changed: Done

[Maximus5]

BTW, if you create clink's issue, please post here the link.

Reported by ConEmu.Maximus5 on 2015-07-23 13:31:05

[Maximus5]

Well, you are right, I was not using the latest alpha version, but since the latest
version shows the same behaviour, updating did not help.  However, I understand, that
it is tiresome to get problems reported, which are already fixed in a newer version.

Thanks's for your help, and here is the Clink issue:
https://github.com/mridgers/clink/issues/337

Reported by m.gritsch on 2015-07-23 14:21:51

[markusgritsch]

Just for completeness: The issue https://github.com/mridgers/clink/issues/337 got fixed in Clink v0.4.5.

[Maximus5]

Wrong place for comment?

[markusgritsch]

What would have been the correct place?

[Maximus5]

My bad. This is OK.