We get an Aquamacs frame with the buffer of source.c fontified in the default emacs theme. (Black text on white background, red comments, purple strings, etc). C-x 5 b *Bac to open a frame at the *Backtrace* buffer that's debugging our init.el file. Hit c to load our theme, and drop to the debugger again. Now both frames are fontified, correctly, with our chosen theme (tango-dark). In the *Backtrace* frame, hit c again to finish and we eventually get a *scratch* buffer with text color set to black. (Also, the font has been set to Lucida Grande.)Īnd starting the process over again, we get an Aquamacs frame fontified with our chosen theme, but the background is white. Switching to the debugger again and hitting c to continue, we get a *scratch* frame+buffer with our theme, the background is correct, but the default text is black. $ aquamacs -args -no-site-file ~/source.c We get a split Aquamacs frame with source.c in the top window, and the startup screen in the bottom window, both correctly fontified with our chosen theme. So if i'd have to guess, it's something that is getting setup in site-start.el (maybe aquamacs.el?), and getting called after the init file is loaded. You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I think the 4 line init.el in my 2 second post in this issue makes that clear.Īnd what that comes after is causing the font color to be wrong? Well according to, no site-start doesn't do that, unless you've changed that behavior.Īlso, normally, the theme would come after site-start, so it’s not quite clear that this is what’s causing it.Ĭorrect, but as you can see from my previous comment, I did change the order, and something under site-start is violating theming.ĭuring startup, when is the theme applied, If you load site-start, it’ll load and execute everything. This is what I'm trying to find out from you.
0 kommentar(er)
