Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Hide #[test] functions by default in emacs #3531

Closed
brson opened this issue Sep 19, 2012 · 2 comments
Closed

Hide #[test] functions by default in emacs #3531

brson opened this issue Sep 19, 2012 · 2 comments

Comments

@brson
Copy link
Contributor

brson commented Sep 19, 2012

It would be nice if emacs did 'folding' to hide the bodies of test functions. Tests are very convenient to write inline, and it's great to put tests as close to the functions they test as possible, but having tests littered everywhere makes reading the code later not as fun.
@mpenet
Copy link
Contributor

mpenet commented Sep 22, 2012

I am not sure it is a good idea to have this part of the mode itself, it is a very uncommon/specific feature for a language mode imho, but you can probably achieve this using folding-mode or something similar (I am told it is really easy to setup).

@brson
Copy link
Contributor Author

brson commented Sep 25, 2012

Agreed it doesn't belong in rust-mode, and it sounds like folding-mode can do this trivially, so there's nothing to do here. Thanks, @mpenet.

@brson brson closed this as completed Sep 25, 2012
RalfJung pushed a commit to RalfJung/rust that referenced this issue May 4, 2024
@bors
Auto merge of rust-lang#3531 - narpfel:quiet-sysroot, r=RalfJung
b0bdbcc 
Don’t print `Preparing a sysroot` when `-q`/`--quiet` is passed

Resolves rust-lang#3530.

This also fixes a typo in `cargo miri --help` that I found while trying to run the `--print-sysroot` example.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mpenet @brson