about summary refs log tree commit diff
path: root/src/etc/vim
AgeCommit message (Collapse)AuthorLines
2015-01-29Pull configs out into individual repositoriesSteve Klabnik-1198/+0
As we grow, these don't belong in-tree. http://internals.rust-lang.org/t/moving-editor-highlighting-into-their-own-repos/1395 * https://github.com/rust-lang/rust.vim * https://github.com/rust-lang/rust-mode * https://github.com/rust-lang/gedit-config * https://github.com/rust-lang/kate-config * https://github.com/rust-lang/nano-config * https://github.com/rust-lang/zsh-config
2015-01-25fix vim syntastic: --parse-only => -Z parse-onlyemanueLczirai-1/+1
when saving .rs files under vim do not fail to run the syntax checker error: Unrecognized option: 'parse-only'. due to this commit 953f294ea30253bb5578e3c895d17fcc97c20dce which removed the deprecated flag --parse-only
2015-01-11Remove range functionTim Brooks-2/+0
2015-01-11Remove old number literal suffixes from Vim syntaxTim Brooks-5/+5
2015-01-07Update editor syntax files for isize/usize.Huon Wilson-1/+1
Yay, syntax highlighting.
2015-01-05rollup merge of #20482: kmcallister/macro-reformAlex Crichton-1/+1
Conflicts: src/libflate/lib.rs src/libstd/lib.rs src/libstd/macros.rs src/libsyntax/feature_gate.rs src/libsyntax/parse/parser.rs src/libsyntax/show_span.rs src/test/auxiliary/macro_crate_test.rs src/test/compile-fail/lint-stability.rs src/test/run-pass/intrinsics-math.rs src/test/run-pass/tcp-connect-timeouts.rs
2015-01-05Reserve the keyword 'macro'Keegan McAllister-1/+1
2015-01-05Update reexports in vim syntax fileChase Southwood-41/+19
2015-01-02Fix vim syntax highlighting for `derive`Chase Southwood-4/+4
2014-12-15rollup merge of #19804: kballard/vim-new-unicode-escapesBrian Anderson-1/+2
2014-12-15rollup merge of #19784: csouth3/vim-syntax-iterBrian Anderson-1/+1
Vim still incorrectly highlights just `ExactSize` as a valid trait name, but the trait has been renamed to `ExactSizeIterator`.
2014-12-14Update emacs and vi modes.Niko Matsakis-1/+1
2014-12-12vim: Support the new \u{1234} unicode escapesKevin Ballard-1/+2
2014-12-12Update vim syntax highlighting for ExactSizeIteratorChase Southwood-1/+1
2014-11-22auto merge of #19125 : chris-morgan/rust/vim-prelude-2014-11-20, r=alexcrichtonbors-32/+27
2014-11-22auto merge of #17513 : dradtke/rust/master, r=kballardbors-15/+38
Looks like I made my previous PR a little too hastily. =) This PR fixes a couple issues that I discovered with my previous revision: 1. Updated the errorformat to ignore "pointer lines" so that they don't show up in the output (with quickfix jumping, they're redundant and unnecessary). 2. Renamed a couple variables to be more in line with Cargo's terminology (`g:cargo_toml_name` should now be `g:cargo_manifest_name`). 3. Added support for errors reported with absolute paths (looks to be the case when compiling an executable instead of a library). 4. Most importantly, added support for errors reported while compiling a dependency. When building a Cargo package with local dependencies, if one of those dependencies failed to compile, the quickfix would be completely broken as it assumed that all errors were relative to the local manifest, or the closest Cargo.toml. With this update, it now pays attention to lines that end with `(file://<path>)`, and from then on adjusts all errors to be relative to `<path>`. As a side note, that `<path>` output is somewhat broken on Windows. While `file:///home/damien/...` on *Nix is a valid URI, `file:///C:/Users/damien/...` on Windows is not, because `C:/` (or whatever the drive is) should take the place of the third slash which is *Nix's root, not be appended to it. I added a workaround for this in my script, but I figured I'd mention it to see if this is a bug in how Rust formats paths.
2014-11-20Update the Vim syntax prelude.Chris Morgan-32/+27
2014-11-19Adding switch in vim plugin to toggle format optsjuxiliary-3/+13
2014-11-16Rename IntoStr to IntoStringBrendan Zabarauskas-1/+1
For consistancy with ToString
2014-11-13Remove Signed trait and add SignedInt traitBrendan Zabarauskas-1/+1
The methods have been moved into Float and SignedInt
2014-11-13Deprecate Num, Unsigned and PrimitiveBrendan Zabarauskas-2/+1
2014-11-13Move checked arithmetic operators into Int traitBrendan Zabarauskas-1/+1
2014-11-10vim: move 'move' to rustStorageJosh Stone-2/+2
2014-11-10auto merge of #18782 : netvl/rust/update-vim-syntax, r=alexcrichtonbors-6/+6
`as` (already for a long time) and `move` (which was only added recently, AFAIK) are not marked as keywords in Vim syntax file, so they are not highlighted as keywords in Rust sources. This PR fixes this.
2014-11-09Added `move` keyword and renamed `fail` to `panic`Vladimir Matveev-6/+6
2014-11-08Renamed Extendable to Extendgamazeps-1/+1
In order to upgrade, simply rename the Extendable trait to Extend in your code Part of #18424 [breaking-change]
2014-11-04Added check for absolute file path, removed hard tab, and added ↵Damien Radtke-3/+14
documentation for new option.
2014-10-24Updates based on kballard's feedback.Damien Radtke-20/+11
2014-10-22vim: Fix :RustRun when cwd has a space in itKevin Ballard-6/+6
2014-10-14Highlight 1..2 according to the current grammar.Chris Morgan-2/+3
2014-10-14Highlight `extern crate "foo" as bar;` properly.Chris Morgan-1/+3
2014-10-14Vim: Stop highlighting foo in `use foo;` speciallyChris Morgan-4/+1
This wasn’t really consistent with other things; the last section of the import was not highlighted in any other case. Also `use {foo, bar};` was having the foo and bar not highlighted, where they would have been as separate statements.
2014-10-07Add `abstract`, `final`, and `override` to rust.vim keyword listJohn Gallagher-1/+1
2014-10-07Use rustc's errorformat and add option to specify permanent parameters.Damien Radtke-4/+15
2014-09-30auto merge of #17479 : gamazeps/rust/issue17478, r=alexcrichtonbors-1/+1
closes #17478
2014-09-29Replaced some TODO by FIXMEgamazeps-1/+1
closes #17478
2014-09-24Some improvements to the Cargo compiler file.Damien Radtke-9/+19
2014-09-22Add cargo.vim compiler file.Damien Radtke-0/+49
2014-09-18fix for vim < 7.4.355Julian Orth-0/+37
2014-09-13update vim indent fileJulian Orth-38/+3
2014-08-17auto merge of #16547 : huonw/rust/new-kw, r=pcwaltonbors-1/+1
2014-08-17auto merge of #16535 : michaelsproul/rust/vim-traits, r=pcwaltonbors-8/+8
The vim syntax highlighting file had become out of sync with the real prelude. Lots of Vector -> Slice renames have happened recently.
2014-08-17Add new keywords (particularly `where` & `virtual`) to editor modes.Huon Wilson-1/+1
2014-08-16vim: Update syntax file for Prelude changes.Michael Sproul-8/+8
Lots of Vector -> Slice renames.
2014-08-15vim: Don't set foldmethod in the syntax file eitherKevin Ballard-11/+14
We shouldn't be setting any settings in the syntax file. Better to put them in the ftplugin, where they won't be pulled in by :syn-include and can be cleaned up when changing the filetype.
2014-08-13vim: Stop setting conceallevel in the syntax fileKevin Ballard-2/+9
We shouldn't be setting conceallevel in the syntax file. Besides not being able to undo this if we switch to another syntax later, it also interferes with embedding rust in other filetypes (such as markdown). Instead, set it in the ftplugin, where it belongs.
2014-08-07Rename `Share` to `Sync`Alex Crichton-1/+1
This leaves the `Share` trait at `std::kinds` via a `#[deprecated]` `pub use` statement, but the `NoShare` struct is no longer part of `std::kinds::marker` due to #12660 (the build cannot bootstrap otherwise). All code referencing the `Share` trait should now reference the `Sync` trait, and all code referencing the `NoShare` type should now reference the `NoSync` type. The functionality and meaning of this trait have not changed, only the naming. Closes #16281 [breaking-change]
2014-07-23vim: Add MutableSeqBrian Anderson-1/+1
2014-07-21Fix :syn-include usage of Vim filetype.Chris Morgan-3/+5
Here’s what the Vim manual says in *:syn-include*: :sy[ntax] include [@{grouplist-name}] {file-name} All syntax items declared in the included file will have the "contained" flag added. In addition, if a group list is specified, all top-level syntax items in the included file will be added to that list. We had two rules for `rustModPath`, one `contained` and the other not. The effect was that the second (now renamed to `rustModPathInUse`) was being included in the group list, and thus that all identifiers were being highlighted as `Include`, which is definitely not what we wanted.
2014-07-21Highlight $(…)* and $foo in Vim.Chris Morgan-0/+7
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-15 21:27:04 +0000