- 11 9月, 2019 31 次提交
-
-
由 Alex Ross 提交于
Part of #80375
-
由 Benjamin Pasero 提交于
-
由 João Moreno 提交于
-
由 Andre Weinand 提交于
-
由 isidor 提交于
-
由 Alex Ross 提交于
* First pass at set view title * Change to get/set instead of setTitle and get the name of the view from the extension contributions
-
由 Benjamin Pasero 提交于
-
由 Martin Aeschlimann 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
* Custom Editor exploration For #77131 Adds a prototype of custom editors contributed by extensions. This change does the following: - Introduces a new contribution point for the declarative parts of a custom editor - Adds API for registering a webview editor provider. This lets VS Code decided when to create a webview editor - Adds an `openWith` command that lets you select which editor to use to open a resource from the file explorer - Adds a setting that lets you say that you always want to use a custom editor for a given file extension - Hooks up auto opening of a custom editor when opening a file from quick open or explorer - Adds a new extension that contributes a custom image preview for png and jpg files Still needs a lot of UX work and testing. We are also going to explore a more generic "open handler" based approach for supporting custom editors Revert * Re-use existing custom editor if one is already open * Don't re-create custom editor webview when clicking on already visible custom editor * Move customEditorInput to own file * First draft of serializing custom editor inputs * Use glob patterns instead of simple file extensions for matching custom resoruces for custom editors * Add descriptions * Try opening standard editor while prompting for custom editor * Make sure we hide image status on dispose * Make sure we restore editor group too * Use glob patterns for workbench.editor.custom * Allow users to configure custom editors for additional file types * Use filename glob instead of glob on full resource path * Adding placeholder for prompt open with * Add enableByDefault setting for editor contributions * Enable custom editors by default and add `discretion` enum Changes `enableByDefault` boolean to a `discretion` enum. This should give more flexibility if we want other options (such as forcing a given custom editor to always be used even if there are other default ones) * Allow custom editors to specify both a scheme and filenamePattern they are active for * Rework custom editor setting * Don't allow custom editors to be enabled for all resources by a config mistake * Replace built-in image editor with one from extension * Adding reopen with command * Improve comment * Remove commented code * Localize package.json and remove image * Remove extra lib setting from tsconfig
-
由 Daniel Imms 提交于
Diff: https://github.com/xtermjs/xterm.js/compare/9169108...6211dcd Changes: - Releasing v4 - Doc updates - Fix sourcemaps in demo
-
由 Matt Bierner 提交于
Use the document that contains the md link as the resource for getting config, not the target document
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Salvador Cabrera Lozano 提交于
* Fix for #26659. Clicking on a local file link will open up the editor on a separate editor group (new or reuse existing one). * Fix for #26659: Add way to open Markdown links in a different editor group Adding "markdown.editor.openMarkdownLinks" setting to specify where links to markdown files should open (current editor group by default).
-
由 Konstantin Solomatov 提交于
-
由 Miguel Solorio 提交于
-
由 Alexandru Dima 提交于
Web: Load onigasm lazy
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Daniel Imms 提交于
Refactor smoke UI automation into separate package
-
由 Daniel Imms 提交于
-
由 Rob Lourens 提交于
so it writes to the code-oss logs folder and doesn't inherit the insiders log folder
-
由 Rob Lourens 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
- 10 9月, 2019 9 次提交
-
-
由 Joao Moreno 提交于
This reverts commit 492def26.
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
Fixes #79967
-
由 Matt Bierner 提交于
-
由 Pine Wu 提交于
-
由 Sergio Schvezov 提交于
* snap: add assets verbatim Providing the desktop files in snap/gui will have snapcraft copy over those assets into the snaps meta/gui verbatim. Addtionally, add a leading ${SNAP} to the Icon entry which was also moved to snap/gui for the "package" to have an icon by default (which is important when sideloading). Signed-off-by: NSergio Schvezov <sergio.schvezov@canonical.com> * escape * fix snapcraft.yml * use @@EXEC@@ in desktop files * fix bad path * fix snap desktop file
-
由 Benjamin Pasero 提交于
-
由 Martin Aeschlimann 提交于
-
由 Martin Aeschlimann 提交于
-