Cloned, installed but linked. Any advice?

➜  Spacemacs git clone https://github.com/syl20bnr/spacemacs ~/.emacs.d
Cloning into '/Users/kasia/.emacs.d'...
remote: Counting objects: 64434, done.
remote: Compressing objects: 100% (47/47), done.
remote: Total 64434 (delta 24), reused 41 (delta 23), pack-reused 64364
Receiving objects: 100% (64434/64434), 37.94 MiB | 3.16 MiB/s, done.
Re

I created this meta issue to track missing documentation. I added [x] even
thought documentation might not be complete. This point is just to make easier
to people to find what module needs documentation, so they can easier contribute
to documentation.

All these are from develop branch.

• completion
  • Company
  • helm
  • ido
  • ivy
• ui
  • deft

Next 1.3.3 has a git-clone (vcs-clone) command. It would be great if, when I press the "fork" Github button, Next suggested me to also clone the repository locally.

What needs to be done: probably installing an event listener on the button. This requires JavaScript knowledge. (we can help a new lisper with the lispy JS). A git-mode mode needs to be created, and the feature be tied to it. Th

Thanks for the active development recently!
Could you please update the inline documents for use-package? It seems outdated.

Evaling the form (throw (ex-info "foo" {})) with M-x cider-pprint-eval-last-sexp-to-comment yields the empty comment string:

;; =>

Arguably it should either:

1. Not yield a ;; => at all (just the empty string) (and appropriate cider error buffer)

or it should:

2. Print the error in the comment.

The later might be useful when describing code interactions and REPL s

Expected behavior

Ignore non-top-level dirs listed in projectile-globally-ignored-directories with both methods of indexing (native and alien).

Actual behavior

Fix introduced in #1119 fixes ignoring of non-top-level dirs for alien indexing mode but not for native.

Steps to reproduce the problem

1. Put this in init.el:

projectile-globally-ignored-directories (append '("*__py

Describe the bug
If there is a syntax error in the file and I call lsp-format-buffer, I do not get visual feedback that the formatting failed.

I can see the error the formatter generated in *lsp-log*.

To Reproduce
Create a syntax error in a file and then call lsp-format-buffer.

Expected behavior
An error should be shown to the user. Most likely in the minibuffer.

Ruby Sass is deprecated. See http://sass.logdown.com/posts/7081811.

According to docstring M-x sp-clone-sexp RET on (| ()) should yield

(  ())
(  ())

because point is two spaces before an sexp, i.e. not immediately before. But the actual behavior results in

(  ()
   ())

as if it were executed on ( |()).

• smartparens version: 20190103.2309
• Active major-mode: lisp-interaction-mode
• Smartparens strict mode: t
• Emacs

https://github.com/Microsoft/language-server-protocol/wiki/Protocol-Implementations

There seems to be a sophisticated OCaml implementation here as well, that already interops with Merlin. Should this be mentioned and/or tested more with Merlin?

In the Issue #161 we have been talking about the org-brain "API", and the need to document the use of the org-brain functions from elisp with the needed arguments, parameters, etc. I want to work with you in what you need related to the more complex linking workflow possible.

All about the issue #163 is a good example of a coding, reference and documentation need for me. How do I

This file structure:

$ ls
mycode.c  other_file.c
$ git init
Initialized empty Git repository in /home/gauthier/tmp/dumb/.git/
$ git add mycode.c && git commit -m"Init"
[master (root-commit) 5271e5a] Init
 1 file changed, 15 insertions(+)
 create mode 100644 mycode.c

mycode.c:

typedef int my_type_t;

my_type_t a;
my_type_t my_function(my_type_t in);
int main(void)