I'm a newbie to code::blocks. I have just installed it on my ubuntu desktop and made some changes to its settings such as change default font size , change caret's color, and some more things in settings -> editor. But when I close code::blocks I see message on a pop-up window the perspective code blocks default has changed do you want to save it?I was not able to save my perspective irrespective of clicking yes in the dialogue box.
I also uninstalled and re-installed it but the problem still persists. I searched all over the internet but can't find solution to my problem. I think I've loosen my mind now. Please someone help me.
It is just a permission issue. Type chmod -R 777 ./.config/codeblocks/ in terminal and you are all set :)
Related
Simply trying to open a README.md file from GitHub in Jupyter Notebook. Greeted with the raw text, no options, and no preview every time. I also note the loss of any of the 'standard' toolbar options at the top (such as kernel).
Screenshot of current situation
Tried just about everything the internet could think of (including a reinstall, or at least what I think to be a reinstall, of notebook), and still no luck. I also have noticed that the executed preview does not work in VSCode on my current machine, or laptop. No idea what is wrong, but clearly, I am the common factor haha. Thanks in advance for any input.
am not getting any error or anything, but VS code by default always switches to a Dark+ (default dark), even if in my system setting I have selected Light theme (I have a MacBook Air). This is too much frustrating and I also uninstalled and installed VS Code 2-3 times and am unable to change the behaviour. Please let me know if you need any additional info with this question, I will provide it.
An additional point on this problem, when I press CMD +, to open setting, and under appearance, I change the Color Theme, it let me change. And then when I open a file (a python file suppose) or just switch to an opened file it changes back to Dark+ (default dark). I don't know how to solve this behaviour. Please help.
I think VS Code is just doesn't follow the system theme (I observed this in my Windows 10 machine). Also cmd+, is not the place to change VS code theme.
You can try CmdP and enter >color theme to select a theme.
VS code doesn't follow system theme, do cmd + K, then let go of K while holding cmd and press T. Or you can cmd + K THEN cmd + T. There you will get a menu where you will get your color options.
I reset workbench settings to default and then added the following to settings.json and it solved my problem.
"workbench.colorTheme": "GitHub Dark Default",
"window.autoDetectColorScheme": true,
"workbench.preferredDarkColorTheme": "GitHub Dark Default",
"workbench.preferredLightColorTheme": "GitHub Light Default",
I managed to get the Powerline fonts working on my Windows 10 pc to use in WSL, particularly in the VS Code terminal window so I can use the Agnoster oh-my-zsh terminal theme. I set it all up and everything works - cool.
BUT when I shutdown my pc and restart it, the font no longer works in VS Code.
However, it does still work in the ubuntu window. See ↓
https://i.imgur.com/SCyDrFM.png -- Sorry, I don't have enough rep to post images :(
I noticed it is not installed in the settings > font window
But it is installed in the control panel fonts window.
Current workaround
I can get the font to work again if I reinstall the font, at which point Windows will prompt me that The font is already installed, do I want to reinstall?. Click yes.
At which point the font will appear in the fonts settings (Add fonts) window.
What is going wrong with the font installation? Reinstalling the font after every boot seems tedious... I suppose I can get a script to automate that on startup but I really want to get to the root cause.
EDIT
So I just found the fix - had to right click on the .ttf file and 🛡️Install for all users.
I don't know why installing it as the local user didn't work but hey ¯\_(ツ)_/¯
I found the answer to my own question...
Have to right click on the .ttf file and 🛡️Install for all users.
It seems that if the font is not listed in the Settings > Personalization > Fonts window, VS Code will not find it. Installing for all users makes the font persist there after reboot.
You can install the Powerline Fonts with the following command:
sudo apt-get install fonts-powerline
And starting VS Code from your WSL prompt with command code .
I want to make iTerm2 as my default terminal on macOS,
I open iTerm2 and hit to make iTerm default Term
But it's not working!
And I go to default terminal preferences
But after open it I see this
(Open iTerm Build version 3.3.7)
Menu: iTerm2 > Make iTerm2 Default Term
It sounds like you need to rebuild your macOS' LaunchServices.
To do this, download OnyX and choose the version based on your current macOS version.
The option that you need is in the red box, and I'd suggest that you UNCHECK anything that you don't need or don't know; otherwise, you might end up with deleting data that you might need:
After that, you can try again with the built-in Make iTerm2 Default Term option in iTerm2 (if this option is greyed out for you, click option + the iTerm menu button to re-enable it again).
There are ways to do this through the command line without downloading third-party apps, but I trust OnyX enough to hand it the job.
However, if you decide to do it from the command line, make sure you type the command that corresponds to your current macOS version. More on that here.
Hope this helps :)
Use this location instead:
/Applications/iTerm.app/Contents/MacOS/iTerm2
but note that it will not solve your issue completely. Termianal will start anyway, but this time, it will run iTerm2 - as you instructed it to do.
One thing you can do is find the file that opens a terminal (in my case it was metro opening in a React Native app). Find the file in your finder, right click on it, choose get info, then expand the Open With tab. There you should find a dropdown menu on what to open those kind of files with. The default is terminal, but choose iTerm2 and click on change all.
For example, in my situation I had to find launchPackager.command file under node_modules/react-native/scripts/. Do the above with that file and it will make iTerm your default terminal after clicking change all.
From where do you want to open the terminal? I was facing the same problem as you when I wanted to open the external terminal from Visual Studio Code.
I solved it by going to Code > Preferences > Settings. Look for terminal in the search bar and setting /Applications/iTerm.app in Terminal > External for your operating system.
I need to debug some JavaScript an' I use Chrome dev tools. I'm a newby in JavaScript (just started to learn a couple of days ago), an' at work I could set breakpoints via the Resources pane. But at home for some reason I can't do this: after the click no breakpoint appeares.
I have Chrome version: 26.0.1410.64 m.
What could be the case?
clicking on the De-Obfuscate Source button (i.e. {}) solved this issue for me.
I'm a fool! haha! breakpoints are set in the Source pane )))
It's been a while, but in version 33.0.1750.146, but my problem was that I was on the Sources pane (I'd call this a tab; it's one of the items at the very top of the window), but I was on the Content scripts tab (on the left hand side). I needed to switch to the Sources tab.
To be clear, there are two sets of Sources tabs; one is within the other.
UPDATE 2016-01-07: Now I'm on 47.0.2526.106. The only thing that worked for me today was to close DevTools and re-open. It was a little finicky. It worked once, then stopped, and I had to close the DevTools and re-open again. I saw #johntrepreneur's answer about closing the browser, but unfortunately I have too many tabs open on too many workspaces, so that's too much of a pain, so I didn't try that, although I have to assume that would work.
Other solutions didn't work for me. Had to close and restart browser to be able to set breakpoints again.
This also happens when there is a JS error in your code.
Some sort of weird built in function in windows 10 i think because I did press a few buttons by accident. Some of my keys even stopped working in certain areas of visual studio. F.e the letter "c" stopped working in the find window.
Mine did this and no solution worked, i pressed alt, windows key and function key a few times and my problem went away.
Fixed as follows: For me, the issue stems from having set up Chrome to interact with operating system files. If you set this up, then the fact is evident from a green dot by the file name. At some point, I could not set a breakpoint in a recently edited file. I fixed this by disconnecting the interaction, as follows: When viewing "sources", above the code, there were some file names listed. Clicking the [x] to make the particular filename go away gave a caution message; I proceeded without saving. After that, I was able to set breakpoints for that file.
I also had this problem. However, once I closed the popup message in my browser, suddenly all my breakpoints that I set in that time appeared. Mental note: Don't set breakpoints while your app is showing a popup.
I couldn't find any direct fix for this problem.
It seems that chrome keeps settings of your site stored somewhere whatever you do to clean it. (I tried removing the folder from workspace, closing et reopening chrome etc... and nothing worked).
A workaround is to change your site's url to make chrome consider it a new site