The difference I have noticed is a small one, probably insignificant to most folks. To me, the most striking aspect of this is the possibility that Atom is incapable of not affecting what happens on cmd-c (OSX) I am very curious about the mechanism producing this. I get the same result in Windows, but my Windows installation is a guest operating system on OSX. I don’t think behavior of ctrl-c on a reqular Windows machine can be predicted from this configuration.
Steps to observe the difference. **
****This is What I am Accustomed To
On OSX or Windows
- Open text edit, notepad, Word, Eclipse, Visual Studio, PowerPoint, the command line, a shell editor at the command line, Safari, Chrome, Opera, or Firefox, take your pick.
- Select a few lines of text.
- Click cmd-c (copies text to the clipboard).
- Click anywhere in any app except atom, without selecting text, The most meaningful example for me is within an editable text area where my typical intention is to paste the text from the clipboard.
- While no text is selected, click cmd-c.
- Click cmd-v or use any normal command for pasting.
The result of these steps is the text copied in step 3 will be pasted into any editable text area where the cursor has obtained focus.
To see how it works differently with Atom, continue with the rest of the steps.
7. Repeat steps 1-3 from above.
8. Now put the cursor into an open document editor in Atom (i.e., open a file with Atom and put the cursor into the area where the file can be edited with the keyboard.).
9. Without selecting any text, click cmd-c.
10. Paste content of the clipboard where ever you choose. The result is the text that will be pasted will not be the text copied into the clipboard in steps 1-3 or 7. Instead, the line of text where the cursor was placed in Atom without selecting text is pasted.
Now that I typed it out, and tested it for this note, it looks like the situation is that hitting cmd-c in Atom when no text is selected copies the current line into the clipboard, instead of there being no effect on the clipboard.
I guess this is a nice feature, I just wish Atom was not overriding the OS on this function.
OK, I’ll confess to my problem. I have a habit of hitting cmd-c when I have placed the cursor in a target text area before hitting cmd-v. I have become accustomed to relying on that nervous habit having no effect on getting the intended text where I need it. Using Atom, that nervous habit costs me the hassle of going back to the source and recopying it to the clipboard. I am going to have to learn to avoid the extraneous but until now harmless extra tap on cmd-c.
Even though I hate that hassle, the more significant issue is that Atom appears to have tossed the OS’s text manipulations out the window. That is a pretty big commitment. I would imagine this was done to give Atom a relatively easy way to standardize its environment, insulated from the OS, especially with regard to character encoding. The cost of implementing that is enormous and also bound to create changes in the user interface people are not used to seeing. It is a huge risk to the succes of the application, because it makes itself foreign to every operating system. Maybe there will be a perceived net benefit but but it is bound to create negatives as well.
I think this is tied to many of the usability issues discussed in this thread.
Any plans for Atom to have its own file system? Is this part of an intention to develop a new OS?