(
Jump to the original submission)
Sun 06 Jul 2008 10:14:28 AM UTC, comment #6:
Fixed for version 0.2.7, testers are welcome (see my previous comment to test it).
|
Tue 01 Jul 2008 08:24:16 AM UTC, comment #5:
I'm currently fixing that!
And you can test it if you want, in devel version ("protocols" branch in git repository).
To test it, you have to do that:
1. comment these 3 lines in src/gui/curses/gui-curses-input.c, line 363-365, like that:
//if (ptr_win == gui_current_window)
// move (ptr_win->win_input_y,
// ptr_win->win_input_x + ptr_win->win_input_cursor_x);
2. run weechat, and create default bars with /bar default
You should have 2 input lines (one is old input (without cursor)), and other is new input as bar (with cursor in line). This bar can be tested with wide chars. I've rewritten all code for input, so you can test (I didn't test if this bug is fixed by this new version).
Other solution is to wait that I remove old input, to keep only input bar.
|
Tue 01 Jul 2008 08:07:29 AM UTC, comment #4:
Ok, I expect for the fix too, so much!
But anyway, author has done a well job, thank you!
|
Tue 01 Jul 2008 08:02:03 AM UTC, comment #3:
hi,
seemes this bug still in progress, may I ask that when will it be fixed ?
|
Tue 09 May 2006 10:43:07 AM UTC, comment #2:
Now there is problem with input line when scrolling (length > window width) if there is wide chars.
|
Mon 08 May 2006 01:28:17 PM UTC, comment #1:
Problem was only with chars that are more than one character cell wide on screen.
Fixed for input and display in buffer chat area.
|
Mon 17 Apr 2006 06:26:25 PM UTC, original submission:
UTF-8 chars coded on more than 2 bytes are not properly displayed by WeeChat
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Follow 7 latest changes.