Please see the figure for the problem. What's is more interesting, is that I copied the two packages directly from git repository of spacemacs, inside which :reg works just well.
Appreciate it if there's any suggestion.
Related
I apologize if this question has been answered somewhere else, but so far I am unable to locate it if it was.
Background:
As many folks have suffered the dreaded blank screen on VS Code, I deployed the recommended fix for --disable-gpu. This fix worked just fine for me and I have been using it ever since.
Issue:
Since this fix has been deployed, I'm unable to view the details page when viewing an Extension. The page/tab just shows up as blank. This happens with any extension, regardless of if I've installed it or not. This in and of itself is not a deal breaker for me, but I was hoping to use the Jupyter Notebook extension, but this seems to be impacting this as well.
If anyone has any guidance, please let me know.
Screenshot showing lack of details
I was able to get this corrected by creating a .bat file that I use to open VS Code. The code file was set up like the following:
cd C:\Program Files\Microsoft VS Code\
Code.exe --disable-software-rasterizer --disable-gpu --no-sandbox
I'm new to zsh, just switched over from fish. I'm trying to get autocomplete working so it displays argument/flag options for commands upon pressing tab.
Currently this works, but it only appears to work for built in commands. For example, it works for ls, grep, git, etc. but does not work for programs I have added myself. For example, fd-find, exa, and nvm all do not work.
For nvm, I have enabled the nvm plugin using Oh My Zsh. I know the plugin is working in general, because nvm itself is working (and it wasn't before enabling the plugin).
For fd-find, I see the auto-completion file in /usr/share/zsh/vendor-completions/_fd
For exa, I manually downloaded and placed the autocompletion file in /usr/local/share/zsh/site-functions/_exa as instructed by the site.
All 3 of these programs do not show me the typical arguments/flags autocomplete menu the way built in commands do. I'm not sure what is wrong.
I echoed the fpath environment variable to make sure /usr/local/share/zsh/site-functions was in there. It is, along with /usr/local/share/zsh/site-functions/
When I run which nvm, I get:
_nvm () {
# undefined
builtin autoload -XUz
}
Which is actually what I get for all of _nvm, _exa, _fd.
Not sure what else to try.
Any suggestions for how to get autocomplete working properly?
Other info: I'm on a System76 Darter Pro laptop running Pop!_OS.
I found a fix that worked for me. After searching through zsh issues related to autocomplete on github, this solution worked for me. Credit was given to the original source of the solution on stackexchange.
The solution was simply to remove all zcompdump files:
rm ~/.zcompdump*
After running the above command, autocomplete works and expands out the possible flags/arguments for non-builtin programs!
I recently started using the sshfs extension by Kelvin Schoofs in VS code and it's a huge time saver. However, my other extentions don't work when I'm editing in the remote workspace.
For example, I have the HTML snippets extension installed and it works when editing a local file. But when I try to use it in a remote workspace it dosen't. Same goes for my other extensions.
I was wondering if anyone had run into this issue and somehow got their other extension to work. I've done some googling around for solutions but haven't found anything that works.
I would also be open to using a different ssh extension if this isn't an issue for the suggested extension.
Thanks in advance for any help or insight you guys can provide.
I just cannot find any actions to work of the latex-workshop extension in VS Code, though it worked well yesterday.
When I tried to find the actions (using Ctrl+Shift+P), it shows a choice of LaTex Workshop: All Actions. However, after click on it, an error occurs as command 'latex-workshop.actions' not found, and nothing happens. And I can't use any command by shortcut keys.
I tried to reload and reinstall the extension, but they don't help.
Does anyone know what's happening here?
I had the same problem, and followed some suggestion in this GitHub issue.
Simply reinstalling the plugin won't work, but I fixed like this:
Uninstall extension
Close VS Code (Make sure all processes are shut down, maybe restart your machine)
Open Code and reinstall the extension
For me, what solved the problem (August 2021) was to revert to an earlier version - the problem was in 8.20.2, I reverted to 8.19.2. Just click on the extension to show its menu screen and hit the drop-down arrow of the "Uninstall" button.
I solved the issue by uninstalling the extension and deleting the folder
/.vscode-oss/extensions/james-yu.latex-workshop-8.14.0/
The name may vary across distributions
The first time I used git bash, backspace was working fine. Then I installed Perl and didn't use git bash for a few days.
When I use backspace in git bash now it doesn't work correctly.
For example, trying to remove the second s and everything after it in ussers:
Now when I use the backspace this happens:
Can anyone help?
I had this same problem today after switching to mintty with a fresh version of git. In my case, it was an old .bashrc file I'd been carrying around for many years with the line export TERM=ansi. After removing that and starting a new bash, everything works again.
More generally, to debug, I was suspicious of all the dot-config stuff in my home directory--so I moved things like .bash_profile, .bashrc, .inputrc, etc. into a temporary directory where they wouldn't be read by bash. Then, I started bash and saw that it worked. I mention it because, if it isn't specifically the TERM issue I had, you might be able to debug using the same technique.
Not sure if this is the same issue.. But I ran into the same after upgrading git
This helped me.. Just enter TERM=XTERM in the bash
I got this from an issue log in github..
screenshot
Just in case people run into a capitalization issue please type TERM=xterm-256color directly into git bash and hit enter. This fixed my issue.
Right click on the menu/title bar of git bash, select options, click on terminal from the options on the left, under the 'type' dropdown, select 'xterm', then apply and save.
Now open a new git bash and it should work :D