| Age | Commit message (Collapse) | Author | Lines |
|---|
|
apparently you can just do this
|
|
|
|
|
|
|
|
|
|
no more configs
I didn't check opts/deps/etc, since I don't use neovim nearly as much
nowadays, so I should check it again eventually.
|
|
It's actually relevant there. This section might get more entries over time.
|
|
I forgor to this when I switched to indent_size=tab for consistency.
|
|
This is a funny one. In emacs' editorconfig.el, you can see the
following comment: "When users choose `indent_size=tab`, they most
likely prefer `indent_style=tab` as well.
Ths directly follows a workaround an issue of excessively setting
tab-width even when it's not explicitly requested.
This means that the behavior of editorconfig.el is as follows:
* If tab_width is set, the value is used.
* Else, if indent_style is set to "tab", indent_size is used for
tab_width.
What I would like is to keep my tab_width and (non-existent)
space_width in sync, and then have (by default) the default
per-filetype indentation style, with the ability to override
them.
This means unsetting indent_style (as it was before), and then setting
indent_size to the common width, which is the editorconfig preferred
approach. Because of the abovementioned bug workaround, since
indent_style is unset (i.e. is not "tab"), indent_size is not used for
tab_width.
Up until now, the way I've been working around this is by setting
indent_size to tab and then using tab_width to control the de-facto
indent_size (reversing the logic). This has the additional bonus of
being more explicit, and keeping mixed tab/space indentations
internally consistent. The problem then is that the indent_size=tab is
treated as a hint to set indent_style=tab globally, removing my
ability to use the filetype default.
I can either patch the code in question, or I can just accept that my
global preference (as a default, other things not considered) is for
spaces (though I do appreciate tabs in specific circumstances). This
line applies this : spaces are now a global default, and I can set a
tab style where appropriate, including in projects.
|
|
|
|
|
|
It actually yells at you every time you save if you don't have it :D
|
|
|
|
|
|
it just feels like it should be here, not there
|
|
Basically the various forms for the multiple utility checks were
annoying me. This is nicer, even if the =$cmd looks a bit jank.
|
|
:(
|
|
|
|
|
|
|
|
|
|
|
|
Otherwise, failure to find xsource() files causes a return of 1 at the
end of zlogin (or similar).
The entire point of xsource is to "safely" source files that may not
be there, so this seems reasonable.
|
|
|
|
Yeah so emacs isn't thaat good at detecting shell scripts either.
|
|
aka the prompt to rule them all
|
|
|
|
In zsh, an EXIT trap defined in a function runs on that function's
execution end. Unfortunately, that's not what I want! Instead, there's
the zsh hook zshexit, but that takes a function.
This changes tt to add the generated directories to a deduplicated
array, which is cleaned up on exit, as long as the function has been loaded.
|
|
|
|
|
|
|
|
I'm just going to stick everything in here from now on.
|
|
fpath isn't exported, so it can't get "inherited" by non-login shells
this could technically also be in zshrc though...
|
|
|
|
don't... worry about it
I spent basically all day between this and monster hunter.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
can't believe I have to do this but...
in short, a bunch of programs check for whether XDG_* is set
in order to activate their XDG compliance
so even if you want the defaults, you're better off setting them...
|
|
|
|
Bunch of stuff bundled with it.
`lsp/` subject to changes.
|
|
It's finally here!
|
|
https://blog.gitbutler.com/how-git-core-devs-configure-git/
reminded me to make sure everything's up to date
I knew my column.ui wasn't working but didn't take the time to find why
yet, so that's nice
still wondering about the fsmonitor stuff though, I might turn them off
and just turn them on per-repo; indeed would be nice if clone asked for
it
|
|
|
|
|
Chloé Vulquin