I installed the Atom Commander plugin in Atom on OSX and it works fine with SFTP. When clicking on the 'Option' (not the 'Alt/Cmd' key as stated) I activate the menu and can select options and add an SFTP server. Then a two pane browser is shown but when I click on a file or folder a large empty gray field is shown on the bottom of the screen and when I click again (defocus the Atom Commander) the gray field disappears.
Trying to hide it by the Element Inspector in dev mode had no success as the gray field is beyond the editor workspace.
Very weird behavior and it wastes a considerable portion of the screen.
This only happens with this plugin and no other parts or plugins of Atom.
Do you have the color-picker package installed? If you do then this has been reported back towards the end of 2015 in Atom Commander Issue #12, and was subsequently fixed in Color Picker Issue #143 and released in v2.1.1 of the latter package.
If you don't have color-picker installed then it is possible that another package is causing the problem, I would recommend using the bug-report package to generate a bug report that you paste into a New Issue.
Related
I am working on a .Net Core application and I keep running into this problem where I get all sorts of random issues appearing in the Problems window in VSCode for "__virtual" files. There are no problems in the actual razor page (.cshtml) and everything is working how we would expect. Is there a way in VSCode to mass ignore all problems from __virtual files?
This started to happen to me after the latest update of Visual Studio Code.
My solution was to configure file association for .razor__virtual.html files into text
Open visual studio code
Click Settings icon in the left bottom and click Settings
In the search box, search for Files: Associations (Copy-paste this)
Click [Add Item] button and enter **/*.razor__virtual.html for key, text for value.
It should look like this,
Done!
For some reason, Netbeans IDE 8.2 won't apply any different themes than the original one. Has anyone else had an issue with this? I have applied the new theme and restarted the application many times without success. Thank you.
It's very hard to identify what is wrong since everything in your screenshot looks perfect, and Sublime-Theme works for me using NetBeans 8.2 on Windows 10. See the file with the tab NewServlet.java in the screen shot below.
Note that using Sublime-Theme does not impact everything. For example, the Projects and Navigator panels don't change. Since your screen shot only showed the Options window, and the Start Page doesn't change in the editor either, are you absolutely certain that none of your files in the editor are using Sublime-Theme?
Also, you say that "Netbeans IDE 8.2 won't apply any different themes than the original one", but NetBeans comes bundled with several themes, such as NetBeans and NetBeans 5.5 as shown in the screen shot below. How many options are shown in the profile drop list for you? If you select a different theme from the Profile list and click Apply the rendering of your files in the editor should change immediately. Is that happening?
If so, the problem is probably confined to the installation of Sublime-Theme. Try deleting Sublime-Theme (the button is in the top right corner of your screen shot), and then import the zip file again to see if that fixes the problem. Also, verify that the Sublime-Theme zip file you downloaded can be manually unzipped since it might be a corrupt file.
Another thing to try is using some alternative plugins. Select Tools -> Plugins -> Available Plugins and then install Dark Look and Feel Themes and Darcula LAF for NetBeans. If those don't work either then there is something fundamentally wrong with the installation of NetBeans.
Finally, this article titled The complete guide to tuning the appearance of NetBeans may be helpful.
I use Eclipse Neon under Windows 10.
I installed a plugin (MonjaDB) using Eclipse Market Place. As I didn't find the plugin to be very useful I uninstalled it using Help->About->Installation Details->Installed Software->Uninstall. Sadly, however, this didn't seem to fully remove the plugin.
I now have a small red square on the right hand side of my workspace in the shortcut toolbar. This cannot be removed using the close option. I went so far as to remove my installation of Eclipse and the .eclipse directory in my home area but after a reinstall the square is still there.
Presumably this means that it is somehow associated with the project in my workspace?? Does anyone have any ideas how to remove this annoying square?
EDIT:
I have noticed two things
The MonjaDB perspective is hanging around somehow and
If I press the little red square on the right it opens an empty tab in the tab set to the right (where mylyn sits) with the title of DB Tree but I cannot remove it.
I have added three screen shots
MonjaDb perspective Partly Active
It seems like your current perspective is the one that was uninstalled. Just try opening a new one via the Open Perspective toolbar button that's close to thevred square, and then you can try right-click > Close on the red square.
At least a part of this is intentional...when the implementation class of a view no longer exists we leave the view 'open' but are supposed to show an "Error Part'. The reason to leave it up is to handle cases where a user has installed a new eclipse and opens his old workspace before installing the extensions. If we were to remove the views the user would have to set up their perspectives again once they had installed the extension.
Note that resetting the perspective won't work because the class implementing IPespectiveFactory no longer exists.
Closing the perspective and opening a new, different, one should work. If the perspective you open has visible views that are no longer available you should just close them.
I installed the Eclipse Moonrise UI and the results are great, except a couple things become unreadable for me. Here is an image of what my project explorer window looks like. I have 2 git repositories which have black text, making it very difficult to read on the dark background. The normal files and folders have light text, but when selected, it becomes completely unreadable because the selected item's background is very light. Also my scroll bars are light (unlike what is seen on the front page of the above link).
I am unable to locate where I can adjust these settings.
On the other hand, the Outliner window has light text on the dark background and when selected becomes dark text on a light background. Not the way it is supposed to look with this plugin, but it's fine, I can read it.
I am running Kepler Service Release 2 on windows 7 x64.
Except for scrollbars that are forced by OS theme, try to import the epf file as suggested on project page. The settings contained in that epf will influence the syntax highlighting (foreground/background colors) for code editors but also custom colors for other views (eg. console, git filenames, etc.).
If instead you're using CDT, unfortunately the issues with package explorer and outline file names cannot be solved now, because those colors are hard-coded in that package and requires a fix in CDT bundle for them before.
I have this problem bugging me for a little while now and I didn't find any help on SO or other resources.
In Eclipse Java EE (Version: Indigo Service Release 2 Build id: 20120216-1857), when double clicking a file (a class, or XML or whatever else) in the Package Explorer to open it in the editor, it will open a new tab every time I double click the file, even though the file has been previously opened in another tab. So for example, double clicking 3 times in a row on a single file in the Package Explorer will open 3 tabs in the editor for this single file.
I found some info about how to display search result in a common tab, or how to open a single file in two different editors, but nothing about this problem, I cannot find any setting to disable this annoying behavior.
Anyone got some clues about this problem ?
After putting back the default settings of Eclipse, it seems to be alright now. I will update this post in case the same problem happens later on.