Re: [O] Bug: Pressing TAB in table cell with CJK characters sometimes destroys proper column alignment [8.2.10 (8.2.10-dist @ /usr/share/emacs24/site-lisp/org-mode/)]
Is there a task defined for this work? I am interested in this too. Grant Rettke -- g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Mon, Apr 6, 2015 at 9:18 PM, Eric Abrahamsen e...@ericabrahamsen.net wrote: Eugen Dueck eu...@tworks.co.jp writes: In a simple org-table like the following: | | | | 漢 | | when pressing the TAB key in the bottom left cell, one space character is removed from that cell and the table thus looks like | | | | 漢 | | Pressing TAB again in that cell removes another space character | | | | 漢 | | I can repeat this until only one space remains between the Japanese character and the column separator to its right. When working on a table, navigating via TAB, over time all the CJK cells that I TABbed out of - or Shift-TABbed out of - get affected, messing up the overall table layout. Once I press C-c C-c, the formatting of the whole table gets restored, until my next TAB, but it would of course be nice if TABs didn't destroy it in the first place. Btw, org-table rocks and I use it all the time - and I hope to be able to use it with Japanese characters as well. A while ago I spent some time making this work as well as possible for double-width glyphs, but I also noticed that sometime recently it's gone back to the old behavior. I can look into it again, but work is encroaching and it might take me a little time...
[O] Bug: Pressing TAB in table cell with CJK characters sometimes destroys proper column alignment [8.2.10 (8.2.10-dist @ /usr/share/emacs24/site-lisp/org-mode/)]
In a simple org-table like the following: | | | | 漢 | | when pressing the TAB key in the bottom left cell, one space character is removed from that cell and the table thus looks like | | | | 漢 | | Pressing TAB again in that cell removes another space character | | | | 漢 | | I can repeat this until only one space remains between the Japanese character and the column separator to its right. When working on a table, navigating via TAB, over time all the CJK cells that I TABbed out of - or Shift-TABbed out of - get affected, messing up the overall table layout. Once I press C-c C-c, the formatting of the whole table gets restored, until my next TAB, but it would of course be nice if TABs didn't destroy it in the first place. Btw, org-table rocks and I use it all the time - and I hope to be able to use it with Japanese characters as well. Emacs : GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 2014-12-10 on gaia, modified by Debian Package: Org-mode version 8.2.10 (8.2.10-dist @ /usr/share/emacs24/site-lisp/org-mode/)
Re: [O] Bug: Pressing TAB in table cell with CJK characters sometimes destroys proper column alignment [8.2.10 (8.2.10-dist @ /usr/share/emacs24/site-lisp/org-mode/)]
Eugen Dueck eu...@tworks.co.jp writes: In a simple org-table like the following: | | | | 漢 | | when pressing the TAB key in the bottom left cell, one space character is removed from that cell and the table thus looks like | | | | 漢 | | Pressing TAB again in that cell removes another space character | | | | 漢 | | I can repeat this until only one space remains between the Japanese character and the column separator to its right. When working on a table, navigating via TAB, over time all the CJK cells that I TABbed out of - or Shift-TABbed out of - get affected, messing up the overall table layout. Once I press C-c C-c, the formatting of the whole table gets restored, until my next TAB, but it would of course be nice if TABs didn't destroy it in the first place. Btw, org-table rocks and I use it all the time - and I hope to be able to use it with Japanese characters as well. A while ago I spent some time making this work as well as possible for double-width glyphs, but I also noticed that sometime recently it's gone back to the old behavior. I can look into it again, but work is encroaching and it might take me a little time...
