On 2016-07-14 19:27:52 +0200, Sven Joachim wrote:
> On 2016-07-13 18:24 -0700, Vincent Lefevre wrote:
> > Could this depend on some library version or on the font?
>
> On the latter. With the default font I see no corruption, but with the
> 9x15 font, for instance. See the attached screenshot.
On Wed, Jul 13, 2016 at 08:23:34PM +0200, Sven Joachim wrote:
> On 2016-06-22 13:46 +0200, Vincent Lefevre wrote:
>
> > Control: reassign -1 xterm 325-1
>
> This problem seems to stem from the attempt to fix bug #738794, at least
> it is not present in xterm 324 and earlier.
agreed (I'm
On 2016-07-15 05:02 -0400, Thomas Dickey wrote:
> On Thu, Jul 14, 2016 at 07:27:52PM +0200, Sven Joachim wrote:
>> On 2016-07-13 18:24 -0700, Vincent Lefevre wrote:
>>
>> > On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote:
>> >> I don't see the behavior which is described, and haven't seen any
On Thu, Jul 14, 2016 at 07:27:52PM +0200, Sven Joachim wrote:
> On 2016-07-13 18:24 -0700, Vincent Lefevre wrote:
>
> > On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote:
> >> I don't see the behavior which is described, and haven't seen any
> >> suitable justification for marking this as a
On 2016-07-13 18:24 -0700, Vincent Lefevre wrote:
> On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote:
>> I don't see the behavior which is described, and haven't seen any
>> suitable justification for marking this as a "grave" issue, rather
>> than "normal". Keep in mind that this is a rarely
On 2016-07-13 20:15:49 -0400, Thomas Dickey wrote:
> I don't see the behavior which is described, and haven't seen any
> suitable justification for marking this as a "grave" issue, rather
> than "normal". Keep in mind that this is a rarely used line-break
> character.
This is not common, but
On Wed, Jul 13, 2016 at 08:23:34PM +0200, Sven Joachim wrote:
> On 2016-06-22 13:46 +0200, Vincent Lefevre wrote:
>
> > Control: reassign -1 xterm 325-1
>
> This problem seems to stem from the attempt to fix bug #738794, at least
> it is not present in xterm 324 and earlier.
>
> > Control:
On 2016-06-22 13:46 +0200, Vincent Lefevre wrote:
> Control: reassign -1 xterm 325-1
This problem seems to stem from the attempt to fix bug #738794, at least
it is not present in xterm 324 and earlier.
> Control: retitle -1 Character U+2028 can yield file corruption when edited in
> xterm
>
>
Control: reassign -1 xterm 325-1
Control: retitle -1 Character U+2028 can yield file corruption when edited in
xterm
This seems to be an xterm bug since there is no such problem in
urxvt and mlterm, where U+2028 takes its own space. Moreover, I
get exactly the same problem with vi in xterm.
On
9 matches
Mail list logo
