I think the error comes from list-colors-print, which seems to have a nil at the end, and that gives you the error you see. This doesn't seem to happen in earlier versions of emacs and is probably a bug.
Assuming that the org- libraries have already been loaded ...
Type: M-x customize-face RET org-ellipsis RET
To see a list of all faces for the org- library, type: M-x customize-group RET org-faces RET
If the org- libraries have not yet been loaded, then evaluate (require 'org) using something like M-x eval-expression aka M-: before querying a particular ...
For exa in eshell you can just use the following alias. It is preserved over a restart of Emacs.
alias exa *exa --color=always
The general problem to teach other programs about the color capabilities of the comint of Emacs is described on Rededit.
This approach helps for an example colorizing git output under Eshell.
Create a file ~/....
You didn't specify which platform you're on, but under X11 you can do something like
(setq x-gtk-use-system-tooltips nil)
(setf (alist-get 'alpha tooltip-frame-parameters) 0.5)
The first line is needed because otherwise emacs will use GTK tooltips, which don't respect the tooltip frame parameters. There does seem to be some support in GTK for changing the ...
If you just want to put *scratch* in its own frame and use special frame parameters for it (e.g. give it its own background color, font, or whatever) then you can do this just by doing these two things:
Customize special-display-alist to have the frame parameters you want.
Customize special-display-buffer-names, adding *scratch* to it.
In a comment you ...
(Variable color-themes is a list of your color themes. A given color theme is a function.)
You can use command color-theme-analyze-defun to check whether a function definition (defun) at point defines a color theme. It's defined in color-theme.el.
Here is its doc string:
Once you have a color-theme printed, check for missing faces.
This is used by ...
The default color theme (in Emacs-speak they're themes) isn't defined in a single place, but you can collect everything into one file by creating your own custom theme.
start Emacs with emacs -Q to disable user and site-local configuration
do M-x customize-create-theme RET y to create a customize buffer that includes basic faces.
At the top of the buffer ...
What do you mean by "colorscheme", and more particularly, what do you mean by "the hex values of the default colorscheme"?
If you're asking about particular colors that you see, where do you see the colors you're interested in?
If they are for buffer text, put your cursor on some text with a particular color and do C-u C-x =. Buffer *Help* will tell you ...
Have you tried xterm-color ?
You can use the config below if you use use-package
(remove 'ansi-color-process-output comint-output-filter-functions))
(lambda () (add-hook 'comint-preoutput-filter-functions
You could use an external package like https://github.com/vic/color-theme-buffer-local to accomplish this.
:defer 2 ; You may not need this line, but was needed in my setup
(load-theme-buffer-local 'misterioso (get-buffer "*scratch*")))
If you kill the scratch buffer and created a new one, the theme will ...
You can't make a frame background transparent by changing the background color. The alpha frame parameter is a separate parameter from background-color.
Function x-show-tip accepts an alist of tooltip frame parameters as argument. If you are the caller of x-show-tip then you can add an alpha parameter and its value to the alist that you pass to x-show-tip....
Customize option tooltip-frame-parameters, specifying an alpha parameter value that is less than 100.
See the Elisp manual, node Font and Color Parameters, for information about parameter alpha. There, you see this:
This parameter specifies the opacity of the frame, on graphical
displays that support variable opacity. It should be an integer
The requirement was for a different background color for each remote host logged into. This snippet is now at the end of the shared .emacs on each host:
("adam" . "seashell")
("eve" . "lavender blush")
("lucifer" . "lavender")
("cherub" . "linen")
("moly" . "alice blue")
("athame" . "mint cream")
("aziraphael" . "alice blue")
Line faces are defined in mu4e~headers-line-handler-functions. To change the face conditionally you can set your preferences in mu4e-mailing-list-colors and try the following code (based on the mu4e~headers-line-apply-flag-face function):
'(("emacs-devel.gnu.org" . "green")
("emacs-orgmode.gnu.org" . "blue")))
Expanding on @amitp's answer above, here's what I did in my .zshenv file to set my $EDITOR env variable:
if [[ -v INSIDE_EMACS ]]; then
# Regular shell
export EDITOR="emacsclient -t"
I do something like this, but for my tabbar and mode line (screenshots). I use red for some projects and blue for some projects.
I don't know of an existing module that does this. Here's an adaptation of what I use, but to match your question.
(defun my/set-local-colors ()
"Set colors based on current directory"
((string-match "/client_foo/" ...