Separate build command

[Sira0909]

This would allow the user to set a build command per project, separate from the last-run command. Useful if you want to save both a command to build the project and one to run it.

[Sira0909]

my mistake, forgot to remove something from bug fixing

[TheLazyCat00]

@Sira0909 I don't know about this. I get the idea, but I think that if we merge #2, there's already a way to set different commands. If we would allow 2 seperate commands, why not allow 3? What I'm saying is that this workflow isnt generally applicable. Personally, I always run and build in one command directly.

[Sira0909]

I agree with the ability to add more than 2 commands, but I do also think the ability to cache those commands on a per-project basis is important, which i do not think #2 has. (Say you have two projects, one in java the other in c. You cant have just one command do both unless you use a makefile for both projects)

[TheLazyCat00]

To be honest, I don't think you should be able to have more than 1 command per project. Not every project is in a compiled language to begin with - what do you do with the build command in a python project? Is it just a wasted keybind? If we introduced a variable amount of commands with the ability to add and remove commands, the whole plugin becomes way more complex, more complex then necessary for most people. We'd have to create some kind of command selection through keybinds (buffer-manager type problem), a way to add commands and probably a lot more. I don't think this is the path I wanna take. This plugin should be a simple terminal with run-last-cmd integration. @Sira0909

[Sira0909]

Alright, thats fine. (Just as a clarification, I think my original idea was that if you dont usually compile you just wouldn't have that keybind. I see your point of keeping it simple though)