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

[LP: #1836601] whitespace cleanups needed (tabs to spaces) #42

Open
paride opened this issue May 24, 2022 · 0 comments
Open

[LP: #1836601] whitespace cleanups needed (tabs to spaces) #42

paride opened this issue May 24, 2022 · 0 comments

Comments

@paride
Copy link
Collaborator

paride commented May 24, 2022

Originally reported by: Scott Moser (@smoser) on 2019-07-15
Original bug URL: https://bugs.launchpad.net/cloud-utils/+bug/1836601
Last Launchpad Status: Triaged
Last Launchpad Severity: Wishlist


When I started cloud-utils long ago, I was under the misguided view that tabs could be used reliably in source code. I have now accepted that without a machine formatted (go fmt) that is not the case.

An example can be seen in cloud-utils itself that has mixed tabs and spaces for indentation. smoser fail.

So, this bug is a request to:

a.) change tabs used for indentation to 4 spaces.
b.) change the vi modeline to be correct, and make sure it is present at the end of all files.

The correct modeline for 4 spaces indentation is:

   # vi: ts=4 expandtab

Note... if someone insists that the right fix is to remove modelines entirely [1] then I would accept that, but something needs to insist on consistent indentation, and I used vi modelines as a mechanism for declaring the style in a file.

--
[1] https://security.stackexchange.com/questions/36001/vim-modeline-vulnerabilities

@paride paride changed the title whitespace cleanups needed (tabs to spaces) [LP: 1836601] whitespace cleanups needed (tabs to spaces) May 24, 2022
@paride paride changed the title [LP: 1836601] whitespace cleanups needed (tabs to spaces) [LP: #1836601] whitespace cleanups needed (tabs to spaces) May 24, 2022
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

No branches or pull requests

1 participant