Fabian Stiewitz

Thanks for the report. `v4.5.4` fixes a few issues I had wih Atom's beta channel, maybe it also fixes your problem. Unfortunately I was not able to reproduce your bug....

The shell option is supposed to be used when there is a need for shell functionality ( like bash scripting or environment variables ). To open a new terminal window,...

Key Binding Resolver shows key bindings, but does not check whether their commands actually exist. Commands for built-tools are mentioned [here](https://github.com/deprint/build-tools-cpp/blob/master/keymaps/build-tools.cson). Just make sure that your "compile" command is the...

You can't access your commands by name. If your command is the first one in your `.build-tools.cson`, you execute it with `build-tools:first-command`. `build-tools:second-command` and `build-tools:third-command` execute the second and third...

g++ works perferctly fine on my machine. I also can't think of a configuration problem that would hide stdout but not stderr, but I also don't really have any information...

I guess it would make sense to also start the command. `g++` just compiles it. Also, stdin can be buggy if you don't use pty.js.

I guess there is something wrong with your configuration but I can't test it, since I don't use this OS. `*.cpp` in your `command` shouldn't work either, but then `g++`...

I'm not saying people should change their OS because of my package. I'm just saying that I do not know enough about Windows to properly support it.

Right now, there is only `build-tools:toggle` (bound to `ctrl-l ctrl-s`). An addition to your user keymap or init script should do the trick. I'll work on a `build-tools:hide` though.

I assume this happened when you closed a console tab while the process was still running ?