Every single file I open opens in new instance of Atom

#1

Everything was working great, until a few days ago when the “Toogle” stopped to open automatically and now everytime I open a file with Atom, it opens a new instance, which can be pretty annoying when I work with a lot of files at the same time. I don’t know what happened and I can’t figure out how to make it work.

Could anyone help me with that ?

Thanks

2 Likes

Atom could open file with new tab in mac book pro
Atom could open file with new tab in mac book pro
#2

I’m facing the same issue here. I’m using macOS Mojave (10.14.4)!!!

1 Like

#3

:wave: There’s an ongoing discussion about 1.36.0 launch behavior here: https://github.com/atom/atom/issues/19147 Subscribe to that issue to stay up to date on progress and decisions.

The short version is that, for now, you can add a project folder to your Atom window (File -> Add Project Folder…). Once your window has a project folder, paths within that folder will open in the existing window as before.

We used to do this for you automatically when you opened a single file, but it caused serious performance issues when you’d try to edit a file in a large directory, like your home directory.

2 Likes

#4

I’m facing the same issue here. I’m using win10

0 Likes

#5

Thanks ! I didn’t know all that

0 Likes

#7

Hi. I open files from ftp in atom. Each time a new tab opens, it is annoying. And the error “Uncaught TypeError: wrapGuide.updateGuide is not a function” appears.
And not working search…

0 Likes

#8

What package are you using for FTP? Do you have the wrap-guide package enabled? If so, try turning it off. If not, try turning it on.

(By the way, when you have a brand new question you should probably start a new thread. Don’t do it now because I’ve already responded to you, but keep that in mind for next time.)

0 Likes

#9

I have downgraded to atom v 1.35.1 and it works, but this bug is very annoying and I’m thinking to switch to another editor

0 Likes

#10

As detailed in the GitHub issue linked above, this is not a bug (it was made that way on purpose, so not a bug by definition); it’s an interaction that wasn’t thought through thoroughly enough given the number of people with use cases that the new behavior causes trouble for. You can participate in the discussion on that issue.

0 Likes