The settungs in the .dir-locals.el do not work well for every emacs setup:
Add .dir-locals.el to the git-ignore list and move content to a template file.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Since commit cac03529 the eslint has been moved from the local nvm to the
developer packages (in `./node_modules`).
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
To get in use of pyright type cheker in Emacs, a pyright installation [1] is
needed and in Emacs the lsp-pyright package has to be installed::
M-x package-install lsp-pyright
[1] https://github.com/Microsoft/pyright
[2] https://github.com/emacs-lsp/lsp-pyright
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
The Node.js installation in the NVM environment can be used by IDEs and other
developer tasks. The required developer packagaes are added to the file
./.nvm_packages and will be installed when Node.js is installed. Initial we
start with:
- eslint
Having a dedicated developer enviroment, provided by nvm makes it easy to
integrate Node.js packages into various IDEs. One example is shown in the
.dir-locals.el which is used by emacs.
[1] https://github.com/nvm-sh/nvm#default-global-packages-from-file-while-installing
[2] https://eslint.org
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
- move jshint option from gruntfile to .jshintrc
- remove trailing-whitespace from gruntfile and
- add jshint esversion: 6
- .dir-locals.el add locals for js-mode to use JSHint from the simple theme
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Open YAML file and use:
M-x flycheck-mode
Since we use yamllint from local/py3/bin, creating a virtualenv is a
prerequisite:
make pyenv
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Installation and use of the command 'virtualenv' was only needed in py2 and py2
is no longer suported by searx. In py3 the command is replaced by 'python -m
venv'.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
The .dir-locals.el set the project's python enviroment for the emacs tasks like
flycheck or jedi. The py-environment has to be next to <repo>/.dir-locals.el::
./local/py3
To setup such an environment build target 'pyenv' or 'pyenvinstall'::
$ make pyenvinstall
TL;DR
Alternatively create the virtualenv, source it and install jedi + epc
(required by `emacs-jedi <https://tkf.github.io/emacs-jedi>`_)::
$ virtualenv --python=python3 "--no-site-packages" ./local/py3
...
$ source ./local/py3/bin/activate
(py3)$ # now install into the activated 'py3' environment ..
(py3)$ pip install jedi epc
...
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
