Vscode: Extension Installation (Retains your extensions) #526
Replies: 3 comments 6 replies
-
My problem now is I don't know how to modify the extensions to set it to $Fav-Theme |
Beta Was this translation helpful? Give feedback.
-
yup, the themepatch should be updated and ignore the vscode extension part ... just get it as an optional input parameter... in
so here in the 3rd column, its the extension id (is always unique) and the theme name (as an extension can have multiple themes in it) and the script will install the |
Beta Was this translation helpful? Give feedback.
-
Will use the script on themev2 branch and will adapt the syntax Concerns:
I will merge themev2 to the theme patcher PR to avoid conflicts. |
Beta Was this translation helpful? Give feedback.
-
Based on this #478
This is an attempt to utilize *.vsix packages used by vscode.
To avoid overwriting on themes I suggest using a compressed version of the extensions WITH Fav-Theme.vsix INCLUDED.
(instructions at the bottom).
By this we can uncompress the Code_Extensions.tar.gz outside the
~/.vscode/
or as a temporary directorythen inside that folder, we can
recursively search for *.vsix files and add it to ``` code --install-extension $Path-to-vsix --force.
example:
By doing this we won't overwrite other extensions.
Downsides: Some re-compilations of the extensions to add the *.vsix files
Compiling instructions:
We need a package called "vsce" to aquire the *.vsix of an extension, OR we can download the extension on web or on vscode app with *.vsix file included.
you can get vsce in the AUR
paru -Sy vsce
Modifying the extensions package label into Fav-Theme.
This is used by vscode to know what is the theme name, so you should edit the extension theme name to be the same to your $Fav_Theme
Example: from "Hack The Box" to "Hackthebox"
On Json it should be at
contributes : themes: label "Fav-Theme"
BUT This might not work so I don't know how ahha HELP me What Part should we edit to override it.
I don't know the right way haha
Generate *vsix : cd to the extension directory with package.json located run
vsce package
Test: Test if the theme name of vscode changes after you change your theme, you can check this inside
code ~/.config/Code/User/setting.json
If your $Fav_Theme name is correctly displayed in "workbench.colorTheme" the theme of the vscode should take effect.Archiving:
Compress it to
Code_$Fav_Theme.tar.gz
. The script also supports either "tar.gz" or "tar. xz ".I can start Writing this and share the progress to get some advice.
@prasanthrangan
@T-Crypt
@ALL
Beta Was this translation helpful? Give feedback.
All reactions