In Atom editor I have installed Go plus package for GO autocomplete. After installing this package, Go autocomplete is working fine, but when the file is saved, the Go plus panel appears from the bottom.
How to hide it permanently?
This depends on the level of "hiding" that you desire. In my opinion there are three levels of hiding. All three can be modified by opening Edit --> Preferences --> Packages --> go-plus --> Settings, and then scrolling down to Panel.
The first level is hiding the panel on opening a new file, but it still appears upon saving a file. You can enable this by changing the Panel Display Mode that has a menu selection (the first one) to closed.
The second level is additionally hiding the panel on saving, but it still appears when a file is saved and has issues. You can enable this by changing the Panel Display Mode that has an input text box (the last one) to hidden.
The third level is additionally hiding the panel on saving when there are issues in a file. You can enable this by untoggling the checkbox off for the Focus the go-plus panel on failure option.
With all three of these, you can basically make it so the panel never shows up if that is what you really want. Note that because go-plus is using the Atom-Linter suite of packages behind the scenes, you will still have notifications from go-plus packages showing up in the Linter panel, and would need to disable those in the Linter-Ui-Default --> Settings (such as Hide Panel When Empty, Show Panel, etc.).
Related
The complete field name is not visible in Kibana navigation bar. If I pass my mouse on the field, it shows the full text for e.g. "requestParameter.allocationID". Should I check each and every field by pointing the mouse? The sidebar width can not be changed or adjusted to fit the entire fieldname?
This is an unresolved issue #737 from November 2013. You are not alone requesting this feature. Deeply in the comment section, there is a comment referring to the issue #38646 where the progress can be tracked.
I bet this will be released very soon.
For now, feel free to pick one of possible workarounds:
Place a mouse pointer over a label to display its full content (not comfortable)
Resize it manually using devtools. (right-click and Inspect in Google Chrome)
There was a change in base code of Atom.io, so there is a tab row in all panel. It is still bearable in my file tree view, but I do think it is really annoying to have the tab in linter warning panel too.
Is there a way to get rid of it?
netizen's answer will work, but it will cause a potential problem for you later: if you end up with more than one component in one of your docks, you won't be able to see them, switch between them, close them, or rearrange them.
What you are seeing is that in Atom 1.17, a new UI building block was added, called Docks. You can read more about Docks in the blog post where they were announced, or in the deep dive written by the Nuclide team.
Instead of specific components written to sit in a special place in the window (such as tree-view, which sat on the left edge), now you have Dock areas: left, bottom, and right. Any component can sit in one of them, and more than one component fits into a dock.
This is like having multiple files in the editor window: you need a way to rearrange them, see all of them, and switch between them. Tabs are the answer to this problem.
Some people find it visually annoying to see the tabs when only one tab exists. Atom offers an option (in the tabs package) to change this behavior.
It turns out that this option covers all of the tab bars, not just the tab bar in the file editor.
You can find the option in the settings for the tabs package.
Open Atom preferences
click "Packages"
search for "tabs"
click "Settings" on the "tabs" package
Un-check "Always Show Tab Bar"
As I mentioned above, this will affect both your editor tabs and the tabs in Docks. When only one tab exists, the tab bar is hidden, and it is shown again when more than one tab exists.
Insert this into yous styles.less file:
.atom-dock-inner .bottom .tab-bar { display:none; }
Edit: As the comment below from #dan-lowe points, this solution has important drawbacks. It should be applied as a last resort and only to this version both of Atom editor and linter-ui-default, as the docks API is new and prone to changes.
I have a situation where I need to merge several classes manually. They contain a huge amount of overrides within an 18,000 line CSS file.
I started making some changes to the huge CSS file and I realize that CSS loads the last case of a property so I did this all very carefully. For the most part things worked well. But, I did find one icon that was wrong and one text link that was the wrong font. So I thought, is there a way that I can compare the before and after state of this work precisely. I don't mean visually. But instead like two full text output files of the results of the computed CSS for the entire current page so I can run a compare on them in notepad++
Sorry if this is an ignorant question as I am a self taught web novice.
You can use notepad ++ to compare two files. You will need a compare plugin to be installed in notepad ++. Please follow the steps below:
Install the Compare Plugin
1. Launch Notepad++.
Click the “Plugins” menu, select “Plugin Manager” and click “Show Plugin Manager.” A list of currently available plugins populates the plugin manager screen.
Check the box next to “Compare.”
Click the “Install” button at the bottom of the screen. The Compare plugin will download and install. If an administrator authentication dialog appears, click the “Allow” button.
Using the Notepad++ Compare Plugin
1. Launch Notepad++ and open the two files you wish to run a comparison check on.
Click the “Plugins” menu, select “Compare” and click “Compare.” The plugin will run a comparison check and display the two files side by side, with any differences in the text highlighted.
Reset to the original window configuration and appearance by clicking the “Plugins” menu, selecting “Compare” and clicking “Clear Results.”
For reference click here
I have an application I am developing with Access 2010. In certain circumstances I have to limit the users to a very limited subset of the application. This implies a limited Ribbon - by setting a dbProperties to "AllowAllMenus" to false, and changing the File menu (using a Custom Backstage ribbon).
This blocks most off the holes that would allow the user to get back to full menus, and then have access to data I would rather he didn't.
However, there is a hole in this process. The quick access toolbar as a little drop down arrow on the end of it with a hover of "Customise Toolbar". Using it drops down a menu with "More Commands...". Clicking on that drops you into the same dialog box you get when you chose "Options" from the File Menu (disabling of which was the prime purpose of my Backstage Ribbon change).
I can of course do the following in VBA
DoCmd.ShowToolbar "Ribbon",acToolbarNo
but that hides all the menus and Quick Access Toolbar completely. I don't want that, because I still need to allow the user to set up filters and toggle them on an off from the data they do see.
I can't find any other reference to how to block up this security hole in the applcation. Does anyone have any ideas on how?
Assuming that you already have your custom ribbon, make sure that you have assigned: startFromScratch="true".
However, this will disable not only "More Commands..", but all the other options of QAT dropdown list as well, except "Show Below the Ribbon".
I have been using the Scald module for few months now, with great experience. But there is one thing I haven't quite figured out yet.
When I have Drag'n'Drop enabled for a textarea (with CKEditor) I can drag images into the textarea and it displays in it's original size. If i Right-click the image I get the image properties for the image, but only at CSS level.
I'm trying to figure out how to add an Image Style to the image, so that my 4000x3000 image that I drag into the editor will be scaled down to a nicer 300x200 image where wanted, and therefor save some valuable bandwidth.
I found the answer after a pile of googling and reading through few articles. First and foremost it was the one about installing and configuring Scald. (Please Google, I can't post that many links :( )
I installed the CKEditor module, disabled the Wysiwyg module, downloaded the library into sites/all/libraries/, and finally read this article about contexts with Scald: https://drupal.org/node/2104651.
Bottom line, this is possible, but not easy (as sometimes Scald is), but when you get the hang of it, it's much better than the Media module.
I just struggled with this so thought I'd document how to set up contexts.
This is how you add new contexts which can use an image style formatter as a transcoder using the UI:
Go to /admin/structure/scald and click add context. Choose any name and details, but do check "Make parseable"
On the top of the original page for scald settings click "Contexts" in the upper right for "Image" under "Scald Unified Atom Types"
In the page that loads (/admin/structure/scald/image/contexts) you'll see your new context named. Open the fieldset and change the "Transcoder" from "Passthrough" to one of your image styles, e.g. "Large (image style)"
Now when you right-click on a image atom in a textarea wysiwyg and choose "Edit Atom Properties" you'll get a dialog with a new context to choose from. You can also go the default contexts provided by Scald and change them from "Passthrough" to one of your image styles.
Also, at the moment you also have to apply this change https://drupal.org/node/2046545 to scald.pages.inc or you'll lose your legend as you switch contexts or use the dev version. When 7.x-1.2 is released this will no longer be necessary.
I just ran across this same issue, using WYSIWYG 2.x-dev with CKEditor library 4.3, Scald 1.2. What fixed it was one of these things (sorry can't remember exactly which one):
Both "Scald DnD Integration" and "Scald SAS conversion" enabled in the relevant WYSIWYG profiles
The display settings for your image (at admin/structure/scald/image/display) have atom field set to enabled but image field set to hidden
You want to use the insert image module
https://drupal.org/project/insert
The easiest way to assign image styles to images going into a wysiwyg area