-
Updated
Dec 10, 2020 - Emacs Lisp
Emacs

Emacs is an extensible text editor written primarily in Emacs Lisp. While it excels at editing text, Emacs stretches the boundaries of what 'text' is.
Here are 4,060 public repositories matching this topic...
-
Updated
Nov 13, 2020
-
Updated
Dec 10, 2020 - Common Lisp
I am running Emacs with the -nw
flag from the terminal.
When looking at the commit graph using log all-branches (keymap l b
) I cannot differentiate which is the currently checked-out branch, as they all look the same.
In contrast, when using Emacs GUI the current branch is highlighted/boxed, which makes it highly visible.
I would expect the font-faces to be different in the terminal i
Maybe it's a dump question, but seems flycheck report all the prelude-
symbols for this error, is there a way to avoid this error being reported?
DEFUN ("make-frame-visible", Fmake_frame_visible, Smake_frame_visible,
0, 1, "",
doc: /* Make the frame FRAME visible (assuming it is an X window).
If omitted, FRAME defaults to the currently selected frame. */)
(Lisp_Object frame)
{
struct frame *f = decode_live_frame (frame);
/* I think this should be done with a hook. */
#ifdef HAVE_WINDOW_SYSTEM
if (FRA
-
Updated
Nov 24, 2020 - Go
-
Updated
Nov 29, 2020 - Emacs Lisp
Expected behavior
That projectile-find-file
works.
Actual behavior
I get an error. It seems like formatting of the final command to call has a bug with it on Windows:
Debugger entered--Lisp error: (file-missing "Setting current directory" #("No such file or directory" 0 25 (charset windows-1252)) "c:/Users/REDACTED/Git/REDACTED/'echo: -c: line 0: unexpe...")
call-process("C:
Expected behavior
Evaluating just a single line in a Rich comment block will apply a green fringe to only the line being evaluated.
Actual behavior
Evaluating just a single line in a Rich comment block will apply a green fringe to the line being evaluated as well as the following line.
Steps to reproduce the problem
- add the following comment block to a file:
(comment
(+ 1
-
Updated
Dec 10, 2020 - Emacs Lisp
-
Updated
Dec 10, 2020 - Emacs Lisp
-
Updated
Dec 10, 2020 - Shell
-
Updated
Nov 26, 2019 - Emacs Lisp
-
Updated
Dec 9, 2020 - Emacs Lisp
-
Updated
Dec 3, 2020 - CSS
Recent emacs 25.3, most recent auto-complete in melpa. Adding ac-source-semantic but it still doesn't work:
My semantic settings should be correct as company with that works fine:
 you use the most. Particularly:lang
modules, so that I can get a test environment up and running to test ag