I have several RaspberryPIs as remotes in VSCode via SSH.
In some of them at some point the "search in files" feature has stoped working.
It is only searching inside the opened files.
[EDIT]
After further investigation I found out that on all the Raspberrys where the error occurs I can not install ripgrep. (E: Unable to locate package ripgrep)
As VSCode is using ripgrep for searching this may be the cause but what is the solution then?
[EDIT2]
I built and installed ripgrep manuall. No success.
But maybe it is related to the debian version being 9.X
As several people have reported the same problem but the cirumstances are always different I tried the following solutions:
Make sure the "book" icon is not checked (some users had that problem)
Make sure it is not related to path lenght. Just one folder in ~ with file a.py and b.py (some user had that problem)
Made sure there is nothing in the .gitignore file (some user had that problem)
Made a new folder not inside a samba shared folder (some user had that problem)
Deactivated all exensions on the remote
Deactivated all non SSH related extensions on the PC
Compared the setting on the broken remote to a working one. They are completely the same.
deleted the .vscode-server folder on the remote to force VSCode to install it again
Related
I am trying to run the first example of zguide (zeromq). The project has two files, client and server, and I am doing this using vscode ssh remote on a RHEL7 machine.
Here is the structure of the folder and how it looks like in VSCode explorer:
ZEROMQ[SSH:remote_machine]
|_.vscode
|_tasks.json
|_c_cpp_properties.json
|_client.cpp
|_server.cpp
Once in a while I receive this warning:
Unable to watch for file changes in this large workspace folder. Please follow the instructions link to resolve this issue.
The instructions are of course telling me to increase the limit size which I don't think is the issue here with such a small project.
So, any ideas what's happening and how to resolve this?
I recently opted to start using Visual Studio Code. I want to connect to a remote server and edit files directly on the server. FTP-Simple seems like a great solution. But I am having a hard time understanding some basics about the program.
If I make a connection to a server, does FTP-Simple download all the actual files to my hard drive?
Also, I was able to make a connection, but in one of the directories there should be a sub-directory and it's missing. What am I doing wrong?
Can someone point me to some good documentation for this extension such as video(s), etc.
If I make a connection to a server, does FTP-Simple download all the
actual files to my hard drive?
Yes, It download all to your hard drive. you can find an address like below:
C:\Users\your user name\AppData\Roaming\Code\User\ftp-simple\remote-workspace-temp\cbc1ad9ed60f12ec861052806d7833db\httpdocs
for opening a directory in VSCode you can press F1 type ftp-config then click ftp-config:Open
and click on target directory you want to open for more information use this
2 years later and I'm having the same problem. I have already uninstalled ftp simple as well as VSC with no effect.
The plugin just doesn't download all the files on the FTP. It worked the first time I installed it for 2-3 weeks and then suddenly stopped being in sync with the FTP server.
There is a folder called "code" on mac in Library/Application Support where most of VSC data is saved, but deleting this didn't have an effect either. Perhaps it works for someone else, as this is apparently necessary to fully deinstall VSC.
I'd pay for good plugin that just allows to work remotely on ftp files!!
So after using unity's asset server for quite a while I decided I would try Perforce as it seemed like a good alternative and a viable way to work with people without the pro license. I am using Windows version of Unity 5 and a Linux install of P4V.
The problem I am getting is this error
The Client path
//ProjectName
maps to this folder
~\Perforce\ProjectName
which is not a parent directory of the projects root:
C:\Users\...\ProjectName`
After searching the internet I found nothing as to what exactly this means so I figured I would ask.
Two pieces of configuration data aren't matching up:
The client workspace root, which in your case appears to be set to "~\Perforce\ProjectName", and
The project root, which in your case appears to be set to "C:\Users...\ProjectName"
P4Connect is expecting the "project root" (C:\Users...) to be "under" the "workspace root" (~\Perforce...)
I suspect the problem is in the use of the Unix-y tilde (~) character to mean your home directory. In general, Windows software doesn't expand the tilde character automatically; that is a Unix-y behavior.
Try replacing the ~ with the full path to your project root.
And make sure that your project root is located inside of your workspace root.
everyone. I've been struggling with this for a long time now. So I started an Android application using the Android Development Tools (ADT) on my computer and now I want to move this project into a repository on my Ubuntu Desktop 12.04 server, so I can work on it with a friend without constantly overwriting one another. I zipped the project on my computer, extracted and imported it on the server (using Eclipse on both ends) and created a git repository on the server by right clicking and going to Team -> Share Project
Now when I try to clone it from my (Windows) computer, I can't seem to connect properly no matter what protocol I use, be it git, SSH, FTP or HTTP. I want to try HTTP since it's the easiest (or am I totally wrong?)
The server has a static IP address, namely 192.168.1.42 (it also has a WAN address which I'll give my friend once this gets sorted out), and the project, along with the .git folder inside it, are under var/www/git/Eclipse Workspace/Musica
I can browse to that folder on Chrome from my computer, and to the hidden .git folder as well, but whenever I try to connect on Eclipse it says:
[address]/info/refs?service=git-upload-pack not found
And I can't seem to get around that. I've also tried using SSH, but the first time I connect it asks me to add a key, then fails loading the files, and every attempt thereafter fails to connect in the first place. FTP isn't cooperating either, nor is git nor file.
I'm out of ideas. I would really appreciate any guidance. Thanks!
I try to install/run emacs on a Win7 64-bit machine after using it for years on a WinXP 32-bit machine and run into a problem I do not find any help for in the documentation or on the web.
Symptom:
when starting runemacs.exe for the first time it creates the file
*C:\Users\USER\My Documents.emacs.d*
as one would expect (for my administrator as well as for my user account)
and comes up operational
from the second start of runemacs.exe it breaks in the startup phase,
displaying the scratch buffer, ringing the warning bell and displaying in
bottom line the error:
File exists: c:/Users/USER/My Documents/.emacs.d/
buffer messages specifies:
make-directory: File exists: c:/Users/USER/My Documents/.emacs.d/
if runemacs was called with a file to open, i.e. because the file type was
associated with it and the file was opened to edit, the file is not open
and ready to be edited, but a file can be opened via the menu File->Open File...
but my configurations in the file
C:\Users\USER\My Documents.emacs
are not loaded
My goal:
I want to regain the way I used emacs on the old WinXP 32-bit system:
click a file associated with emacs, get it opened and ready for editing, get my configurations in .emacs loaded automatically, i.e. work with emacs seamlessly.
Checks done and failed attempts to fix this:
I tried the following newly downloded versions of emacs
emacs-23.4-bin-i386.zip
emacs-23.2-bin-i386.zip (the one I used on the WinXP)
I had the emacs directory containing the directory stucture (bin, etc, ...)
located at:
C:\Program Files (x86)\emacs-23.4\ (my preferred location)
C:\Emacs\emacs-23.4\
in the download directory, where I originally extracted it
My HOME variable points to:
C:\Users\USER\My Documents (default)
C:\Users\USER\My Documents\ (tried)
My PATH variable contains:
C:\Program Files (x86)\emacs-23.4\bin (default)
or the corresponding other locations which I tried
The ownership and permissions of my C:\Users\USER\My Documents.emacs.d
look OK:
owner is the USER (administrator or standard_user)
permissions grant Full Control
Having originally installed emacs to *C:\Program Files (x86)\emacs-23.4*
using the administrator account, I also tried to use user account installation
instead (to check for some non- obvious parameter/access permission not set
right if the admin account is uses for setup)
For the runemacs.exe executable I manually set the compatibility settings to
Windows XP (Service Pack 3)
default setting after unpacking: no compatibility setting enabled
I removed the private configuration file C:\Users\USER\My Documents.emacs
(inherited from my XP installation) to check whether it produces a screw-up
All that did not change a bit of the described symptom, i.e. either I screwed up
in testing the above and missed a particular setting which should work, or I am looking into the wrong direction...
It is still unclear to me whether this has anything to do with:
W7 64-bit vs. XP 32-bit
environmental parameter screw-up
emacs configuration (.emacs, .emacs.d) screw-up
general stupidity (of me ;-)
... and why is it has emacs a problem with it in the first place, that the .emacs.d directory already exists... That should be the standard case...
Any help and wisdom much appreciated.
First of all, nice question. The details and listing of what you've already tried is helpful.
Some points:
Don't have spaces in key paths (Emacs, and %HOME%). Generally, things work
fine. But when things break it's often hard to debug and trace back to the
fact that some package author didn't take spaces properly into account.
Set a HOME environment variable to your %USER_PROFILE%. Make it
%USER_PROFILE%/home if you must, but I use the former.
Start by running emacs without any customization.
runemacs -Q
When that works, add your customizations one at a time.
n.b. This answer is not relevant to the original question (which was about Windows), but may be useful to Unix users searching for this error message
You will get this error also if emacs does not have the correct permissions on the .emacs.d directory.
Check it
ls -ld $HOME/.emacs.d
And make sure the user you are running under has rwx permissions!
I got similar problems when I installed the new version of emacs on a new installation of the ubuntu 12.10. I get the problem fixed by chmod 777 .emacs.d, that is, as the previous post pointed out, the emacs does not have the access right to .emacs.d directory. Hope this help.