it shows "You must run VS code with admin privileges in order to enable Neon Dreams.".It doesn't work even after running vs-code as administrator.
The error is caused by the new version of VSCode, the extension normally change the workbench files of electron-browser but electron-browser was removed in the commit https://github.com/microsoft/vscode/tree/f4f1b04d872a2b94d9a5105a1eefb81a213c07f2 and it has been replaced by electron-sandbox.
So you have 2 choices :
You can go back to previous version of VSCode (1.69 June version) by downloading it here https://code.visualstudio.com/updates/v1_69 and then run VSCode as Administrator and enable neon dreams again
Or
You can stay in 1.70 and modify manually the extension :
Go to "C:/Users/YourUsername/.vscode/extensions/robbowen.synthwave... or wherever your vscode extensions are stored
Go to src/ and open extension.js
You will have to replace all the "electron-browser" with "electron-sandbox" so
const htmlFile =
base +
(isWin
? "\\electron-browser\\workbench\\workbench.html"
: "/electron-browser/workbench/workbench.html");
const templateFile =
base +
(isWin
? "\\electron-browser\\workbench\\neondreams.js"
: "/electron-browser/workbench/neondreams.js");
on line 34 become
const htmlFile =
base +
(isWin
? "\\electron-sandbox\\workbench\\workbench.html"
: "/electron-sandbox/workbench/workbench.html");
const templateFile =
base +
(isWin
? "\\electron-sandbox\\workbench\\neondreams.js"
: "/electron-sandbox/workbench/neondreams.js");
and same operation at line 149 on
var htmlFile =
base +
(isWin
? "\\electron-browser\\workbench\\workbench.html"
: "/electron-browser/workbench/workbench.html");
Save extension.js, close VSCode, open VSCode as Administrator and Enable Neon Dreams again.
Hope it helps !
Following the advise of S.Mollet to find and replace electron-browser with electron-sandbox worked; only difference I was on mac, but principal was same.
Find vs code extension files, mine were in ~/.vscode/exentions/robb...
and then to run vs code with admin I ran sudo code --user-data-dir="~/.vscode-root"
and then in vs code press ⌘-p and select enable dreams.
I was losing so much productivity while my font wasnt glowing, smh.
Related
I have a problem on my nvim LSP.
according to mason plugin the pyright is downloaded and I on other IDE the lsp works great.
when i open python file with neovim it didn't recognized import and basic functions.
someone can handle this situation?
maybe it's because Lspinfo tell me that it didn't get the python root directory?import don't auto complete pythonpyright is downloaded via masonLSPInfo description
on other languages it works so don't really understand the problem
Same as me, at the moment I solved like this (it happens in some languages for me too):
local status_ok, mason = pcall(require, "mason")
if not status_ok then
return
end
local status_masonlsp_ok, mason_lspconfig = pcall(require, "mason-lspconfig")
if not status_masonlsp_ok then
return
end
local servers = {
"sumneko_lua",
"rust_analyzer",
"tailwindcss",
"bashls",
"pyright",
-- "csharp_ls",
"html",
"omnisharp",
"gopls",
}
mason.setup(settings)
mason_lspconfig.setup({
ensure_installed = servers,
automatic_installation = true,
})
So when I open nvim they are installed automatically.
I've recently tried to install the QDK via the VSCode extension in my Windows 10 Desktop and VSCode wasn't able to find the Microsoft libraries even after I was able to execute the code by the dotnet run command on the terminal. The code was the sample project code described in the create new project part of the tutorial. I also didn't have .NET SDK so I installed it but it seems to be working fine. In computers I got problems all the code, all related to not finding the namespaces.
namespace QuantumRNG {
open Microsoft.Quantum.Canon;
open Microsoft.Quantum.Intrinsic;
open Microsoft.Quantum.Measurement;
open Microsoft.Quantum.Math;
open Microsoft.Quantum.Convert;
operation GenerateRandomBit() : Result {
using (q = Qubit()) {
H(q);
return MResetZ(q);
}
}
operation SampleRandomNumberInRange(max : Int) : Int {
mutable output = 0;
repeat {
mutable bits = new Result[0];
for (idxBit in 1..BitSizeI(max)) {
set bits += [GenerateRandomBit()];
}
set output = ResultArrayAsInt(bits);
} until (output <= max);
return output;
}
#EntryPoint()
operation SampleRandomNumber() : Int {
let max = 50;
Message($"Sampling a random number between 0 and {max}: ");
return SampleRandomNumberInRange(max);
}
}
Do you see any error messages in the output console?
To see the output console select "View: Toggle Output" (Ctrl + Shift + U) and select "Q# Language Extension" from the drop down list.
If the drop down list doesn't show "Q# Language Extension" then it probably means that the language-server that gets downloaded on first run is still downloading, so give it a minute or so (depending on your internet connection).
I think I also had the same problem. The .Net SDk which you have downloaded automatically creates a path in the environment variable by the name "%USERPROFILE%.dotnet\tools" so delete this and add "C:\Program Files\dotnet\sdk" or copy the path of dotnet SDK from the drive where you have installed dotnet and create a new environment variable under user variable. This might solve your namespace problem.
Problem
"liveSass.command.watchMySass not found" and "Extension host terminated unexpectedly” in vs code on windows 10 while using live-sass-compiler extension.
Failed attempts:
manually deleted the extension from the .vscode folder and reinstalled it as per #219
[Antivirus/defender] tried excluding the extensionHostProcess.js file at C:\Users\ (user file name e.g- hp...etc) \AppData\Local\Programs\Microsoft VSCode\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js as per #94858
Disabled all extensions and tried running as per #94807
Tried restoring quarantined files from antivirus/defender
Tried all the aforementioned steps again after reinstalling vs code.
downloaded vscode - January 2020 (version 1.42) build as per https://stackoverflow.com/a/61133333/11045279
Error log
c:\Users\ADITYA\.vscode\extensions\ritwickdey.live-sass-3.0.0\node_modules\sasslib\sass.sync.js:61
var Module=typeof Module!=="undefined"?Module:{};var moduleOverrides={};var key;
for(key in Module){if(Module.hasOwnProperty(key)){moduleOverrides[key]=Module[key]}}
Module["arguments"]=[];
Module["thisProgram"]="./this.program";
Module["quit"]=(function(status,toThrow){throw toThrow});Module["preRun"]=[];Module["postRun"]=[];
var ENVIRONMENT_IS_WEB=false;var ENVIRONMENT_IS_WORKER=false;var ENVIRONMENT_IS_NODE=false;
var ENVIRONMENT_IS_SHELL=false;
if(Module["ENVIRONMENT"]){if(Module["ENVIRONMENT"]==="WEB"){ENVIRONMENT_IS_WEB=true}
else if(Module["ENVIRONMENT"]==="WORKER"){ENVIRONMENT_IS_WORKER=true}
else if(Module["ENVIRONMENT"]==="NODE"){ENVIRONMENT_IS_NODE=true}
else if(Module["ENVIRONMENT"]==="SHELL"){ENVIRONMENT_IS_SHELL=true}
else{throw new Error("Module['ENVIRONMENT'] value is not valid. must be one
of: WEB|WORKER|NODE|SHELL.")}}else{ENVIRONMENT_IS_WEB=typeof
window==="object";ENVIRONMENT_IS_WORKER=typeof importSc
Error: Import "node_modules/bootstrap/scss/bootstrap" could not be resolved.
at File.load (D:\Projects\vscode-ext-color-highlight\node_modules\file-importer\index.js:130:1)
at D:\Projects\vscode-ext-color-highlight\node_modules\file-importer\index.js:136:1
at FSReqCallback.oncomplete (fs.js:165:21)
abstractExtensionService.ts:155 Extension host terminated unexpectedly. Code: 7 Signal: null
Thanks.
Here's the fix so you don't have the nightmare I've been having.
Uninstall live sass and close VScode.
For Windows, type the following into file explorer:
%USERPROFILE%.vscode\extensions
Then delete the folder for live sass. Should be called something like:
ritwickdey.live-sass-3.0.0
Open VScode, reinstall live sass.
Done
The problem that's not about installation problem, that's need to open VS Code editor and then create new file with SCSS format. For example, style.scss, and please wait for second and then you see watch sass in below of vscode.
I'm trying to get vim set up as an IDE for Perl. I'm using generic, text-based vim, not gvim.
I installed the "vim-perl" addon at https://github.com/vim-perl/vim-perl using the vim addon manager per the suggestion of someone else. At least I think it's installed but I don't notice any difference in how the file is processed.
First I installed the vim-addon-manager with Debian's package manager. Then I put the following code in my .vimrc file and reloaded it:
" put this line first in ~/.vimrc
set nocompatible | filetype indent plugin on | syn on
fun! SetupVAM()
let c = get(g:, 'vim_addon_manager', {})
let g:vim_addon_manager = c
let c.plugin_root_dir = expand('$HOME', 1) . '/.vim/vim-addons'
" Force your ~/.vim/after directory to be last in &rtp always:
" let g:vim_addon_manager.rtp_list_hook = 'vam#ForceUsersAfterDirectoriesToBeLast'
" most used options you may want to use:
" let c.log_to_buf = 1
" let c.auto_install = 0
let &rtp.=(empty(&rtp)?'':',').c.plugin_root_dir.'/vim-addon-manager'
if !isdirectory(c.plugin_root_dir.'/vim-addon-manager/autoload')
execute '!git clone --depth=1 git://github.com/MarcWeber/vim-addon-manager '
\ shellescape(c.plugin_root_dir.'/vim-addon-manager', 1)
endif
" This provides the VAMActivate command, you could be passing plugin names, too
call vam#ActivateAddons([], {})
endfun
all SetupVAM()
" ACTIVATING PLUGINS
" OPTION 1, use VAMActivate
VAMActivate github:vim-perl/vim-perl
" OPTION 2: use call vam#ActivateAddons
"call vam#ActivateAddons([vim-perl], {})
use <c-x><c-p> to complete plugin names
" OPTION 3: Create a file ~/.vim-srcipts putting a PLUGIN_NAME into each line
" See lazy loading plugins section in README.md for details
" call vam#Scripts('~/.vim-scripts', {'tag_regex': '.*'})
So what exactly is the vim-perl addon supposed to do for me? I can't find any good documenation anywhere.
At least parts of vim-perl are incorporated in the factory-default configuration of Vim; cp. $VIMRUNTIME/ftplugin/perl.vim and $VIMRUNTIME/syntax/perl.vim. By installing (and regularly upgrading) the plugin, you'll get:
a newer version of the scripts, with potential enhancements and bug fixes
some additional functionality (f.e. there's a syntax/mason.vim that's not yet in Vim itself)
If you regularly edit non-trivial Perl scripts, or use latest language features, installing vim-perl is worth contemplating. If you're just a casual programmer, I would wait until a real need arises.
I'm trying to use Powershell DSC's Package resource to install an exe... Perforce's P4V to be specific. Here's my code:
Configuration PerforceMachine
{
Node "SERVERNAME"
{
Package P4V
{
Ensure = "Present"
Name = "Perforce Visual Components"
Path = "\\nas\share\p4vinst64.exe"
ProductId = ''
Arguments = "/S /V/qn" # args for silent mode
LogPath = "$env:ProgramData\p4v_install.log"
}
}
}
When running this, this is the error Powershell gives me:
PowerShell provider MSFT_PackageResource failed to execute Set-TargetResource functionality with error message: The return code 1619 was not expected. Configuration is likely not
correct
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : SERVERNAME
According to documentation, return code 1619 means the MSI package couldn't be opened. However, when I manually log in to the machine and run "\\nas\share\p4vinst64.exe /S /V/qn", the install works flawlessly.
Does anyone know why this is failing? Alternately, can anyone tell me how to troubleshoot this? I pasted all the error information I got from the terminal, my log file (p4v_install.log) is a 0 byte file, and there are no events in the event viewer. I don't know how to troubleshoot it any further!
EDIT: I should note that I also tried using the File resource to copy the file locally, and then install it from there. Sadly, that met with the same result.
Daniel over at the Powershell.org forums was able to figure this out for me.
The P4V InstallShield setup wrapper puts the MSI file into wrong path if you execute as LocalSystem.
I’ve managed to develop a Configuration that works, see below. The key is the /b switch here which puts the MSI file into a defined location. I’ve added ALLUSERS=1 to get the shortcuts visible to all users and REBOOT=ReallySuppress to avoid a sudden restart (which will happen otherwise).
Configuration PerforceMachine
{
Package P4V
{
Ensure = "Present"
Name = "Perforce Visual Components"
Path = "C:\My\p4vinst64.exe"
ProductId = ''
Arguments = '/b"C:\Windows\Temp\PerforceClient" /S /V"/qn ALLUSERS=1 REBOOT=ReallySuppress"' # args for silent mode
}
}
Well, what happens here is that the package gets installed (not tested with p4vinst64.exe yet! So, not sure why it says pack cannot be opened as the error) but since you did not specify a ProductID value, the verification at the end of install fails. That is the error you are seeing. The Package resource is no good for installing .exe packages or even MSIs with no ProductID represented as a GUID.
You can use the WindowsProcess resource instead.