summaryrefslogtreecommitdiff
path: root/.dir-locals.el
AgeCommit message (Collapse)Author
2021-06-05[emacs] flycheck - activate yamllint and use .yamllint.ymlMarkus Heiser
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>
2021-05-17[emacs] don't use tabs, except in makefile-gmake-modeMarkus Heiser
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2020-12-18[mod] remove obsolete virtualenv commandMarkus Heiser
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>
2019-11-29.dir-locals.el: add some comments about jedi & EPCMarkus Heiser
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2019-11-28boilerplate: add .dir-locals.el with emacs python enviromentMarkus Heiser
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>
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion