rust/x.ps1, branch 1.88.0

use `&` instead of start-process in x.ps1

2023-12-09T14:46:16+00:00

start-process has weird parsing rules and buggy behavior. we've already had to work around them several times, and the workarounds were not complete. i wonder who could have added it HMMMMMM ``` PS C:\Users\jyn\src\rust> git log --reverse -S Start-Process x.ps1 commit 775c3c0493e9a383a7f1c521b06d36f2e3d0d886 Author: Jynn Nelson Date: Sun Jul 31 14:02:31 2022 -0500 Add `x.sh` and `x.ps1` shell scripts ``` the latest broken thing is trailing backslashes: ``` $ x.ps1 t .\tests\ui\error-emitter\ ``` would be transformed into ``` ['t', '.\\tests\\ui\\error-emitter"'] ``` rather than trying to hack around that too, abandon start-process altogether and just use `&`.

x.ps1: remove the check for Python from Windows Store

2023-10-23T05:25:48+00:00

When installing Python from the Windows Store, a copy of `python.exe` is installed inder the Microsoft directory in the user's local AppData directory. Currently, `x.ps1` checks for this file, because by default running `python.exe` opens a link to the Microsoft Store rather than running Python. Once the user installs Python, however, this contains a valid interpreter. Unfortuantely, `x.ps1` can't tell the difference between a legitimate Python install and the stub. Remove the check, as it makes it impossible to use the official version from Microsoft once it has been installed. Signed-off-by: Sean Cross

Don't print "x.ps1"

2023-06-24T19:44:53+00:00

This is left over from adding `Get-Command -syntax`; it's not helpful.

Give a better error on Windows if python isn't installed

2023-06-24T19:44:53+00:00

Before: ``` PS C:\Users\vboxuser\rust> ./x x.ps1 PS C:\Users\vboxuser\rust> ``` After: ``` PS C:\Users\vboxuser\rust> ./x x.ps1 C:\Users\vboxuser\rust\x.ps1 : C:\Users\vboxuser\rust\x.ps1: error: did not find python installed help: consider installing it from https://www.python.org/downloads/windows/ At line:1 char:1 + ./x + ~~~ + CategoryInfo : NotInstalled: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,x.ps1 ``` The existing message from the shell script is already decent and I decided not to change it: ``` $ ./x Python was not found but can be installed from the Microsoft Store: ms-windows-store://pdp/?productid=9NJ46SX7X90P ```

Rollup merge of #111151 - ozkanonur:syntax-check-on-bootstrap-scripts, r=Mark-Simulacrum

2023-05-06T21:32:01+00:00

check bootstrap scripts syntax Fails bootstrapping if `x`/`x.ps1` scripts are not valid. Currently, it keeps executing lines until the invalid one.

check bootstrap scripts syntax

2023-05-03T17:32:39+00:00

Signed-off-by: ozkanonur

Return error code from x.ps1

2023-05-03T17:21:36+00:00

Powershell: Create a `Start-Process` wrapper

2022-12-28T19:41:42+00:00

Powershell: Use `WaitForExit` instead of `-Wait`

2022-12-28T15:41:46+00:00

Add better python discovery

2022-10-31T07:33:24+00:00

`x.ps1` and `x` will now search for python executables like `python3.9` and `python3.10.exe`