I have tons of an IDE errors, where the file is red - even there is "No problems found" in the files.
Update: I realised I had moved some files around just before upgrading. And as the right answer states it, the red files are unversioned under Git(see answer from artspb)
This happened after upgrading to Goland 2021.2 - MacOS Big Sur
I tried to "Invalidate caches..." under files.
Do you know how to solve this?
The red files are unversioned under Git, the green files are staged, and so on (see help).
Related
I am trying to follow this tutorial. I am running on MacOS Catalina, 10.15.3 , on a 13" Macbook pro from 2016. I downloaded the latest release from here for Mac. I unzipped the file, and moved the zig executable (but not the rest of the contents of the folder) to usr/local/bin so I could call it from anywhere. Now, regardless of where I run it, I can call zig version and get the output 0.6.0+352976ed2 as expected. However, whenever I try something like zig run main.zig or zig build main.zig it just freezes and does nothing.
Now the tutorial does say that it doesn't support zig 0.6.0. But I was assuming that this would still work, and the tutorial was referring more to things like the way to print being changed when it said it doesn't support 0.6.0. Obviously this could be an incorrect assumption, but I don't know why this wouldn't work. And as zig is young, has a shortage of getting started tutorials so I don't know where else to look.
I have gotten zig 0.6.0 to work with homebrew before, but as I am potentially looking at contributing or trying experimental branches of the compiler down the line, I want to be able to run an arbitrary zig executable.
I was able to fix my problem. First I removed zig from usr/local/bin, and any other files associated with the original download. Then instead of downloading the master release, I downloaded the 0.6.0 release for mac. I unzipped it. I tried compiling with it directly from there, and it worked. However when I moved it to usr/local/bin it gave me the error,
Unable to find zig lib directory
so clearly the executable needed to be with the rest of the folder's contents, where I replaced the executable.
I created a new directory in my home directory that I named tools. I moved the unzipped folder (called zig-macos-x86_64-0.6.0) into the tools directory. Then (from my home directory) I created a symlink to the binary in my bin using this command.
ln -s tools/zig-macos-x86_64-0.6.0/zig ../../usr/local/bin/zig
I quit and restarted terminal. Now zig version produces 0.6.0 and when compiling the program main.zig,
const std = #import("std");
pub fn main() void {
std.debug.warn("Hello, {}!\n", .{"World"});
}
using the command zig run main.zig I get the proper output of
Hello, World!
I experienced the same problem as described in this post:
not possible to set the "R home directory path" in Bluesky Statistics
But I was asked to open a new question for my case.
The Problem:
When I start the newly installed BlueSky Statistics program the following error message appears:
Error: Cannot Launch BlueSky Statistics! Please make sure:
R_HOME configuration variable is pointing to the correct version of R.
But setting the R_HOME path manually, (to the R Version that came with BlueSky Statistics) even in system variables does not make BlueSky Statistics work. (I took care that the path is set with correct "/" ).
My Setup:
Windows 10 Pro
64bit
What I have tried:
I tried all solutions in the mentioned post, but none of them worked.
I deleted all other R versions and their remaining files from my hard disk and tried different versions of BlueSky Statistics.
I always deleted the BlueSky folder in the Roaming folder in between every try.
I installed the newest BlueSky-Statistics-Open-Source-x64-v6.30.7341.34565.exe
and even the one reported in the other thread to be working anyways, version x64-v6.10.7107.24021, does not work for me either.
Possible Solution:
The other thread mentioned a missing dll file belonging to .net.
If someone could post a link to this particualte version of the dll or the .net download, I would be happy to try if that works.
I highly appreciate your help.
Thank you!
The missing dll file is already in the newest BlueSky-Statistics-Open-Source-x64-v6.30.7341.34565.exe. Please try the following
Try this, please rename the "R-core" to say "R-core2" under HKEY_CURRENT_USER\SOFTWARE\
And now launch the BlueSky Statistics application.
If you still see the issue rename the other "R-core" as well, under HKEY_LOCAL_MACHINE\SOFTWARE\
And now launch the BlueSky Statistics application.
I'm having serious issues with Codelight. It has been working for days now, maybe even weeks but after today when I took my project to school to work on it there something happened. My workspace is in a onedrive folder so that I can work on it wherever I am. I have reinstalled codelight and reinstalled MinGW and set it up according to my school's instructions but right now I can't build anything at all (see attached image). I have been looking at other threads but none of them have helped so far. Error
What do you think happened?
Edit: I seem to have fixed the issue. When you let codelite search for a compiler, as it does the first time you launch it, you mess up the directories of things completely. So for example the directory for the C compiler should be $(CodeLiteDir)/tools/gcc-arm/bin/arm-none-eabi-gcc.exe instead of C:\MinGW or wherever it may be installed. Also, we use a patched version of codelite with 'added debugging support' for the md407 so you really don't want to update codelite. There were more issues, for example the C compiler options for my project, so when I built the project it complained about all sorts of things and the cursor wouldn't show up so debugging was impossible, but I managed to fix that too.
In conclusion: this was not fun to fix and codelite is sensitive.
I use Dev-C++ I got similiar 'Mingw32-make.exe' errors. When installing Mingw you will notice there is another directory 'c:\Mingw32\MSYS\1.0\bin'. Within MSYS this directory is global and it has some very important binary files like its own 'make.exe' file. 'Mingw32-make.exe' uses files from this directory. Because the IDE will not know about this directory you will need to include this in your system/environment path because outside of MSYS this directory is not global and 'ming32-make.exe' will not be able to access those binary files.
Regardless of your compiler if your 'make' is Mingw32 that path must be set.
This is not a big problem but it's bothering me. I've installed it in Program Files (x86), already found many old solutions which didn't work for me. I can't install it in another location. I've tried to change the ico to a different one located in a path without spaces, but it didn't work.
Git CMD icon works fine (but I don't like this terminal), the problem persists only with GitBash icon
Can someone help?
Sometimes it could be purely because of the shortcut referring to a previous installation which no longer exists. Check properties by right-clicking on git bash terminal's taskbar icon.
If that's the case
Delete the shortcut or
Replace the path with the current installation directory.
The icon was missing in older versions (2.10: see issue 870)
In your case, make sure to install the latest 64-bits version (in Program Files, not Program Files (x86))
That would be: Git-2.15.0-64-bit.exe.
Update Oct. 2022: this is still working correctly.
I am using the most recent version of R (3.3.2), running in the most recent version of RStudio (1.0.136) on MacOS Sierra (10.12.3). I am running into an issue in which my working directory corresponds, and is stuck on, the directory that contains the .RMD file I currently have open in RStudio. Upon opening the file, the working directory is correctly set to the directory holding the .Rproj file. When I go to load in a file with a path relative to that directory, however, I get an error that there is no such file in the current working directory, and the error returns the location of the .RMD file as that working directory.
The working directory, however (using getwd()) still reads where the working directory is supposed to be, and no matter where I try to set it, I still get the same error message when I try to read in a file. Notably, I do NOT get an error message that the working directory cannot be changed--R tells me that the working directory has been changed, and that directory is allegedly the current working directory...but it's not.
I have tried fully (as far as I am aware) uninstalling R and R studio and reinstalling them, to no avail. Does anyone have a solution? This is frustrating the heck out of me right now, since I have to revise all the relative paths in the notebooks that I have defined to do my work in the interim.
Extra information in case it's relevant: I restored from a Time Machine backup that I suspect may have been corrupted somehow; some contents of my Applications folder were missing that I had to move over manually. Could this be causing the issue? Are there other system files that R depends on when interacting with the filesystem that I might look to? I'm trying to avoid doing a clean OS install or a piecemeal rebuilding of my files, since I don't know if that's actually the issue.
Thanks in advance!
This is a known feature/bug of RStudio notebooks (Working Directory about halfway down). Notebooks are executed in the same directory as the file. As #Simon Jackson noted, you can change this using knitr::opts_knit$set(root.dir = normalizePath()).