WIP run test buffer in single fullscreen window and restore after finished

[tonini]

This is just a draft solution for running test buffers as fullscreen windows.

• Select specific test buffer and show as single opened window.
• define q key inside of buffer to quite and restore last window state.

@senny What do you think about these kind of test flow? Consider that the code is really prototypal, so we could talk about how to do it later. :smile:

[tonini]

@jone Your opinion is also desired. :jack_o_lantern:

[jone]

What is the difference from using M-1 / M-C-1? Does this automatically enlarge on M-e?

[tonini]

yeah it makes your current test buffer (M-e) as active window and enlarge it (aside this, it defines the "q" key to restore the last window setup and quit the test buffer.)

The whole point it's about having the test buffer isolatet as standalone window, get a better overview and a consistency where the buffer will shown up.

[jone]

Ok. I'm personally a little bit conservative about things that change my window configuration. I do not have a very consistent window management behavior and like to manage them more explicitly, such as with M-1.

Sometimes I do exactly the same (enlarging the test buffer) but often I also make the *compilation* window very small and continue working on the code while re-running the tests and watching just the modeline of the compilation buffer. In this situation it would interrupt my coding flow when my coding windows are "removed" for showing the compilation buffer.

Since I'm not using the ruby bundle very often I'm not very affected by this change, but I'd not make this the default behavior, but maybe make it configurable.

By the way, you could also use a separate perspective for tests. The point of perspectives is that it takes care of the window settings so that you can switch between multiple working environments. I often also use this for separating coding and testing, and then I switch between the perspectives with C-p p.

[tonini]

I see your point and also think to make it a default behavior wouldn't be a good choice.

What do you think about it if I try to build it more customizable and by default it's there isn't a special behavior when you run your test suite. I will try to build two solutions, one with perpective and one without.

The idea at last would be to give the possibilty for a test suite runner setup for every programming language bundle.

Thanks for your feeback.:)

[tonini]

I will close this one and use this workflow in my personal setup. :)