summary refs log tree commit diff
path: root/home/.config/nvim (follow)
Commit message (Collapse)AuthorAge
* Add \d to replace .Dd macroJune McEnroe2020-01-25
|
* Add \S to sort inside bracesJune McEnroe2019-12-26
|
* Add GPL header templateJune McEnroe2019-11-06
|
* Mark ' for \aJune McEnroe2019-10-28
|
* Set the write variable for nvim man modeJune McEnroe2019-10-14
| | | | Embarrassing...
* Update neovim 0.4.2June McEnroe2019-10-02
| | | | | Finally a release with my man mode fix... Meanwhile neovim itself has probably gotten worse.
* Clean up home filesJune McEnroe2019-07-27
|
* Color python imports as StatementJune McEnroe2019-04-15
|
* Set man_hard_wrap in nvimJune McEnroe2019-02-20
| | | | | Vendoring man.vim until <https://github.com/neovim/neovim/pull/9633> is merged and appears in a release.
* Color format specifiers light cyan in vimJune McEnroe2019-02-15
|
* Add nmap gpJune McEnroe2019-02-15
|
* Use italic for underline in nvim man modeJune McEnroe2019-02-10
| | | | | This doesn't yet work in Terminal.app: <https://github.com/neovim/neovim/issues/9598>.
* Don't open folds when using {}June McEnroe2019-02-08
|
* Import autoload/man.vim from 71bb4fdJune McEnroe2019-02-07
| | | | | | | | This is the version of man.vim prior to <https://github.com/neovim/neovim/pull/9023>. I opened an issue for the degraded experience <https://github.com/neovim/neovim/issues/9583>.
* Set nvim Directory back to blueJune McEnroe2019-02-01
| | | | | nvim is going bad I tell ya. Man mode seems broken in the new version too.
* Set nvim UI colors back to the 8-color paletteJune McEnroe2019-01-25
| | | | | Neovim seems intent on replacing all the default colors with ghastly choices from the 256-color palette.
* Remove \h bindingJune McEnroe2018-12-02
|
* Set default .asm, .h, .sh syntax modes for vimJune McEnroe2018-11-23
|
* Disable number, laststatus, ruler in vimJune McEnroe2018-11-23
|
* Add \l binding to insert AGPL commentJune McEnroe2018-11-14
|
* Add \s sort binding and simplify \h and \aJune McEnroe2018-11-11
|
* Add mdoc syntax fileJune McEnroe2018-09-10
|
* Remove colorcolumn at 100June McEnroe2018-09-02
|
* Add vim mapping to add a #includeJune McEnroe2018-08-17
| | | | | Unfortunately as far as I know I can't have it automatically sort them after I hit escape.
* Ignore .o files in vimJune McEnroe2018-08-09
|
* Fix colorscheme manUnderline disableJune McEnroe2018-08-06
| | | | | Otherwise manUnderline counts as "cleared" so the default in man.vim takes over again.
* Disable underline in man pagesJune McEnroe2018-08-06
|
* Use 16-color palette in colorschemeJune McEnroe2018-08-06
| | | | | neovim 0.3.0 just doesn't give a shit anymore about how many colors your terminal supports.
* Use color numbers in colorschemeJune McEnroe2018-07-30
| | | | | Neovim is really dumb about how it interprets the names, and at this point I actually know the order the colors are in.
* I've really done it nowJune McEnroe2018-05-13
| | | | Time to see what it's like to be a hard-tab person.
* Highlight Special as NormalJune McEnroe2018-04-02
| | | | Special characters in strings are more like normal code than keywords.
* Set g:clipboard to pb{copy,paste} alwaysJune McEnroe2018-03-30
| | | | | Previously neovim would use these automatically if it found them, but now it only checks for them on macOS. pbd continues to work well.
* Sort extern crate lines with \cJune McEnroe2018-03-28
|
* Add \u to sort use linesJune McEnroe2018-03-24
|
* Only sort system includes with \hJune McEnroe2018-03-06
|
* Only list first space of tabsJune McEnroe2018-02-12
|
* Set cinoptionsJune McEnroe2018-02-04
|
* Tweak colorscheme moreJune McEnroe2018-02-04
|
* Color MatchParen DarkYellowJune McEnroe2018-02-04
| | | | White is not obvious enough.
* Map \h to sort includesJune McEnroe2018-01-31
|
* Remove Tarmak remappings from vimJune McEnroe2018-01-29
|
* Set t_Co = 8June McEnroe2018-01-29
| | | | | Weirdly with t_Co = 16 yellow and bright white weren't showing up on TERM=linux.
* Add :Q command aliasJune McEnroe2018-01-29
| | | | It seemes I can't take my finger off the shift key fast enough.
* Set nonumber in terminalsJune McEnroe2017-12-31
|
* Use 4-space indent everywhereJune McEnroe2017-09-15
|
* Rename curtis -> homeJune McEnroe2017-09-06
Why the heck did I do this?
generated by cgit-pink 1.4.1 (git 2.36.1) at 2025-01-12 07:56:11 +0000
2b730b034eebd0e9da4aa014785a3ee5de436be&follow=1'>builtin: Fix echo performance regressionHerbert Xu The commit d6c0e1e2ffbf7913ab69d51cc794d48d41c8fcb1 ("[BUILTIN] Handle embedded NULs correctly in printf") caused a performance regression in the echo built-in because every echo call now goes through the printf %b slow path where the string is always printed twice to ensure the space padding is correct in the presence of NUL characters. In fact this regression applies to printf %b as well. This is easily fixed by making printf %b take the fast path when no precision/field width modifiers are present. This patch also changes the second strchurnul call to strspn which generates slightly better code. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix ghost fields with unquoted $@/$*Herbert Xu Harald van Dijk <harald@gigawatt.nl> wrote: > On 22/03/2018 22:38, Martijn Dekker wrote: >> Op 22-03-18 om 20:28 schreef Harald van Dijk: >>> On 22/03/2018 03:40, Martijn Dekker wrote: >>>> This patch fixes the bug that, given no positional parameters, unquoted >>>> $@ and $* incorrectly generate one empty field (they should generate no >>>> fields). Apparently that was a side effect of the above. >>> >>> This seems weird though. If you want to remove the recording of empty >>> regions because they are pointless, then how does removing them fix a >>> bug? Doesn't this show that empty regions do have an effect? Perhaps >>> they're not supposed to have any effect, perhaps it's a specific >>> combination of empty regions and something else that triggers some bug, >>> and perhaps that combination can no longer occur with your patch. >> >> The latter is my guess, but I haven't had time to investigate it. > > Looking into it again: > > When IFS is set to an empty string, sepc is set to '\0' in varvalue(). > This then causes *quotedp to be set to true, meaning evalvar()'s quoted > variable is turned on. quoted is then passed to recordregion() as the > nulonly parameter. > > ifsp->nulonly has a bigger effect than merely selecting whether to use > $IFS or whether to only split on null bytes: in ifsbreakup(), nulonly > also causes string termination to be suppressed. That's correct: that > special treatment is required to preserve empty fields in "$@" > expansion. But it should *only* be used when $@ is quoted: ifsbreakup() > takes nulonly from the last IFS region, even if it's empty, so having an > additional zero-length region with nulonly enabled causes confusion. > > Passing quoted by value to varvalue() and not attempting to modify it > should therefore, and in my quick testing does, also work to fix the > original $@ bug. You're right. The proper fix to this is to ensure that nulonly is not set in varvalue for $*. It should only be set for $@ when it's inside double quotes. In fact there is another bug while we're playing with $@/$*. When IFS is set to a non-whitespace character such as :, $* outside quotes won't remove empty fields as it should. This patch fixes both problems. Reported-by: Martijn Dekker <martijn@inlv.org> Suggested-by: Harald van Dijk <harald@gigawatt.nl> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02parser: Allow newlines within parameter substitutionHerbert Xu On Fri, Mar 16, 2018 at 11:27:22AM +0800, Herbert Xu wrote: > On Thu, Mar 15, 2018 at 10:49:15PM +0100, Harald van Dijk wrote: > > > > Okay, it can be trivially modified to something that does work in other > > shells (even if it were actually executed), but gets rejected at parse time > > by dash: > > > > if false; then > > : ${$+ > > } > > fi > > That's just a bug in dash's parser with ${} in general, because > it bombs out without the if clause too: > > : ${$+ > } This patch fixes the parsing of newlines with parameter substitution. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix bugs with words connected to the right of $@Herbert Xu On Sun, Mar 04, 2018 at 12:44:59PM +0100, Harald van Dijk wrote: > > command: set -- a ""; space=" "; printf "<%s>" "$@"$space > bash: <a><> > dash 0.5.8: <a>< > > dash 0.5.9.1: <a>< > > dash patched: <a><> This is actually composed of two bugs. First of all our tracking of quotemark is wrong so anything after "$@" becomes quoted. Once we fix that then the problem is that the first space character after "$@" is not recognised as an IFS. This patch fixes both. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-25Revert "[BUILTIN] Remove unnecessary restoration of format string in printf"Herbert Xu This reverts commit 7bb413255368e94395237d789f522891093c5774. The commit breaks printf with more than argument. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-22parser: Fix backquote support in here-document EOF markHerbert Xu