The C-c C-s binding mirrors the export and writable export bindings.
embark-export is used for type specific exports (such as buffers to an
ibuffer buffer), not for verbatim exports. This is most noticeable if
you want to export a variable list, which gets you to an apropos buffer.
if you just want a list of things to keep around,
embark-collect-snapshot is the tool for the job, but having it be only
on C-; S makes it harder to reach and less visible. C-c C-s is a nice
visible thing to have around.
BREAKING CHANGE: This commit changes the behaviour of the TAB and RET
keys in a consult-completing read multiple session, in order to make
them more intuitive. The behaviour is now:
- TAB: (unchanged) always select or deselect the current candidate, and
if the candidate is selected, move the index to the next one (this
allows for pressing TAB repeatedly to select multiple subsequent
candidates).
- RET: If no candidates have been selected, select the current candidate
and exit the completion session. If some have been selected, disregard
the current candidate and exit.
- S-TAB: (new) like TAB, but the keeps the input.
lsp-mode doesn't detect the correct indentation, since it treats the
derived tsx-mode as a web-mode. This change modifies the lsp-mode
internal alist to recognize tsx-mode correctly. Ideally lsp-mode would
have a better way to modify its known mode lists but I couldn't see it.
Ref: emacs-lsp/lsp-mode#3308
- Add @angular/core in detecting angular to set the web-angularjs minor
mode
- At the same time set the web-mode-engine to "angular" so that
`format-all` uses prettier to format ionic `*.page.html` files in
addition to `*.component.html` files.
When `format-all` sees the web-mode-engine is set to "angular", it
applies `prettier` as opposed to `html-tidy`, as `tidy` doesn't
recognise angular component tags and hence errors out. The current
web-mode only sets the engine to "angular" for "*.components.html".
However, ionic angular uses file names such as "*.page.html", setting
engine will apply prettier to these html fils.
set-{eval,repl}-handler! operate on major modes, not minor modes (this
should be corrected upstream, but I'll do so later). This doesn't apply
to set-lookup-handlers!, but I'm changing it too for consistency.
BREAKING CHANGE: Remove `company-erlang` which depends on
`ivy-erlang-complete`. `company-erlang` and `ivy-erlang-complte` have
not been maintained now. The lsp mode provides much better experience
than `company-erlang` and `ivy-erlang-complete`. The
`ivy-erlang-complete` package also has the defect that slow down the
erlang-mode buffer when the buffer is huge enough. It is not a good
choice to integrate ivy-erlang-complete nowadays even as a non-LSP
option.
code-review is built on magit-sections so it will have the same default
bindings for M-1, M-2 etc. To be consistent with the rest of doom, those
should be used for switching workspace and z1, z2 etc should be used for
toggling outlines in a magit-sections buffer.
This only affects users with :editor (evil +everywhere) enabled.
Amend: 2d3a68df49
In org-mode, if one writes a math expression in a section (i.e. heading)
while using cdlatex, pressing tab indents the section instead of
performing a cdlatex-tab.
This fix takes care of this issue to have the wanted behavior: if in
math environment and hit tab while in section, execute cdlatex-tab.
Close: #5926
Co-authored-by: roiholtzman <roiholtzman@users.noreply.github.com>
Did I already mention that this `latex-mode` slash `LaTeX-mode`
ambiguity was a reeeeeeally bad decision upstream? Anyways, this very
small PR also loads `writegood-mode` with AucTeX, which uses
`LaTeX-mode`, and not `latex-mode`.
These files were put directly in .emacs.d causing the repository to
appear dirty. This should follow the doom convention of putting the
files in the .local/etc dir.
Amend: 2d3a68df49
* feat(fortran): account for f90 and fortran modes
* feat(fortran): initial keybindings
* feat(fortran): basic compilation
* feat(fortran): compilation popup
This customizes the name of the compilation buffer produced by the
`compile` function. We're keeping things simple; Emacs already knows how
to run compilation commands in a popup and parse the results, so let's
let it do its thing.
* feat(fortran): doctor checks
* docs(fortran): installation instructions
* feat(fortran): actual usage of fpm
* feat(fortran): configure compilation popups
* feat(fortran): improved raw gfortran usage
Although it's recommended to do everything through `fpm` to make life
easier.
* docs(fortran): backburner `+intel` for now
* feat(fortran): address PR suggestions
