atom-editor

I am using Atom for first time. Sublime has a great functionality which consists in: You open a file, you just see the content and don't change anything. Then when you open a new file, as you haven't change anything in the last one, then the new file will take the place of the last one. Did you get it ? is there a way to do that with Atom ? This is implemented as "Preview Tabs" in the bundled "tabs" package in Atom. Go to Settings > Packages > search for "tabs" > click its "Settings" button. Scroll down to tick the "Use Preview Tabs" checkbox. Since Atom 1.6 this behavior is built in Atom

I have begun using the Atom editor with the atom-typescript package on an existing project, and I am encountering this warning. Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option to remove this warning. I cannot seem to figure out how to do this. I tried adding "experimentalDecorators": true to the compilerOptions in ~/.atom/packages/atom-typescript/lib/tsconfig.json but this did not help. What can I do to get rid of the warning? In order to configure a particular project's TypeScript compiler settings, you

I would like to try Kite , which is concept of artificial intelligence helping developers with hints about useful functions or expressions that he or she is currently writing. I have downloaded the Kite Atom plugin from GitHub. However, as I am new to GitHub's Atom Editor I don't know how to install this plugin into editor. As this plugin isn't available from the Atom Package Manager repository you will need to link this manually: Clone the Repository. Change to the plugins\atom directory. Run the following command: apm link kite I've created a short animation to show you me doing this on my

Is it possible to have themes run based on the type of document? For example, I'd like to have one theme for .js, .html, another for .md files. This is no longer the correct answer, please see the other answer for a package that allows you to do what the question asked. I tried to delete this answer, but can‘t do it, since it‘s the accepted answer at the moment. No, this is currently not possible. Atom uses two themes: The UI Theme determines the overall layout of the editor, including tabs, the tree view and and all other visible areas - is this really what you want? The Syntax Theme

My problem is one I found many other answers too but none worked for me. The code and "server" are both localhost. Edit : tried using port 9001 instead as suggested in some answers + tried if Visual Studio Code worked, but the strange thing is: it breaks on exceptions in VS Code but still not on breakpoints. The connection seems to work: My setup Software Windows 10 Pro x64 MAMP (non pro) running port 81 atom php-debug package xdebug-2.4.1-7.0-vc14.dll extention the code to be debugged is written inside the Laravel framework Configs PHP info xdebug part ( full ) xdebug xdebug support enabled

I am working on react-native application for which I am using Atom IDE. I am getting an error on opening Atom I installed babel-cli and babel-preset-flow with npm command. npm install --save-dev babel-cli babel-preset-flow Now when I restart Atom then it shows same warning to me "Flow was not found when attempting to start". Can anyone help me how to fix it. I have followed this https://medium.com/react-native-training/getting-started-with-react-native-and-flow-d40f55746809 flow server is working well but how I add flow to atom so I can get rid from this https://i.stack.imgur.com/7jJVI.png If

Does anyone know if there is a plugin/option for hiding or grouping autogenerated files in Atom? The files I want hidden/grouped is what the typescript compiler auto generates ( .js and .map.js files). Visual Studio style grouping would be best, if possible My typescript file file.ts which generates file.js file.map.js file.js is interesting to read once in a while, but in general its autogenerated and I shouldn't care about it. So letting file.ts be a virtual folder like - file.ts - file.js - file.map.js would be the ideal solution. Plain hiding is fine. (hiding .js files in general is not a