| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
https://github.com/vim/vim/commit/40295c92be643a09d6443121637fa93d6cd105a1
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Normalize the 15 existing guards to the documented two-level form
get(g:, 'X_recommended_style', get(g:, 'filetype_recommended_style', 1)):
fix the two non-standard "!exists() || != 0" guards (python, arduino) and
tolk's wrong fallback variable, and convert the simple one-level guards.
Add the guard to filetype plugins that set stylistic indentation/format
options without one: aap, abap, ada, cabal, cobol, elixir, falcon,
graphql, heex, idris2, mermaid, occam, racket, scala, swift, tera.
Settings that are required rather than stylistic are left untouched, e.g.
make/gomod/scdoc (mandatory tabs), chatito and vroom (indent mandated by
the format), and the textwidth/formatoptions cases in gitcommit/help/
jjdescription.
Supported by AI.
fixes: vim/vim#20036
closes: vim/vim#20650
https://github.com/vim/vim/commit/1f33732613304958c935f302d8cb44bddc7f672f
Co-authored-by: Christian Brabandt <cb@256bit.org>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Effective use of 'formatprg' requires both an understanding of the
specific capabilities of the formatting tool and Vim's formatting
commands. This is overly burdensome for some users.
Rather than address each complaint on a filetype by filetype basis,
remove 'formatprg' settings from all ftplugins.
It is expected that formatter plugins will be available in the near
future as a better solution. See vim/vim#17145 (Add "formatter" feature using
"compiler" as a template).
Note: 'formatprg' will be removed from older ftplugins after the release
of Vim 9.2. The setting was added to the go and gleam ftplugins during
the current development cycle and have not been included in a Vim
release.
See: vim/vim#18650 (rust.vim: stop setting formatprg to rustfmt)
closes: vim/vim#19108
https://github.com/vim/vim/commit/dcc41752843428142623b527433c551991ea7a31
Co-authored-by: Doug Kearns <dougkearns@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
last `unmap` can cause the error "E31: No such mapping" when
`doaudocmd FileType go` if appending other commands to `b:undo_ftplugin` i.e.
the space and the next bar as `let b:undo_ftplugin .= ' | setl ...'`.
closes: vim/vim#17664
https://github.com/vim/vim/commit/f9d87fa6ba4b8026d089bf0fb755f6b0f7296408
Co-authored-by: ichizok <gclient.gaap@gmail.com>
|
| |
|
|
|
|
|
|
| |
closes: vim/vim#17641
https://github.com/vim/vim/commit/5ecee30dcdc1e8c731a69aa04729f07edd57fc27
Co-authored-by: Rob B <github@0x7e.net>
|
| |
|
|
|
|
|
|
|
|
| |
runtime files
closes: vim/vim#17121
https://github.com/vim/vim/commit/fbbaa6ebe92b938f1f9ef008571c330a8d29166a
Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
- The document from `go doc` can be very long, and you can scroll if
using `!` to run shell command in Gvim.
- I realize that I didn't fully mimic behavior of default keywordprg
in Nvim in the last commit.
Solution:
- Use builtin terminal for keywordprg in Gvim
- In Nvim (both TUI and GUI), it should mimic the behavior of Vim
`:term`, `:Man`, and `:help`
closes: vim/vim#16911
https://github.com/vim/vim/commit/11ab02c819449eaeddc3d8d291f06bc73f428e91
Co-authored-by: Phạm Bình An <phambinhanctb2004@gmail.com>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
| |
|
|
|
|
|
|
| |
closes: vim/vim#16804
https://github.com/vim/vim/commit/62e822808e364c84e8abfbc4827bf6012e5b32e0
Co-authored-by: Phạm Bình An <phambinhanctb2004@gmail.com>
|
| |
|
|
|
|
|
|
| |
related: vim/vim#15264
https://github.com/vim/vim/commit/3e07d5aef19ac34a61b9d58c2e0698351d392f52
Co-authored-by: markmacode <code@mamo.aleeas.com>
|
|
|
Updated runtime files.
https://code.google.com/p/vim/source/detail?r=1e8ebf870720e7b671f98f22d653009826304c4f
|
