Now both frames are fontified, correctly, with our chosen theme (tango-dark). Hit c to load our theme, and drop to the debugger again. C-x 5 b *Bac to open a frame at the *Backtrace* buffer that's debugging our init.el file. (Black text on white background, red comments, purple strings, etc).

We get an Aquamacs frame with the buffer of source.c fontified in the default emacs theme. Start Aquamacs with something that will get fontified: $ cd ~/Library/Preferences/Aquamacs Emacs/ My fix is to type M-x custom-themes (I can't see 'custom-themes' in the minibuffer because the font color is the same color as the background), and when the buffer with the custom themes opens I uncheck the wombat theme and recheck it (I can't see some of the text in the custom themes buffer either because it is the same color as the background).Īlso, if I want to use a third party custom theme, where should I put the file? My aquamacs preferences file, Preferences.el, is in the directory: The color of the text is actually a few shades darker than the background, which creates a shadow effect: I can see where the white text was, but I can't read it anymore. However, if I quit aquamacs and relaunch it, the text that was white in the wombat theme is now nearly the same color as the background, making the text unreadable. I checked the checkbox for the theme wombat, and then I clicked the Save Theme Settings button in the buffer. The Win32 IsTextUnicode is notoriously bad, it checks only for UTF-16, and is probably the culprit behind the 'bush hid the facts' thing in notepad.When I type M-x custom-themes, I am presented with a buffer listing about 15 custom themes that come with aquamacs. frequency of character pairs and triplets containing non-ASCII characters, or word lists in different languages, but I haven't found any suitable approach trying that. It works OK on a test set but of course misinterpretations are possible, if unlikely.Ĭode Pages could be determined by a statistical analysis of the text (e.g. The only possibility to help in this case is let the user select the code page (from a user experience, the best would be letting the user change the assumed encoding when he sees the text). a file saved with 'eastern european' encoding and loading on a computer with 'western european' default code page will be garbled. This copes with the many BOM-less text files that are out there, but does not help with text stored with custom ANSI code pages.įor these, there's no deterministic detection possible. Check if the text is valid UTF-16 BE/LE.Check if the text is valid UTF-32 BE/LE.

Here's what I do (accepting the first that matches): I've coded that a while ago in C++, and it got pretty complex.

Aquamacs text black