I also use this same workflow at the moment, and I blame it for my squinty eyes and headaches, as its not exactly easy to visually parse compiler errors from a command terminal…
I mean, it seems like it would be easy to get a keyboard shortcut for walking through each compiler error working since Particle Dev already has a list with locations of compiler errors loaded into memory and displayable on the Atom compiler search errors window that opens…
I’m afraid I don’t have the time to dig into it at the moment (plus don’t know how to write atom packages yet).
Another (preferable) alternative to this would be if Particle could integrate Particle Dev with a Linter for GCC as I detailed in this other post. If that were the case, then you’d see each error/warning as you are writing code in real time and this problem would be moot.