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

fish_indent - Don't force single-command variables to be on the same line #7955

Closed
IlanCosman opened this issue Apr 25, 2021 · 0 comments
Closed

Comments

@IlanCosman
Copy link
Contributor

This:

function foo
    first_long_variable=something \
    second_long_variable=something_else \
    echo $first_long_variable $second_long_variable
end

is obviously nicer than this:

function foo
    first_long_variable=something second_long_variable=something_else echo $first_long_variable $second_long_variable
end
@IlanCosman IlanCosman changed the title Don't force single-command variables to be on the same line fish_indent - Don't force single-command variables to be on the same line Apr 25, 2021
@krobelus krobelus modified the milestones: fish-future, fish 3.3.0 Apr 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants