Is there a way to get rid of the tab row in atom editor? - atom-editor

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.

Related

How to precisely test if CSS final computed values have changed anywhere on a page?

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

Can't re-open project files sidebar anymore in Atom Editor

Sorry if this is the wrong place to answer but I found no other community which could help me with this. I accidentally closed the left-sidebar that shows the currently open project and it's files. Not sure what it's called, maybe navigation, folder view, either way, I tried pressing nearly every key combination to no results. I tried searching in the command palette for something that looked like "open project sidebar" but nothing. Now I'm stuck having no idea how to restore my primary navigation means when working with Atom. I tried opening multiple projects but I just get a black screen without the project sidebar, like it was hidden.
Any ideas?
I'm talking about this sidebar:
It is called "Tree-View".
You should be able to enable it via command pallete or ctrl + ,
It depends on your OS. On Mac OS X, it's CMD-\ (Command-Backslash) to toggle it. The option located on the View menu, called Toggle Tree View (the last menu option).

Use of variables like %{buildDir} in QtCreator kit settings in Qt5

In this documentation (under section "Specifying a Custom Executable to Run") I noticed that there is mention of what looks like a variable %{buildDir} in the field "Working directory".
I have struggled for a while now to find documentation for this feature. I would like to know first of all is there documentation for this somewhere?.
Secondary questions:
What other variables are available?
In which fields can they be used?
Can I access variables that I created in my project's .pro file?
Are there any other eval features or is this mechanism limited to variables?
Thanks!
As mentioned in the comments there is a "variables" button... supposedly for use all over the qt environment. However I have only found it available in obscure places that are not very useful!
However, you can at least get the list of vars from these places and use them where you actually need them. To find this, navigate to:
Tools (menu) --> Options --> Environment (tab) --> External Tools
Click "Update Translations..."
Click inside "Working Directory.." and you should see a "AB->" icon in colour to the right.
Click the icon for your list of vars.
You will notice that the style is a little different then %{BuildDir} but I believe the equivalent is %{CurrentProject:BuildPath} - You can see on the second screen shot I have right clicked and it asks you what you want to insert (the variable, or the value of the variable).
Annoyingly I could not figure out how to copy / paste the whole list as it is single line click only... maybe someone more clever can figure that out and we can stick that list in some Qt wiki :o
Here are the screen shots... Notice in screen shot 1 the little icon at the right side of "Working Directory" text-edit box.
In text edit widgets within Qt Creator (v5.14.0 and possibly earlier), there is an icon at the right end. Click on it, and a dialog of all the possibilities comes up. Make sure that the caret is at the proper position in the text edit widget.

Using image styles with Scald dnd (Drupal 7)

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

How can I stop aptana Outline view automatically collapsing?

I'm using aptana to work on a web document with a fair bit of javascript that's organised into functions. I want to be able to easily jump around the functions, so I selected aptana for the document explorer / outline view panel. It works fine, but when I'm typing the document it collapses all by itself, which drives me bananas.
How can I stop it doing this?
Thanks.
Under the little arrow in the top right corner is an option to "Link with Editor". Turn this off and the Outline view should stay as you leave it rather than trying to match what you are doing in the editor.
I tried doing what Sarah suggested and I was unable to get the Outline View to NOT collapse when editing a .js file.
I looked through the documentation and tried different settings within the Outline tab without success. Expand All did expand all of the functions, objects, and variables, but when I edited one of the objects or functions, that one would then collapse in the Outline View. The problem is it would never expand itself even when I moved in to another section of the document.
I would think that after editing a section of the document, the Outline View should update to reflects the change without collapsing. If it does collapse, then it should expand once saved.
It either collapses and expands by itself (link with editor is "on") or only collapses by itself when you change anything in the document (link with editor is "off"). I don't think this behaviour is what most of us, users, would expect. I hope they change it soon. It's one of the very flaws this otherwise great piece of software has.

Resources