<table><tr><td style="">mglb added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D12238">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D12238#264434" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D12238#264434</a>, <a href="https://phabricator.kde.org/p/hindenburg/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@hindenburg</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Also, I'm a little concerned that we're going to start having to request what version of libc users's have in bug reports. And then have to research how that version uses wcwidth.</p></div>
</blockquote>
<p>You are right here. I have wcwidth maps from several glibcs, so I am able to just grep a code point and verify if it has different width in some version. Sadly, this is not easily downloadable from some reliable source, so it is not an option to recommend.<br />
On the other hand, were there other bugs than "character width is wrong" or "cursor disappears on character/backspaces too much" (where it is obvious the width is wrong for the user), related to character width?</p>
<p>BTW. Why there is no "Please attach <tt style="background: #ebebeb; font-size: 13px;">konsole --show-info-for-a-bug-report</tt> output to the bug" and respective switch in Konsole, and custom additional info defined by a program in "report bug" feature? Could help in some cases, not only with this.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Where as now, we know everyone uses konsole_wcwidth.</p></blockquote>
<p>Sure, but we'll get less bugs than with konsole_wcwidth - people with newer libc won't have them, people with older version will get about as much as with konsole_wcwidth. Also, using system's wcwidth fixes bugs like "cursor in bash moves wrong" (392171) and similar problems with programs using system's wcwidth, for everyone.</p>
<p>The ultimate (and complex) solution I was thinking about would be something like:</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">width maps specified in files; user can create or download new ones</li>
<li class="remarkup-list-item">possibility to specify default map in profile (e.g. system's wcwidth-based, or generated straight from Unicode files)</li>
<li class="remarkup-list-item">possibility to specify separate map for app-screen programs (vim-based map for vim, tig-based for tig, etc)</li>
</ul>
<p>This would solve problems with custom implementations, different libc, user preferences (including "Unicode is wrong, I want it this way" or improved powerline-like features). But due to complexity it probably won't appear soon.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R319 Konsole</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D12238">https://phabricator.kde.org/D12238</a></div></div><br /><div><strong>To: </strong>mglb, Konsole<br /><strong>Cc: </strong>hindenburg, Konsole, herrold, ngraham, maximilianocuria<br /></div>