Description

The documentation for the @spacemacs preconfigured custom layout is inconsistent with actual behavior.

Reproduction guide 🐞

• Start Emacs
• Press SPC l o e

Observed behaviour: 👀 💔
Spacemacs opens a custom layout in the .spacemacs.d directory.

Expected behaviour: ❤️ 😄
Spacemacs opens a custom layout in the `.e

https://github.com/SpaceVim/SpaceVim/blob/master/autoload/SpaceVim/plugins/projectmanager.vim#L199

init.toml

project_rooter_patterns        = ["Pipfile", ".git/"]

for a setup like mine

project/.git
project/whatever/Pipfile
project/whatever/x.py

the root should be project/whatever instead of project.

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)

This should be in docs or at least in the unfinished manual. I keep forgetting how to do that and always go to this issue to relearn. Also for others and future self all the setting names can be found in the config-schema.json file. For example.

when I try to open a pdf file, it go into the Fundamental-mode. I must activate the doc-view-mode manually

Could you make instructions on how to add this to neovim also? I thought just changing things to their respective neovim paths would work, but I got an error trying to do that.

Is it easily just to pull docker container to install it in VPS?
I am not very familiar with VPS or DOCKER so I was defeated to see the installation document.
Could you please make a tutorial video?

If we have no branch and git-link-use-commit is nil we'll get an empty path segment, e.g., path//foo. Under these circumstances we should should signal a "cannot figure out what to link to" error and not return a link.

Just ran into this amazing idea/package, it would be great to have a video tutorial or something, does anyone know anything that kind of help?

Feature request:

Inspect the possibility to utilize ReflectionDocBlock as a backend for looking up API documentation. Then we could have proper docblock documentation in e.g company-quickhelp and similar tools.