winget-cli

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 5f2d19ed4a8e8dd0b895a051f279fe658c97cb27
parent d68a1a69346e7ca16a5d07eef38a2c93172eb991
Author: Sarah <sarah@sarahlean.com>
Date:   Wed,  9 Jun 2021 15:29:09 +0100

Broken Image Paths Fixed (#1140)

* Update export.md

update image path

* update image path

* Update features.md

* update image path

* update image path
Diffstat:
Mdoc/windows/package-manager/package/repository.md | 4++--
Mdoc/windows/package-manager/winget/export.md | 4++--
Mdoc/windows/package-manager/winget/features.md | 2+-
Mdoc/windows/package-manager/winget/import.md | 4++--
Mdoc/windows/package-manager/winget/index.md | 4++--
Mdoc/windows/package-manager/winget/install.md | 2+-
Mdoc/windows/package-manager/winget/list.md | 6+++---
Mdoc/windows/package-manager/winget/search.md | 2+-
Mdoc/windows/package-manager/winget/settings.md | 2+-
Mdoc/windows/package-manager/winget/show.md | 2+-
Mdoc/windows/package-manager/winget/source.md | 2+-
Mdoc/windows/package-manager/winget/uninstall.md | 8++++----
Mdoc/windows/package-manager/winget/upgrade.md | 4++--
13 files changed, 23 insertions(+), 23 deletions(-)

diff --git a/doc/windows/package-manager/package/repository.md b/doc/windows/package-manager/package/repository.md @@ -46,7 +46,7 @@ If your validation fails, use the errors to locate the line number and make a co Next, create a fork of the repository and clone it. 1. Go to [https://github.com/microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) in your browser and click **Fork**. - ![picture of fork](images\fork.png) + ![picture of fork](images/fork.png) 2. From a command line environment such as the Windows Command Prompt or PowerShell, use the following command to clone your fork. ```CMD @@ -96,7 +96,7 @@ You're now ready to push your new manifest to the remote repository. After you push your changes, return to [https://github.com/microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) and create a **pull request** to merge your fork or branch to the main branch. -![picture of pull request tab](images\pull-request.png) +![picture of pull request tab](images/pull-request.png) ## Submission process diff --git a/doc/windows/package-manager/winget/export.md b/doc/windows/package-manager/winget/export.md @@ -20,7 +20,7 @@ The **export** command is often used to create a file that you can share with ot `winget export [-o] <output> [<options>]` -![export](images\export.png) +![export](images/export.png) ## Arguments @@ -57,6 +57,6 @@ Note: matching an application depends on metadata in the manifest from a configu In the example below, you will see warnings for _reSearch_ and _Angry Birds_. -![export](images\export-command.png) +![export](images/export-command.png) Once the export is complete, you can edit the resulting JSON file in your favorite editor. You can remove apps you do not wish to import in the future. diff --git a/doc/windows/package-manager/winget/features.md b/doc/windows/package-manager/winget/features.md @@ -20,7 +20,7 @@ You can find the latest up to date information features on the [experimental fea `winget features` -![features command](images\features.png) +![features command](images/features.png) Notice above that the status of each feature is listed. If the feature is **disabled** you will not be able to use it. If the feature is **enabled** you will notice that the command will be available to you through winget. diff --git a/doc/windows/package-manager/winget/import.md b/doc/windows/package-manager/winget/import.md @@ -18,7 +18,7 @@ The **import** command is often used to share your developer environment or buil `winget import [-i] <import-file> [<options>]` -![import](images\import.png) +![import](images/import.png) ## Arguments @@ -51,6 +51,6 @@ The JSON file includes the following hierarchy: When the Windows Package Manager imports the JSON file, it attempts to install the specified applications in a serial fashion. If the application is not available or the application is already installed, it will notify the user of that case. -![import](images\import-command.png) +![import](images/import-command.png) You will notice in the example above, the Microsoft.WindowsTerminal was already installed. Therefore the import command skipped passed the installation. diff --git a/doc/windows/package-manager/winget/index.md b/doc/windows/package-manager/winget/index.md @@ -43,10 +43,10 @@ One of the most common usage scenarios is to search for and install a favorite t 1. To [search](search.md) for a tool, type `winget search <appname>`. 2. After you have confirmed that the tool you want is available, you can [install](install.md) the tool by typing `winget install <appname>`. The **winget** tool will launch the installer and install the application on your PC. - ![winget commandline](images\install.png) + ![winget commandline](images/install.png) 3. In addition to install and search, **winget** provides a number of other commands that enable you to [show details](show.md) on applications, [change sources](source.md), and [validate packages](validate.md). To get a complete list of commands, type: `winget --help`. - ![winget help](images\help.png) + ![winget help](images/help.png) ### Commands diff --git a/doc/windows/package-manager/winget/install.md b/doc/windows/package-manager/winget/install.md @@ -18,7 +18,7 @@ The **install** command requires that you specify the exact string to install. I `winget install [[-q] \<query>] [\<options>]` -![search command](images\install.png) +![search command](images/install.png) ## Arguments diff --git a/doc/windows/package-manager/winget/list.md b/doc/windows/package-manager/winget/list.md @@ -20,7 +20,7 @@ The **list** command also supports filters which can be used to limit your list `winget list [[-q] \<query>] [\<options>]` -![list help command](images\list.png) +![list help command](images/list.png) ## Arguments @@ -68,7 +68,7 @@ The following example limits the output of list to 12 apps. winget list -n 12 ``` -![list output command](images\list-count.png) +![list output command](images/list-count.png) ## List with Update @@ -76,7 +76,7 @@ As stated above, the **list** command allows you to see what apps you have insta In the image below, you will notice the preview version of Terminal has an update available. -![list output command](images\list-update.png) +![list output command](images/list-update.png) The **list** command will show not only the update version available, but the source that the update is available from. diff --git a/doc/windows/package-manager/winget/search.md b/doc/windows/package-manager/winget/search.md @@ -18,7 +18,7 @@ The **search** command can show all applications available, or it can be filtere `winget search [[-q] \<query>] [\<options>]` -![Screenshot of the Windows Power Shell window displaying the results of the winget search.](images\search.png) +![Screenshot of the Windows Power Shell window displaying the results of the winget search.](images/search.png) ## Arguments diff --git a/doc/windows/package-manager/winget/settings.md b/doc/windows/package-manager/winget/settings.md @@ -20,7 +20,7 @@ The **settings** command will launch your default MD editor. Windows by default Launch your default JSON editing tool: `winget settings` -![Screenshot of the Windows Package Manager Settings.](images\settings.png) +![Screenshot of the Windows Package Manager Settings.](images/settings.png) When you launch the settings for the first time, there will be no settings specified. At the top of the JSON we provide a [link](https://aka.ms/winget-settings) where you can discover the latest experimental features and settings. diff --git a/doc/windows/package-manager/winget/show.md b/doc/windows/package-manager/winget/show.md @@ -18,7 +18,7 @@ The **show** command only shows metadata that was submitted with the application `winget show [[-q] \<query>] [\<options>]` -![show command](images\show.png) +![show command](images/show.png) ## Arguments diff --git a/doc/windows/package-manager/winget/source.md b/doc/windows/package-manager/winget/source.md @@ -21,7 +21,7 @@ A source provides the data for you to discover and install applications. Only ad `winget source \<sub command> \<options>` -![Source image](images\source.png) +![Source image](images/source.png) ## Arguments diff --git a/doc/windows/package-manager/winget/uninstall.md b/doc/windows/package-manager/winget/uninstall.md @@ -18,7 +18,7 @@ The **uninstall** command requires that you specify the exact string to uninstal `winget uninstall [[-q] \<query>] [\<options>]` -![uninstall command](images\uninstall.png) +![uninstall command](images/uninstall.png) ## Arguments @@ -48,7 +48,7 @@ The options allow you to customize the uninstall experience to meet your needs. Once you have successfully identified the application intended to uninstall, winget will execute the uninstall command. In the example below, the **name** 'orca' and the **id** was passed in. -![uninstall command](images\uninstall-execute.png) +![uninstall command](images/uninstall-execute.png) ### Example queries @@ -69,12 +69,12 @@ winget uninstall --id "{24559D0F-481C-F3BE-8DD0-D908923A38F8}" If the query provided to **winget** does not result in a single application to uninstall, then **winget** will display multiple results. You can then use additional filters to refine the search for a correct application. -![uninstall command](images\uninstall-multiple.png) +![uninstall command](images/uninstall-multiple.png) ## Uninstalling apps not installed with Windows Package Manager As mentioned in [**list**](.\list.md), the **winget list** command will display more than just apps installed with the **winget**. Therefore you can use these commands to quickly and easily remove apps from your PC. In this example, **list** was used to find the application, and then the **id** was passed in as part of uninstall. -![uninstall with list command](images\uninstall-with-list.png) +![uninstall with list command](images/uninstall-with-list.png) diff --git a/doc/windows/package-manager/winget/upgrade.md b/doc/windows/package-manager/winget/upgrade.md @@ -18,7 +18,7 @@ The **upgrade** command requires that you specify the exact string to upgrade. I `winget upgrade [[-q] \<query>] [\<options>]` -![search command](images\upgrade.png) +![search command](images/upgrade.png) ## Arguments @@ -75,7 +75,7 @@ It is common to use the [**list**](.\list.md) command to identify apps in need o In the example below you will see [**list**](.\list.md) identifies that an update is available for Microsoft.WindowsTerminalPreview, and then the user uses **upgrade** to update the application. -![search command](images\upgrade.gif) +![search command](images/upgrade.gif) ## **upgrade** --all