Serious question: why would you want to make two clicks where you only need one?
customizable packages are not working properly
This is especially annoying when you single click on a file and want to search, the file tab is closed…
By default, single-clicking on a file will open a pending tab. This is for quickly scanning through multiple files without cluttering up your tabs. Do you want to disable this?
Workspaces… does not really exist such as “project” you can create a project but the moment you close the editor you loose your folders “imported”. You can reopen the “workspace” folder again but then it will show you all the folders… totally inconsistent.
There are a number of packages that exist to make it easy to store and recall specific projects, like
The whole idea of the packages corrupts the configurability, you never know if it is a “core” package and you should configure something in the package, or it is found under the settings, or maybe the config is under a custom package… I don’t know why you can not have a Config tab where all the installed packages are/can subsrice with their config and show the options for example.
It’s easy to look up which packages are core packages, through the
Settings -> Packages view. From that same view, you can change the settings for individual packages by clicking on the card for that package (you can tell if packages have their own settings because they have a button with a gear icon, which goes to the same place as the package card).
Building… usually opens a windows with text output. Have you ever tried to copy text from that windows? Any text selection on any window (except the text editor) makes the selection crazy and selects EVERYTHING visible in the editor…
Building what? Atom doesn’t have the capability to build any code, so you have to use a package for that. Each package controls its own way of doing things, determined by the author. Which package are you using?
Some features can be accessed via settings, some feature can be accessed via menus, some with shortcuts, rest with the “command line”.
These aren’t so muddled as you make them out to be. Configurations and packages are managed through
Settings. The default menus contain application-level commands and standard text operations–what most people expect to find in a text editor’s menu–plus a menu for all packages. You can change this if you want. Most built-in commands have keybindings associated, but not all. Atom has no command line by default. What I think you mean is the Command Palette.
Yes we use a command line under a graphical tool. This is such a hardcoded linux thinking in 2017 that i just dropped my mind.
You are perfectly free to bind any command in Atom to any keybinding, menu item, or toolbar button you desire.
And that was the time I noticed the huge amount of “eclipse” like packages you can install, seems people try to eclipsify the atom, probably for a reason (and not just the reson that they got used to eclipse).
Search for other editors, like vim and Sublime, and you’ll see that there’s nothing unique about Eclipse in this sense. There are Atom packages for introducing features and behaviors from a bunch of different origins. It’s not because people actually want to be using those other programs, but because Atom is so flexible that it allows people to make it behave like their preferred tools.