I'm using Mac OSX with Mountain Lion and I'm running MacVim 7.3 snapshot 66, I just installed it with brew install macvim but it doesn't starts with its toolbar and I really want it, what should i do to set it up so each time I open MacVim it starts with its toolbar?
Put set guioptions+=T in your .vimrc. Note that set guioptions=T clears all other gui options.
Related
I have KDE neon and recently it was upgraded to the latest version, 5.23. The problem I have that System Monitor Indicator widgets no longer working, they are just empty, like this:
When I open settings for that widget and go to Sensors page, there are no sensors available
I have the same issue on at least 2 different installations. Strangely, I can't find any informaiton about it anywhere. Is there any fix available?
Check if you have ksystemstats installed by running it in Konsole.
ksystemstats
If it appears not found or not installed, try to install it.
sudo apt install ksystemstats
then try again running in konsole (you will see that it initializes)
ksystemstats
and finally open System Monitor.
PhpStorm was running fine till this morning but suddenly it has stopped working. Since the IDE was not loading at all I decided to reinstall it.
The first step was I used the following command to remove the application
$ sudo rm -R ~/Phpstorm*
Then I downloaded version 2016.1 from https://confluence.jetbrains.com/display/PhpStorm/Previous+PhpStorm+Releases and followed the instruction as shown in this article:
https://www.jetbrains.com/help/phpstorm/install-and-set-up-product.html
But neither any launcher icon was created nor I am able to find PhpStorm in application search.
Running $ ./phpstorm.sh in terminal window gives me
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=350m;
support was removed in 8.0
The above message is familiar to me because it used to come every time I run PhpStorm from terminal.
But after reinstall, the message is appearing but the application does not start.
Edit
Content of /usr/share/applications/phpstorm.desktop
[Desktop Entry]
Version=5.0.4
Name=JetBrains PhpStorm
# Only KDE 4 seems to use GenericName, so we reuse the KDE strings.
# From Ubuntu's language-pack-kde-XX-base packages, version 9.04-20090413.
GenericName=Text Editor
Exec=phpstorm
Terminal=false
Icon=/opt/PhpStorm-145.1616.3/bin/webide.png
Type=Application
Categories=TextEditor;IDE;Development
X-Ayatana-Desktop-Shortcuts=NewWindow
[NewWindow Shortcut Group]
Name=New Window
Exec=phpstorm
TargetEnvironment=Unity
Reference article:
https://blog.shaharia.com/create-phpstorm-luncher-and-terminal-command-on-ubuntu
when running ubuntu cli in a tab (a chrome tab in chrome os) using crouton, i can't press control w to search in the nano text editor. It triggers the close window command instead for chrome. How can I disable this? With a GUI installed for Ubuntu, I can run the program full screen and get total keyboard command capture. Is this impossible when running in a Chrome tab? Is there any way to get the cli out of the chrome tab?
Chrome OS Download 'Crouton integration Extension' from Google Store
Chrome OS Download crouton from bottom link of Francois Beaufort
Chrome OS Open CROSH ...type crt + alt + t
Chrome OS type shell
Chrome OS type: sudo sh ~/Downloads/crouton -r trusty -t unity,extension
Chrome OS type: sudo startunity
Info & Links https://plus.google.com/+FrancoisBeaufort/posts/JDVkXALPcNq
I saw this two videos
http://www.youtube.com/watch?v=kVSo4buDAEE
http://www.youtube.com/watch?v=x6qe_kVaBpg
and I wanted to try google workspaces on my linux desktop
I followed these instructions: https://plus.google.com/+GoogleChromeDevelopers/posts/644qQuBKZeL
And this detailed tutorial: http://devcoma.blogspot.it/2013/01/how-to-enable-workspace-experiment-on.html
But the "File system folders in Sources Panel" won't show up
I tried with "Chromium Version 25.0.1364.160 Ubuntu 13.04 (25.0.1364.160-0ubuntu3)"
and also with "Chrome Version 29.0.1530.2 dev"
(I installed this dev version from http://www.chromium.org/getting-involved/dev-channel)
Anybody had any luck whith this?
I found the way to test it.
These are the steps I had to follow
Install a ppa with a more recent chromium version, from here:
http://www.webupd8.org/2012/09/new-chromium-stable-and-development.html
sudo add-apt-repository ppa:a-v-shkop/chromium-dev
sudo apt-get update
sudo apt-get install chromium-browser
as of today it install Version 27.0.1453.6 Ubuntu 13.04 (191032)
Open the browser and in the url bar enter chrome://flags/
enabled "Enable Developer Tools experiments."
restart the browser
open the web page you want to debug using workspaces
press F12 to open the dev tool
press F1 to open the settings panel
go to Experiments and check "File system folders in Sources Panel"
restart browser
in your file system, add a file named .allow-devtools-edit
cd
touch .allow-devtools-edit
once again, press F12, F1, and select Workspace, add folder, and add the root of your project
to map your web site to your file system, right click on any js file and select 'Map to network resource', then choose the corresponding file
and that's it, in the Workspace section of your Settings, you will see that a mapping has been added, with something like
'http://localhost:9000' -> '/home/opensas/dev/apps/my_js_project'
The good news is that it seems that with the latest Google Chrome development version everything works out of the box, no need to mess around with development or experimental features.
This question is a duplicate for this one
In the Dev-channel version things were changed a bit.
So you don't need to enable devtools experiments
and don't need to manually create .allow-devtools-edit
I was unable to locate the "Mono for Android SDKs" preferences option when following the Mono for Android for Mac installation instructions.
troubleshooting steps I've tried:
After completing installation of the evaluation copy of Mono for Android for Mac I restarted MonoDevelop (version 2.4.2) and still didn't have the option available. I rebooted my Mac but that did not trigger MonoDevelop to expose the option either. I tried reinstalling the Mono for Android addin also.
Anyone struggled with the same problem? Let me know what you tried. Thanks!
I suppose it's funny to answer my own question, but on further troubleshooting steps...
I installed the lastest MonoDevelop beta and the preferences option appeared.