In emacs when I press alt + m to build. It prompts me with 'Save file w:/xxx/xxx/xxx.cp? (y, n ...)'.
Now I switched to 4coder I noticed how useful this is. I had several times already I didn't understand the compile errors until I noticed I forgot to save a file.
So I hope this will get in some day.
Now I switched to 4coder I noticed how useful this is. I had several times already I didn't understand the compile errors until I noticed I forgot to save a file.
So I hope this will get in some day.
clankill3r
In emacs when I press alt + m to build. It prompts me with 'Save file w:/xxx/xxx/xxx.cp? (y, n ...)'.
Now I switched to 4coder I noticed how useful this is. I had several times already I didn't understand the compile errors until I noticed I forgot to save a file.
So I hope this will get in some day.
I've setup my vimrc to always save when I build. I'm curious, do you ever want to build before saving?
Adding a configuration option for "save all dirty buffers before build" has been on my todo list for a while, but it has never been promoted to the top somehow. I'll get this in in the next build.
Am i missing something or are things like this just not documented anywhere?
I know how its done now since i searched through the code; but are there logs or something?
If you open 4coder you wrote that its in now, but not how to use it.
And you wrote its in the config file, but at least the method i use has to be declared in the
project file.
This is no hate; id just like to know if im missing something.
For anyone who wants to know how it works, or at least one way of doing it:
add a forth argument to the fkey commands
example:
fkey_command_linux[1] = {"./build.sh", "*compilation*", true, true};
I know how its done now since i searched through the code; but are there logs or something?
If you open 4coder you wrote that its in now, but not how to use it.
And you wrote its in the config file, but at least the method i use has to be declared in the
project file.
This is no hate; id just like to know if im missing something.
For anyone who wants to know how it works, or at least one way of doing it:
add a forth argument to the fkey commands
example:
fkey_command_linux[1] = {"./build.sh", "*compilation*", true, true};
You're not missing anything Benno, the documentation is not spectacular. I try to make up for it by being quick to respond to emails with questions, so you can ask as [email protected] next time something you need isn't clear enough.