Home
last modified time | relevance | path

Searched refs:PowerShell (Results 1 – 25 of 27) sorted by relevance

12

/third_party/rust/crates/clap/clap_complete/tests/
Dpowershell.rs9 clap_complete::shells::PowerShell, in basic()
21 clap_complete::shells::PowerShell, in feature_sample()
33 clap_complete::shells::PowerShell, in special_commands()
45 clap_complete::shells::PowerShell, in quoting()
57 clap_complete::shells::PowerShell, in aliases()
69 clap_complete::shells::PowerShell, in sub_subcommands()
81 clap_complete::shells::PowerShell, in value_hint()
93 clap_complete::shells::PowerShell, in value_terminator()
/third_party/rust/crates/clap/clap_complete/src/shells/
Dshell.rs22 PowerShell, enumerator
56 Shell::PowerShell, in value_variants()
66 Shell::PowerShell => PossibleValue::new("powershell"), in to_possible_value()
78 Shell::PowerShell => shells::PowerShell.file_name(name), in file_name()
88 Shell::PowerShell => shells::PowerShell.generate(cmd, buf), in generate()
136 Some(Shell::PowerShell) in from_env()
152 "powershell" | "powershell_ise" => Some(Shell::PowerShell), in parse_shell_from_path()
Dpowershell.rs11 pub struct PowerShell; struct
13 impl Generator for PowerShell { implementation
Dmod.rs13 pub use powershell::PowerShell;
/third_party/python/Doc/using/
Dvenv-create.inc89 issuing the following PowerShell command:
122 | | PowerShell Core | $ <venv>/bin/Activate.ps1 |
126 | | PowerShell | PS C:\\> <venv>\\Scripts\\Activate.ps1 |
148 PowerShell activation scripts installed under POSIX for PowerShell Core
Dwindows.rst306 Alternatively, it will be available from any Command Prompt or PowerShell
365 ``https://aka.ms/nugetclidl``, for example, using curl or PowerShell. With the
/third_party/mesa3d/.gitlab-ci/windows/
DREADME.md9 only inside that base container. This is open-coded in PowerShell scripts.
36 `*.ps1` scripts for building dockers are using PowerShell 7 to run
DDockerfile_vs11 # Make sure any failure in PowerShell scripts is fatal
/third_party/flutter/skia/third_party/externals/sdl/build-scripts/
Dwinrtbuild.bat8 PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '%PowerShellScriptPath%'";
/third_party/flutter/flutter/
Dflutter_console.bat30 echo Want to run the "flutter" command from any Command Prompt or PowerShell window?
/third_party/flutter/flutter/dev/devicelab/test/
Drunning_processes_test.dart9 test('Parse PowerShell result', () {
/third_party/flutter/flutter/dev/devicelab/lib/framework/
Drunning_processes.dart84 // PowerShell script to get the command line arguments and create time of
108 /// Parses the output of the PowerShell script from [windowsRunningProcesses].
/third_party/node/doc/api/
Dsynopsis.md42 Windows PowerShell:
/third_party/python/PC/
Dstore_info.txt22 To build for sideloading, use these commands in PowerShell:
35 (Note that only the last command requires PowerShell, and the others
/third_party/node/deps/npm/node_modules/debug/
DCHANGELOG.md179 * Readme: Corrected PowerShell environment variable example (#252, @gimre)
195 * Readme: doc fixes for PowerShell (#271 #243, @exoticknight @unreadable)
DREADME.md81 Note that PowerShell uses different syntax to set environment variables.
/third_party/flutter/flutter/bin/
Dflutter.bat105PowerShell.exe -ExecutionPolicy Bypass -Command "Unblock-File -Path '%update_dart_bin%'; & '%updat…
/third_party/node/deps/npm/node_modules/node-gyp/
DREADME.md51 …pm install --global --production windows-build-tools` from an elevated PowerShell or CMD.exe (run …
/third_party/node/
DBUILDING.md614 Alternatively, you can use PowerShell. Run those commands from an elevated
615 PowerShell terminal:
/third_party/rust/crates/clap/
DCHANGELOG.md1557 * Uses the short help tool-tip for PowerShell completion scripts ([ecda22ce](https://github.com/cl…
1862 * **PowerShell Completions:** fixes a bug where powershells completions cant be used if no subcomm…
1867 * **PowerShell Completions:** massively dedups subcommand names in the generate script to make sma…
2189 * **Completions:** adds completion support for PowerShell. ([cff82c88](https://github.com/clap-rs/…
/third_party/mksh/
Dmksh.faq22 <tt>COMMAND.COM</tt>, <tt>CMD.EXE</tt> or PowerShell on other operating
/third_party/python/Doc/whatsnew/
D3.8.rst1404 activating virtual environments under PowerShell Core 6.1.
/third_party/node/deps/npm/
DCHANGELOG.md754 PowerShell ([@ExE-Boss](https://github.com/ExE-Boss))
/third_party/python/Misc/NEWS.d/
D3.8.0a1.rst3112 The Activate.ps1 script from venv works with PowerShell Core 6.1 and is now
/third_party/node/deps/npm/changelogs/
DCHANGELOG-2.md1958 install it with `--global`. This should prevent Windows PowerShell from thinking

12