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.

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

Next/prev jump to end of span. #397

Merged
merged 1 commit into from
Jul 24, 2019
Merged

Next/prev jump to end of span. #397

merged 1 commit into from
Jul 24, 2019

Conversation

ehuss
Copy link

@ehuss ehuss commented Jul 21, 2019

This changes the next/prev commands to jump to the end of a message span instead
of the beginning. When using inline phantoms, jumping to the beginning can
be hard to see the message for a multi-line message.

I've flip-flopped over time which I like better. I've been using "end" for a
while now, and it seems to work better for me. If anyone objects, we can always
add a config setting.

This also changes how the test works, since the old test didn't handle this new
format very well.

This changes the next/prev commands to jump to the end of a message span instead
of the beginning. When using inline phantoms, jumping to the beginning can
be hard to see the message for a multi-line message.

I've flip-flopped over time which I like better. I've been using "end" for a
while now, and it seems to work better for me. If anyone objects, we can always
add a config setting.

This also changes how the test works, since the old test didn't handle this new
format very well.
@ehuss
Copy link
Author

ehuss commented Jul 24, 2019

bors r+

bors bot added a commit that referenced this pull request Jul 24, 2019
397: Next/prev jump to end of span. r=ehuss a=ehuss

This changes the next/prev commands to jump to the end of a message span instead
of the beginning. When using inline phantoms, jumping to the beginning can
be hard to see the message for a multi-line message.

I've flip-flopped over time which I like better. I've been using "end" for a
while now, and it seems to work better for me. If anyone objects, we can always
add a config setting.

This also changes how the test works, since the old test didn't handle this new
format very well.

Co-authored-by: Eric Huss <eric@huss.org>
@bors
Copy link

bors bot commented Jul 24, 2019

Build succeeded

  • continuous-integration/travis-ci/push

@bors bors bot merged commit ce5bb8b into rust-lang:master Jul 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant