Dear Maintainer, I use emacs for editing all my text files, it is awesome. However when editing files with Korean in them it suddenly becomes extremely laggy and top shows a very high CPU usage. This occurs as son as I have opened the file, even before I have started hangul mode to type Korean. An example Korean file that gives this problem is here: http://www.kitamura-studios.com/ko-index.shtml I don't get this problem editing Chinese files. I am working around this problem by using libreoffice to edit files that contain Korean at the moment.
kie <bugs@hotsite.to> writes: Can you explain how I might reproduce this? Here's what I tried: $ wget 'http://www.kitamura-studios.com/ko-index.shtml' $ emacs23 -Q ko-index.shtml and I didn't see any excessive CPU usage. I also tried launching Emacs like this: $ LANG=en_HK.UTF-8 LC_CTYPE=en_HK.UTF-8 emacs23 -Q ko-index.shtml ...which behaved reasonably too. Though I should note that the system involved is a mixture of wheezy, unstable, and experimental. Thanks
Hi Rob, I tried doing exactly the same (so without using my .emacs file). By just pressing the arrow key to scroll either left or right or up and down I was at random times getting 100% CPU usage, although the recovery was a lot quicker than the very long hangs I was getting with my previous usage (which uses my .emacs file). I have posted a screenshot with emacs and top showing CPU usage. http://www.kitamura-studios.com/pix/emacs_korean_700808.jpg Just to note that I only get this hang with editing files with Korean text. My system is all 'testing' apart from darktable which is from 'unstable'. Hope this helps, please let me know if there is any other information that I can provide. best rgds Kie On Fri, Mar 01, 2013 at 08:24:27PM -0600, Rob Browning (rlb@defaultvalue.org) wrote...
This was 8 years and 4 Emacs major releases ago. If this is still an issue with Emacs 27.1, I suggest opening a new report with upstream directly.
This was 8 years and 4 Emacs major releases ago. If this is still an issue with Emacs 27.1, I suggest opening a new report with upstream directly.