averello/vim-mirror
1
0
Fork 0
mirror of https://github.com/vim/vim.git synced 2026-01-15 12:22:36 +01:00
Code Issues Packages Projects Releases Wiki Activity
22,743 Commits 1 Branch 18,817 Tags
fc00006777594f969ba8fcff676e6ca1bcb43546
Commit Graph

11 Commits

Author SHA1 Message Date
Christian Brabandt
62d8f3dab5 runtime: Revert several "mark invalid contact addresses" commits 
This reverts commits:
- 6b652a7850
- 2f689d5abd
- a025a46d41

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.

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2026-01-01 15:14:14 +00:00
Christian Brabandt
2f689d5abd runtime: mark more invalid email addresses 
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2025-12-31 16:38:08 +00:00
Aaron Jacobs
98ef8433b6 runtime(rust): use textwidth=100 for the Rust recommended style 
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](37aa2135b5/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: #18892

Signed-off-by: Aaron Jacobs <jacobsa@google.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2025-12-09 12:43:39 +01:00
Aaron Jacobs
eba51337d4 runtime(rust): Do not use rustfmt as 'formatprg' by default 
This reverts commit 4ac995bf93.

This was added in #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: #16967
related: #17055
closes: #18640

Signed-off-by: Aaron Jacobs <jacobsa@google.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2025-10-27 17:46:11 +00:00
Konfekt
4ac995bf93 runtime(rust): set formatprg to rustfmt 
closes: #16967

Signed-off-by: Konfekt <Konfekt@users.noreply.github.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2025-03-31 20:54:50 +02:00
Konfekt
7c3f9af0ed runtime(misc): unset compiler in various ftplugins 
just to foster best practices

closes: #15798

Signed-off-by: Konfekt <Konfekt@users.noreply.github.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-10-05 17:26:46 +02:00
Riley Bruins
0a0830624a patch 9.1.0464: no whitespace padding in commentstring option in ftplugins 
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: #14843

Signed-off-by: Riley Bruins <ribru17@hotmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-06-03 20:40:45 +02:00
MyyPo
ef21bcaab1 runtime(rust): Respect no_plugin_maps and no_rust_maps globals (#14221) 
Signed-off-by: myypo <nikirsmcgl@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-03-18 19:38:09 +01:00
Gregory Anders
fc93594d56 runtime(rust): sync rust runtime files with upstream (#13075) 
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2023-09-12 20:23:38 +02:00
Lily Ballard
21aaff3faa Update my name and email in runtime files (#12763) 2023-08-11 19:30:27 +02:00
Bram Moolenaar
3c2881dc11 Update runtime files. Add Rust support. 2017-03-21 19:18:29 +01:00