2018-02-07 18:47:23 -06:00
# rustfmt [![Build Status](https://travis-ci.org/rust-lang-nursery/rustfmt.svg)](https://travis-ci.org/rust-lang-nursery/rustfmt) [![Build Status](https://ci.appveyor.com/api/projects/status/github/rust-lang-nursery/rustfmt?svg=true)](https://ci.appveyor.com/project/nrc/rustfmt) [![crates.io](https://img.shields.io/crates/v/rustfmt-nightly.svg)](https://crates.io/crates/rustfmt-nightly) [![Travis Configuration Status](https://img.shields.io/travis/davidalber/rustfmt-travis.svg?label=travis%20example)](https://travis-ci.org/davidalber/rustfmt-travis)
2015-04-29 22:09:33 -05:00
A tool for formatting Rust code according to style guidelines.
2015-11-09 12:34:44 -06:00
If you'd like to help out (and you should, it's a fun project!), see
2015-11-11 16:46:55 -06:00
[Contributing.md ](Contributing.md ).
2015-11-09 12:34:44 -06:00
2017-06-21 12:45:24 -05:00
We are changing the default style used by rustfmt. There is an ongoing [RFC
process][fmt rfcs]. The last version using the old style was 0.8.6. From 0.9
onwards, the RFC style is the default. If you want the old style back, you can
use [legacy-rustfmt.toml ](legacy-rustfmt.toml ) as your rustfmt.toml.
2017-06-11 22:50:43 -05:00
2017-06-13 20:57:31 -05:00
The current `master` branch uses libsyntax (part of the compiler). It is
published as `rustfmt-nightly` . The `syntex` branch uses Syntex instead of
libsyntax, it is published (for now) as `rustfmt` . Most development happens on
the `master` branch, however, this only supports nightly toolchains. If you use
stable or beta Rust toolchains, you must use the Syntex version (which is likely
to be a bit out of date). Version 0.1 of rustfmt-nightly is forked from version
0.9 of the syntex branch.
2018-02-07 18:47:23 -06:00
You can use rustfmt in Travis CI builds. We provide a minimal Travis CI
configuration (see [here ](#checking-style-on-a-ci-server )) and verify its status
using another repository. The status of that repository's build is reported by
the "travis example" badge above.
2017-05-17 02:07:25 -05:00
2015-12-15 22:58:20 -06:00
## Quick start
2018-02-15 13:35:45 -06:00
You can use `rustfmt` on Rust 1.24 and above.
2017-06-15 19:00:43 -05:00
2015-12-15 22:58:20 -06:00
To install:
```
2018-02-15 13:35:45 -06:00
rustup component add rustfmt-preview
2015-12-15 22:58:20 -06:00
```
to run on a cargo project in the current working directory:
```
2018-02-15 13:35:45 -06:00
cargo fmt
2015-12-15 22:58:20 -06:00
```
2015-10-23 15:51:29 -05:00
2018-01-05 08:34:45 -06:00
## Installation
2017-06-15 19:00:43 -05:00
```
2018-02-15 13:35:45 -06:00
rustup component add rustfmt-preview
2015-10-23 15:51:29 -05:00
```
2016-05-28 10:38:33 -05:00
## Installing from source
To install from source, first checkout to the tag or branch you want to install, then issue
```
cargo install --path .
```
2017-06-15 19:00:43 -05:00
2017-04-26 10:36:10 -05:00
This will install `rustfmt` in your `~/.cargo/bin` . Make sure to add `~/.cargo/bin` directory to
2016-05-28 10:38:33 -05:00
your PATH variable.
2015-11-03 22:45:01 -06:00
2017-06-15 19:00:43 -05:00
2015-12-13 13:17:26 -06:00
## Running
2015-12-15 21:41:58 -06:00
You can run Rustfmt by just typing `rustfmt filename` if you used `cargo
2015-12-13 13:17:26 -06:00
install`. This runs rustfmt on the given file, if the file includes out of line
modules, then we reformat those too. So to run on a whole module or crate, you
just need to run on the root file (usually mod.rs or lib.rs). Rustfmt can also
2015-12-15 21:41:58 -06:00
read data from stdin. Alternatively, you can use `cargo fmt` to format all
binary and library targets of your crate.
2015-12-13 13:17:26 -06:00
You'll probably want to specify the write mode. Currently, there are modes for
2017-07-20 16:10:27 -05:00
`diff` , `replace` , `overwrite` , `display` , `coverage` , `checkstyle` , and `plain` .
2016-01-22 21:33:59 -06:00
2017-07-20 16:10:27 -05:00
* `overwrite` Is the default and overwrites the original files _without_ creating backups.
* `replace` Overwrites the original files after creating backups of the files.
2016-01-23 10:33:50 -06:00
* `display` Will print the formatted files to stdout.
2017-07-20 16:10:27 -05:00
* `plain` Also writes to stdout, but with no metadata.
2016-01-23 10:33:50 -06:00
* `diff` Will print a diff between the original files and formatted files to stdout.
2016-08-24 14:25:31 -05:00
Will also exit with an error code if there are any differences.
2016-01-22 21:33:59 -06:00
* `checkstyle` Will output the lines that need to be corrected as a checkstyle XML file,
that can be used by tools like Jenkins.
The write mode can be set by passing the `--write-mode` flag on
the command line. For example `rustfmt --write-mode=display src/filename.rs`
2015-12-13 13:17:26 -06:00
2017-07-20 16:10:27 -05:00
`cargo fmt` uses `--write-mode=overwrite` by default.
2015-12-15 23:07:59 -06:00
2016-04-10 12:03:54 -05:00
If you want to restrict reformatting to specific sets of lines, you can
use the `--file-lines` option. Its argument is a JSON array of objects
with `file` and `range` properties, where `file` is a file name, and
`range` is an array representing a range of lines like `[7,13]` . Ranges
2016-05-30 17:42:14 -05:00
are 1-based and inclusive of both end points. Specifying an empty array
will result in no files being formatted. For example,
2016-04-10 12:03:54 -05:00
```
rustfmt --file-lines '[
{"file":"src/lib.rs","range":[7,13]},
{"file":"src/lib.rs","range":[21,29]},
{"file":"src/foo.rs","range":[10,11]},
{"file":"src/foo.rs","range":[15,15]}]'
```
would format lines `7-13` and `21-29` of `src/lib.rs` , and lines `10-11` ,
and `15` of `src/foo.rs` . No other files would be formatted, even if they
are included as out of line modules from `src/lib.rs` .
2016-04-14 18:51:50 -05:00
If `rustfmt` successfully reformatted the code it will exit with `0` exit
status. Exit status `1` signals some unexpected error, like an unknown option or
a failure to read a file. Exit status `2` is returned if there are syntax errors
2017-11-01 01:33:55 -05:00
in the input files. `rustfmt` can't format syntactically invalid code. Finally,
2016-04-14 18:51:50 -05:00
exit status `3` is returned if there are some issues which can't be resolved
automatically. For example, if you have a very long comment line `rustfmt`
doesn't split it. Instead it prints a warning and exits with `3` .
You can run `rustfmt --help` for more information.
2015-12-13 13:17:26 -06:00
2015-11-12 03:44:28 -06:00
## Running Rustfmt from your editor
2015-11-03 22:45:01 -06:00
2016-10-10 20:35:07 -05:00
* [Vim ](https://github.com/rust-lang/rust.vim#formatting-with-rustfmt )
2016-10-05 08:19:21 -05:00
* [Emacs ](https://github.com/rust-lang/rust-mode )
2017-05-31 16:39:12 -05:00
* [Sublime Text 3 ](https://packagecontrol.io/packages/RustFmt )
2015-11-16 23:24:42 -06:00
* [Atom ](atom.md )
2017-05-12 06:06:28 -05:00
* Visual Studio Code using [vscode-rust ](https://github.com/editor-rs/vscode-rust ), [vsc-rustfmt ](https://github.com/Connorcpu/vsc-rustfmt ) or [rls_vscode ](https://github.com/jonathandturner/rls_vscode ) through RLS.
2015-11-03 22:45:01 -06:00
2016-08-24 14:25:31 -05:00
## Checking style on a CI server
To keep your code base consistently formatted, it can be helpful to fail the CI build
when a pull request contains unformatted code. Using `--write-mode=diff` instructs
rustfmt to exit with an error code if the input is not formatted correctly.
It will also print any found differences.
2018-02-17 01:47:54 -06:00
A minimal Travis setup could look like this (requires Rust 1.24.0 or greater):
2016-08-24 14:25:31 -05:00
```yaml
language: rust
2017-02-26 13:34:32 -06:00
before_script:
2018-02-17 01:47:54 -06:00
- rustup component add rustfmt-preview
2016-08-24 14:25:31 -05:00
script:
2018-02-17 01:47:54 -06:00
- cargo fmt --all -- --write-mode=diff
2017-02-26 13:34:32 -06:00
- cargo build
- cargo test
2016-08-24 14:25:31 -05:00
```
2015-08-31 21:42:58 -05:00
## How to build and test
2015-10-23 15:51:29 -05:00
2015-04-29 22:09:33 -05:00
`cargo build` to build.
`cargo test` to run all tests.
2018-02-25 21:39:36 -06:00
To run Rustfmt, you'll need the binaries repo: https://github.com/rust-lang-nursery/rustfmt-bin
2015-11-03 22:45:01 -06:00
2016-01-13 22:58:23 -06:00
## Configuring Rustfmt
2015-11-09 12:34:44 -06:00
Rustfmt is designed to be very configurable. You can create a TOML file called
2016-07-31 16:32:35 -05:00
`rustfmt.toml` or `.rustfmt.toml` , place it in the project or any other parent
directory and it will apply the options in that file. See `rustfmt
--config-help` for the options which are available, or if you prefer to see
2017-04-26 10:36:10 -05:00
visual style previews, [Configurations.md ](Configurations.md ).
2015-11-09 12:34:44 -06:00
2017-06-21 12:45:24 -05:00
By default, Rustfmt uses a style which conforms to the [Rust style guide][style
2017-11-21 12:25:36 -06:00
guide] that has been formalized through the [style RFC
process][fmt rfcs].
2015-11-09 12:34:44 -06:00
2017-12-04 01:10:36 -06:00
Configuration options are either stable or unstable. Stable options can always
be used, while unstable ones are only available on a nightly toolchain, and opt-in.
See [Configurations.md ](Configurations.md ) for details.
2015-11-09 12:34:44 -06:00
2016-05-15 17:09:53 -05:00
## Tips
2015-11-03 22:45:01 -06:00
* For things you do not want rustfmt to mangle, use one of
2015-11-20 12:58:57 -06:00
2015-11-09 12:34:44 -06:00
```rust
2016-03-16 23:51:16 -05:00
#[rustfmt_skip] // requires nightly and #![feature(custom_attribute)] in crate root
#[cfg_attr(rustfmt, rustfmt_skip)] // works in stable
2015-11-03 22:45:01 -06:00
```
2016-07-31 16:32:35 -05:00
* When you run rustfmt, place a file named `rustfmt.toml` or `.rustfmt.toml` in
target file directory or its parents to override the default settings of
2017-09-18 21:56:49 -05:00
rustfmt. You can generate a file containing the default configuration with
2017-11-01 01:33:55 -05:00
`rustfmt --dump-default-config rustfmt.toml` and customize as needed.
2015-11-03 22:45:01 -06:00
* After successful compilation, a `rustfmt` executable can be found in the
target directory.
2016-05-15 17:09:53 -05:00
* If you're having issues compiling Rustfmt (or compile errors when trying to
install), make sure you have the most recent version of Rust installed.
2016-04-14 13:48:21 -05:00
2017-07-13 16:02:40 -05:00
* If you get an error like `error while loading shared libraries` while starting
up rustfmt you should try the following:
2017-12-31 20:41:46 -06:00
On Linux:
2017-07-13 16:02:40 -05:00
2017-12-31 20:41:46 -06:00
```
export LD_LIBRARY_PATH=$(rustc --print sysroot)/lib:$LD_LIBRARY_PATH
```
2017-07-13 16:02:40 -05:00
2017-12-31 20:41:46 -06:00
On MacOS:
2017-07-13 16:02:40 -05:00
2017-12-31 20:41:46 -06:00
```
export DYLD_LIBRARY_PATH=$(rustc --print sysroot)/lib:$DYLD_LIBRARY_PATH
```
2016-04-14 13:48:21 -05:00
2017-12-31 20:41:46 -06:00
On Windows (Git Bash/Mingw):
2017-08-12 02:38:12 -05:00
2017-12-31 20:41:46 -06:00
```
export PATH=$(rustc --print sysroot)/lib/rustlib/x86_64-pc-windows-gnu/lib/:$PATH
```
2017-08-12 02:38:12 -05:00
2017-12-31 20:41:46 -06:00
(Substitute `x86_64` by `i686` and `gnu` by `msvc` depending on which version of rustc was used to install rustfmt).
2017-08-12 02:38:12 -05:00
2016-04-14 13:48:21 -05:00
## License
Rustfmt is distributed under the terms of both the MIT license and the
Apache License (Version 2.0).
See [LICENSE-APACHE ](LICENSE-APACHE ) and [LICENSE-MIT ](LICENSE-MIT ) for details.
2017-06-21 12:45:24 -05:00
[rust]: https://github.com/rust-lang/rust
[fmt rfcs]: https://github.com/rust-lang-nursery/fmt-rfcs
[style guide]: https://github.com/rust-lang-nursery/fmt-rfcs/blob/master/guide/guide.md