On Fri, Mar 29, 2013 at 17:37 (+0100), Andreas Herz wrote:
> On 29/03/13 at 17:30, Raphaël wrote:
>> On Fri, Mar 29, 2013 at 01:16:28PM -0300, Jim Diamond wrote:
>>> Starting with 9.17 (and continuing in 9.18), if you have a line that
>>> starts with a tab character (as opposed to actual spaces) and you
>>> select the first word on the line by double-clicking, the tab is also
>>> selected.
>>> To reproduce (assuming your 'lnext' char is Ctrl-V and that you press
>>> the tab key for <tab>, of course):
>>> <prompt> echo "^V<tab>aaa"
>>> aaa
>>> <prompt>
>>> Now double-click on the "aaa" and note that the selection includes
>>> the tab character.
>>> I'm assuming this is an unintended consequence of the changes for
>>> selection of wide characters, but I guess someone who understands
>>> that part of the code and those changes should make a definitive
>>> comment.
>> I found myself having this issue too, using x11-terms/rxvt-unicode-9.17
>> from Gentoo:
>>> +256-color +blink +buffer-on-clear +fading-colors +focused-urgency
>>> +font-styles +iso14755 +mousewheel +perl +pixbuf +secondary-wheel
>>> +startup-notification +wcwidth +xft
>>> -alt-font-width -unicode3 -vanilla
> Try +vanilla first to make sure it is no gentoo specific patch that
> causes the problem.
> I thinkg +wcwidth might be a candidate. One of the reasons i use
> +vanilla in gentoo, the patches are not that good.
I don't use gentoo.
I compiled the source using Slackware64 14.0 (just like I compiled
versions before and since), but I didn't really think it was relevant,
so I didn't mention it.
Cheers.
Jim
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
