The Wayback Machine - https://web.archive.org/web/20201211070700/https://github.com/topics/emacs
Skip to content
#

Emacs

emacs logo

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...

doom-emacs
hlissner
hlissner commented Feb 18, 2020

As Doom continues to grow, so have incoming bug reports for modules I do not use and toolchains I know little about, like :lang clojure or :tools ein, and so I struggle to support them.

If you know a little nix and use Doom, consider contributing a shell.nix file to the module(s) you use the most. Particularly :lang modules, so that I can get a test environment up and running to test ag

dadinn
dadinn commented Sep 3, 2020

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

brotzeit
brotzeit commented May 8, 2019
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
sonictk
sonictk commented Nov 17, 2020

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:
dareno
dareno commented Dec 4, 2020

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

  1. add the following comment block to a file:
(comment
  (+ 1
You can’t perform that action at this time.