2015-11-11 14:01:38 -06:00
|
|
|
# rustfmt [![Build Status](https://travis-ci.org/rust-lang-nursery/rustfmt.svg)](https://travis-ci.org/rust-lang-nursery/rustfmt)
|
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
|
|
|
|
2015-12-15 22:58:20 -06:00
|
|
|
## Quick start
|
|
|
|
|
|
|
|
To install:
|
|
|
|
|
|
|
|
```
|
2015-12-15 23:00:40 -06:00
|
|
|
cargo install rustfmt
|
2015-12-15 22:58:20 -06:00
|
|
|
```
|
|
|
|
|
|
|
|
to run on a cargo project in the current working directory:
|
|
|
|
|
|
|
|
```
|
|
|
|
cargo fmt
|
|
|
|
```
|
2015-10-23 15:51:29 -05:00
|
|
|
|
|
|
|
## Installation
|
|
|
|
|
2015-11-11 11:34:17 -06:00
|
|
|
> **Note:** this method currently requires you to be running cargo 0.6.0 or
|
|
|
|
> newer.
|
2015-10-23 15:51:29 -05:00
|
|
|
|
|
|
|
```
|
2015-12-15 23:00:40 -06:00
|
|
|
cargo install rustfmt
|
2015-10-23 15:51:29 -05:00
|
|
|
```
|
|
|
|
|
2015-10-26 21:51:59 -05:00
|
|
|
or if you're using [`multirust`](https://github.com/brson/multirust)
|
2015-10-23 15:51:29 -05:00
|
|
|
|
|
|
|
```
|
2015-12-15 23:00:40 -06:00
|
|
|
multirust run nightly cargo install rustfmt
|
2015-10-23 15:51:29 -05:00
|
|
|
```
|
2015-04-29 22:09:33 -05:00
|
|
|
|
2015-12-15 21:41:58 -06:00
|
|
|
Usually cargo-fmt, which enables usage of Cargo subcommand `cargo fmt`, is
|
|
|
|
installed alongside rustfmt. To only install rustfmt run
|
|
|
|
|
|
|
|
```
|
2015-12-15 23:00:40 -06:00
|
|
|
cargo install --no-default-features rustfmt
|
2015-12-15 21:41:58 -06:00
|
|
|
```
|
2015-11-03 22:45:01 -06: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
|
|
|
|
replace, overwrite, display, and coverage. The replace mode is the default
|
|
|
|
and overwrites the original files after renaming them. In overwrite mode,
|
|
|
|
rustfmt does not backup the source files. To print the output to stdout, use the
|
|
|
|
display mode. The write mode can be set by passing the `--write-mode` flag on
|
|
|
|
the command line.
|
|
|
|
|
|
|
|
`rustfmt filename --write-mode=display` prints the output of rustfmt to the
|
|
|
|
screen, for example.
|
|
|
|
|
|
|
|
You can run `rustfmt --help` for more information.
|
|
|
|
|
2015-12-15 23:07:59 -06:00
|
|
|
`cargo fmt` uses `--write-mode=replace` by default.
|
|
|
|
|
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
|
|
|
|
2015-11-12 03:44:28 -06:00
|
|
|
* [Vim](http://johannh.me/blog/rustfmt-vim.html)
|
|
|
|
* [Emacs](https://github.com/fbergroth/emacs-rustfmt)
|
2015-12-11 20:11:09 -06:00
|
|
|
* [Sublime Text 3](https://packagecontrol.io/packages/BeautifyRust)
|
2015-11-16 23:24:42 -06:00
|
|
|
* [Atom](atom.md)
|
2016-01-01 11:30:36 -06:00
|
|
|
* Visual Studio Code using [RustyCode](https://github.com/saviorisdead/RustyCode) or [vsc-rustfmt](https://github.com/Connorcpu/vsc-rustfmt)
|
2015-11-03 22:45:01 -06:00
|
|
|
|
2015-08-31 21:42:58 -05:00
|
|
|
## How to build and test
|
2015-10-23 15:51:29 -05:00
|
|
|
|
2015-11-03 22:45:01 -06:00
|
|
|
First make sure you've got Rust **1.4.0** or greater available, then:
|
2015-06-01 19:30:46 -05:00
|
|
|
|
2015-04-29 22:09:33 -05:00
|
|
|
`cargo build` to build.
|
|
|
|
|
|
|
|
`cargo test` to run all tests.
|
|
|
|
|
2015-12-14 18:18:47 -06:00
|
|
|
To run rustfmt after this, use `cargo run --bin rustfmt -- filename`. See the
|
2015-12-15 21:41:58 -06:00
|
|
|
notes above on running rustfmt.
|
2015-11-03 22:45:01 -06:00
|
|
|
|
|
|
|
|
2015-11-09 12:34:44 -06:00
|
|
|
## What style does Rustfmt use?
|
|
|
|
|
|
|
|
Rustfmt is designed to be very configurable. You can create a TOML file called
|
|
|
|
rustfmt.toml, place it in the project directory and it will apply the options
|
2015-11-14 09:43:18 -06:00
|
|
|
in that file. See `cargo run -- --config-help` for the options which are available,
|
2015-11-09 12:34:44 -06:00
|
|
|
or if you prefer to see source code, [src/config.rs].
|
|
|
|
|
2015-11-28 03:03:46 -06:00
|
|
|
By default, Rustfmt uses a style which (mostly) conforms to the
|
2015-11-09 12:34:44 -06:00
|
|
|
[Rust style guidelines](https://github.com/rust-lang/rust/tree/master/src/doc/style).
|
|
|
|
There are many details which the style guidelines do not cover, and in these
|
|
|
|
cases we try to adhere to a style similar to that used in the
|
|
|
|
[Rust repo](https://github.com/rust-lang/rust). Once Rustfmt is more complete, and
|
|
|
|
able to re-format large repositories like Rust, we intend to go through the Rust
|
|
|
|
RFC process to nail down the default style in detail.
|
|
|
|
|
|
|
|
If there are styling choices you don't agree with, we are usually happy to add
|
|
|
|
options covering different styles. File an issue, or even better, submit a PR.
|
|
|
|
|
|
|
|
|
2015-11-03 22:45:01 -06:00
|
|
|
## Gotchas
|
|
|
|
|
|
|
|
* 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
|
|
|
|
#[rustfmt_skip]
|
|
|
|
#[cfg_attr(rustfmt, rustfmt_skip)]
|
2015-11-03 22:45:01 -06:00
|
|
|
```
|
|
|
|
* When you run rustfmt, place a file named rustfmt.toml in target file
|
|
|
|
directory or its parents to override the default settings of rustfmt.
|
|
|
|
* After successful compilation, a `rustfmt` executable can be found in the
|
|
|
|
target directory.
|