I've recently upgraded OS X to 10.9 Mavericks, and since this upgrade Emacs has problems with displaying unicode subscript characters (such as ₁, ₂). There are a few strange things about this behaviour:
it doesn't seem to depend on the font, as I've tried selecting several
different Unicode fonts;
it doesn't seem to affect any other unicode character, as I've tried several
uncommon mathematical operators, which display just fine. Even superscripts (¹,²)
are displayed as normal;
it doesn't affect anything outside of Emacs, as the characters are displayed by
my browser just fine.
Does anyone have a clue what could be causing this behaviour?
I just tried this in the version of Emacs you are using, 24.3, and it appears to be broken. However, I also built Emacs from a recent snapshot of the Emacs trunk, which appears to be working correctly.
You can download a prebuilt version from www.emacsforosx.com under Other versions -> Nightlies, alternatively you could wait for the next Emacs release which typically comes out around this time every year.
Related
I recently started using emacs on Android in Termux. My projects feature some chinese characters, which are displayed there just fine.
When later opening the same file in Emacs on Windows, I was disappointed to see them displayed as \xxxx
I am not sure how to search for a solution, because I do not what the problem is.
The only thing I found related to my problem is this:
Unicode characters in emacs term-mode
but it did no help me solve the issue.
You can tell what's going on by looking at the first few characters in the mode line. In Termux, it says UUU, but in Windows it says DDU. These three characters stand for:
the coding system for keyboard input
the coding system for terminal output
the coding system of the file in the buffer
U stands for UTF-8, while D stands for various DOS code pages. (You can find this using M-x list-coding-systems. This is all described in the Mode Line section of the Emacs manual.)
So this means that Emacs is reading the file correctly, but it thinks that the terminal is unable to display the Chinese characters, so it uses the \uxxxx notation as a fallback. I'm not sure how to get this to work properly in a Windows terminal, but try M-x set-terminal-coding-system with utf-8 - it might just work.
As an aside, if you run Emacs as a "normal" Windows application instead of in a terminal, the characters should display correctly automatically, so if there is a particular problem preventing you from doing so, it might be worth trying to fix that instead.
Emacs randomly started doing strange things on my mac -- I'm not sure exactly when it started; it could have been when I updated to Mavericks in the fall. Basically, it randomly doesn't allow me to edit certain lines of text, or it will display files incorrectly (i.e. it deletes some characters).
For example:
I just typed a .txt file containing "hihihi". Upon saving and then reopening the file in emacs, it only displayed "ihihi". This is a simple example...sometimes it deletes whole lines; regardless, this is extraordinarily annoying. However, I do know that it's not actually altering the file, because if I open the same file in Vim it still displays the original content. Emacs is just displaying the files incorrectly.
Has anyone experienced something similar and found a solution?
I've been trying to just install a newer version of emacs, but I think that I'm still running the old version, not the newer version that I installed with homebrew. If anyone has any suggestions for how to fix that I would also appreciate it!
Thanks!
I recently upgraded to emacs 24.3.1 in order to use a new mode for programming in D. I seem to have introduced some problem with my other modes now (Java, C++ C I'm just using whatever comes with emacs). When I scroll up/down in a buffer, the text displayed is totally messed up. As in lines mixed together, indentation screwy, cursor not modifying where it looks like it is. If I hit ctrl-l the screen refreshes and all is good. I noticed this problem every once in a while with my previous version when editing C .h files. But now it's happening on every single buffer. I can't work with it. Every time I move up/down I have to refresh the screen. I can't find anything similar to my problem with a google search. Might end up being an issue with some incompatible version of a dependency. Here's my system stats.
CentOS release 5.4 (Final)
linux 2.6.18-164.el5
emacs 24.3.1
I don't even know what other libs emacs might depend on. I'll be happy to post versions of anything that might be relevant.
Thanks
Since you say that this happens also with emacs -Q, i.e., without your init file, consider filing a bug report: M-x report-emacs-bug. For that, try to give a short, reprocible recipe, starting with emacs -Q. Emacs Dev will take a look and let you know whether they think there is a bug.
Using report-emacs-bug also automatically gathers info about your Emacs version etc., and includes it with your bug description.
I upgraded my emacs recently to 24.2 cocoa using homebrew, and now org-mode is pretty much useless in the terminal. The problem is more irritating than it would be if it didn't work at all, which would give me a clue as to how to fix it.
When I'm editing a list (using the asterisk), and contract or expand the elements of the list (using tab), all kinds of weirdness occurs. Some list items will suddenly duplicate. Some list items will disappear completely. Items will be pushed way down the page, and then jump back up. This is all happening as I'm pushing nothing but tab.
I've uninstalled, reinstalled emacs using brew. I've done a lot of googling but can't find anyone who has had this problem with org-mode. Anyone have any ideas?
Mac OS X Lion 10.7.5
Emacs 24.2
org-version 7.8.11
Have you tried using a different terminal emulator? They all have different bugs, so perhaps you've tripped over one in the default Terminal app. Try a plain xterm instead. I assume that emacs works fine when it's not in a terminal.
I'm using emacs 24 on OS X and have the strange problem that I'm unable to see any color codes. Emacs seems to just ignore them. My motivation is to see colored output from cmake, llvm and the googletest framework for a C++ project. I'd like to see the colors in compile mode, however it would probably suffice to fix the display for comint or shell modes.
My problem differs from many others in the fact that I can neither see the raw ansi color sequences nor the colors they should produce. It seems that the codes are just stripped away from the output, but I can't find out where.
I tried out the obvious things like
requiring 'ansi-color
turning ansi-color-for-comint-mode on
unsuccessfully trying to produce any ansi-colored output in either shell, eshell, multi-term, ansi-term
setting my TERM to various settings, including xterm, xterm-color, xterm-256color
all to no avail.
Edit:
My emacs configuration is divided into my personal settings and a fork of emacs prelude in which I modified some minor settings, mainly adding packages
So it turned out that the problem was caused by zenburn-theme 1.2. There was a bug there with the ansi-color-names-vector that's fixed in version 1.3 (released just now). If you're experiencing a similar problem make sure you upgrade your version of zenburn.
I can definitely say it's working fine for me with just (ansi-color-for-comint-mode-on). FWIW you can browse my emacs config, but it's fairly big :)
https://github.com/aufflick/emacs.d