Eglot's configuration for LSP servers does not have a “false” literal in
Lisp. Furthermore, the previously used `nil` value was being mapped to
JSON's `null` value instead of `false`; making the LSP server to load
defaults for those settings instead of setting those settings to false.
Changed mypy configuration INI format. Python's configparser checks
boolean values in a case-insensitive manner, so it doesn't matter if
values start in Title-case or lower-case. This way, the configuration
is easily translated to TOML format for writing a pyproject.toml file;
with the exception of string values which will have to be enclosed in
quotes anyways.
Similar to a plugin manager, Emacs has Elpa and Melpa repos. Here,
Melpa repository is being added and then some packages (themes and
languages' modes) provided by that repo.
As with previous change, the custom-set-font interface reorders stuff
it's own way. Moving this settings outside that scope makes the
settings stay put.
Emacs customization interface has it's own way to sort settings out.
With this change, the same settings' effects are achieved manually
without having to rely on the internal sorting the customize interface
intends.
Changed mypy configuration file format from INI to TOML. It works all
the same and in this way there are more similarities with the format
inside pyproject.toml file.
The function that added nice text for folded blocks was reverted in
https://github.com/neovim/neovim/pull/27217 in favor of the default text
generated by setting the folding-text option to `""`.
Now, the automatic pop-up that appears when the cursor is idle, appears
en both, Normal and Insert modes; and only displays messages under the
cursor, not the entire line.
For the other behavior, there is still the keybinding `<space>`+`e`.
Added a newly found Pylint message that's duplicated by pycodestyle (via
Flake8).
This message wasn't on the documentation but has a PR and is awaiting
approval.
The purpose of this Makefile and base.mk files are to emulate the
behavior of command `make` when only given a build target (inferring the
source file to use); but using instead a custom set of building flags.
base.mk holds those custom set of building flags, Makefile is just the
wrapper to add get the target name and source file.
In order to achieve the same linting as when compiling a C project, use
those default compilation options for linting inside text editors that
support clangd LSP.