| Age | Commit message (Collapse) | Author | Files |
|---|
|
commits (#37192)
This reverts commits:
- 6b652a785033fd4164e049492a7327c1ed7c3e5f
- 2f689d5abde0ccddca9e20d8c93a0299bd054e32
- a025a46d4169587145fb54f04af349cd05cb6122
Several email addresses that are known to be valid caused bounces
due to an issue with my email setup. The previous commits incorrectly
marked these addresses as invalid. So revert the whole thing again.
https://github.com/vim/vim/commit/62d8f3dab5a0b30c31a8df86a973c5e59821a3f0
N/A patch:
vim-patch:2f689d5: runtime: mark more invalid email addresses
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
https://github.com/vim/vim/commit/2f689d5abde0ccddca9e20d8c93a0299bd054e32
Skip colors/ and syntax/help_ru.vim: missing previous changes.
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
style (#36875)
The help text here said 99 was the recommended style for the standard
library, but I can't find a citation for this anywhere. In contrast the
Rust Style Guide hosted on rust-lang.org
[says](https://doc.rust-lang.org/stable/style-guide/#indentation-and-line-width)
the maximum line width is 100, and rustfmt
[agrees](https://github.com/rust-lang/rust/blob/37aa2135b5d0936bd13aa699d941aaa94fbaa645/src/tools/rustfmt/src/config/options.rs#L570).
Having the two disagree causes an annoying off-by-one error in vim: if
you configure vim to highlight too-long lines then it will occasionally
complain about a line that rustfmt refuses to fix.
closes: vim/vim#18892
https://github.com/vim/vim/commit/98ef8433b654ee96c57b66348b767edc73a44406
Co-authored-by: Aaron Jacobs <jacobsa@google.com>
|
|
default (#36361)
This reverts commit 4ac995bf9366c6624a0724d19b2226f4c95694b3.
This was added in vim/vim#16807, with no explanation for why it was necessary beyond
"it's an example of an idea". It completely breaks `gq` for me—rustfmt doesn't
reflow comments so is not an appropriate tool here! Beyond that, formatting a
selection with rustfmt treats that selection as if it were an entire file,
throwing away any indentation.
For example, the commit causes `gq` to turn this:
```rust
pub fn foo() {
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
}
```
into this:
```rust
pub fn foo() {
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
}
```
which is totally wrong. In contrast, if I clear `formatprg` then `gq` does the
right thing again:
```rust
pub fn foo() {
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
// blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
// blah blah blah blah blah blah
}
```
related: vim/vim#16967
related: vim/vim#17055
closes: vim/vim#18640
https://github.com/vim/vim/commit/eba51337d4b8051b768164f3394d680742234ca8
Co-authored-by: Aaron Jacobs <jacobsa@google.com>
|
|
closes: vim/vim#16967
https://github.com/vim/vim/commit/4ac995bf9366c6624a0724d19b2226f4c95694b3
Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
|
|
just to foster best practices
closes: vim/vim#15798
https://github.com/vim/vim/commit/7c3f9af0ed5dd7035f8a3fbb2f0bf965a453e359
Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
|
|
Problem: no whitespace padding in commentstring option in ftplugins
Solution: Change default to include whitespace padding, update
existing filetype plugins with the new default value
(Riley Bruins)
closes: vim/vim#14843
https://github.com/vim/vim/commit/0a0830624a260660c7fa692ecb7e6e5de09114ba
Co-authored-by: Riley Bruins <ribru17@hotmail.com>
|
|
runtime(rust): Respect no_plugin_maps and no_rust_maps globals (vim/vim#14221)
https://github.com/vim/vim/commit/ef21bcaab145d6b22fb7c823607de23700f82653
Co-authored-by: MyyPo <110892040+MyyPo@users.noreply.github.com>
|
|
runtime(rust): sync rust runtime files with upstream (vim/vim#13075)
https://github.com/vim/vim/commit/fc93594d562dbbd9da03c89754538f91efd0c7ca
Co-authored-by: Gregory Anders <8965202+gpanders@users.noreply.github.com>
|
|
Update my name and email in runtime files (vim/vim#12763)
https://github.com/vim/vim/commit/21aaff3faa828c5c2677a0a9f1b90a0b780d57f6
Co-authored-by: Lily Ballard <lily@ballards.net>
|
|
Update runtime files. Add Rust support.
https://github.com/vim/vim/commit/3c2881dc1195f53ebafc387378399ddd6cb677a7
|
