- 24 Jan, 2022 8 commits
-
-
Carlo Sala authored
-
Marc Cornellà authored
Fixes #9737
-
David Chin authored
-
Marc Cornellà authored
-
Marc Cornellà authored
Fixes missing $USER value in ArchLinux sh (bash)
-
Marc Cornellà authored
-
Ricky Medina authored
Co-authored-by:
Marc Cornellà <hello@mcornella.com>
-
Mathias Neerup authored
Closes #4962
-
- 22 Jan, 2022 2 commits
-
-
Marc Cornellà authored
-
-
- 21 Jan, 2022 1 commit
-
-
kronion authored
-
- 20 Jan, 2022 1 commit
-
-
Billy Mathews authored
Closes #6555
-
- 19 Jan, 2022 4 commits
-
-
Marc Cornellà authored
-
Marc Cornellà authored
-
kronion authored
-
Mike Mattice authored
Co-authored-by:
Mike Mattice <mmattice@reliant.io>
-
- 18 Jan, 2022 4 commits
-
-
Marc Cornellà authored
-
Marco Franssen authored
-
Marc Cornellà authored
-
Carlo Sala authored
-
- 17 Jan, 2022 3 commits
-
-
Marc Cornellà authored
-
Marc Cornellà authored
-
Marc Cornellà authored
-
- 14 Jan, 2022 1 commit
-
-
Mykola Krachkovsky authored
-
- 13 Jan, 2022 4 commits
-
-
Marc Cornellà authored
-
Marc Cornellà authored
Fixes #10587
-
Marc Cornellà authored
-
Marc Cornellà authored
-
- 12 Jan, 2022 1 commit
-
-
Carlo Sala authored
Fixes #10578
-
- 11 Jan, 2022 4 commits
-
-
Marc Cornellà authored
-
Marc Cornellà authored
-
Marc Cornellà authored
The previous check only worked if the user could run `sudo` without typing the password, which is almost none (I checked in Google Cloud Shell so I failed to notice this). This new check works whether the user has no sudo privileges, or if it has, whether they have to type in the password or not. It should really be easier to check if the user doesn't have privilege without having to make them type the password.
-
Marc Cornellà authored
This fixes the error in Google Cloud Shell, where a password prompt appears when running `chsh` but the user (hello) does not have a password. If ran with `sudo`, the `chsh` command happens without a password prompt.
-
- 10 Jan, 2022 3 commits
-
-
Marc Cornellà authored
-
WeZZard authored
-
Marc Cornellà authored
-
- 09 Jan, 2022 2 commits
-
-
Marc Cornellà authored
-
Marc Cornellà authored
-
- 08 Jan, 2022 2 commits
-
-
Joey Territo authored
When generating completions for Cargo, if the Rust sysroot (i.e. `rustc +${${(z)$(rustup default)}[1]} --print sysroot`) contains spaces, Cargo completions will not work because the spaces are not escaped, thus passing two arguments to the "source" command instead of one. The spaces need to be escaped for this to work.
-
Fabian Günter authored
-