This has been discussed before, but not recently.... Has there been any progess in making uv3 not open all its windows when using the -b command line option? It is rather annoying when all you want to do is compile from within emacs and it insists on waisting all that time opening 10s if windows for no reason at all....
"It is rather annoying when all you want to do is compile from within emacs ..." Wouldn't you want to invoke the command-line tools directly from emacs or from emacs through a makefile? http://www.keil.com/support/man/docs/ca/ca_cm_cmdprompt.htm
The problem is that its a team of people working on the source, not just me. Most of the programs have a M$ background and find the IDE OK. I however have a unix background and find the IDE terrible. I've been using emacs for the last 16 years and my finger subconsiously know the key sequences without my brain being involved.... Plus there is the automatic indentation, spelling checker, ctags cross reference, .., .., .... Moving to a Makefile is not possible becasue of the other programmers. I would end up maintaining a makefile in parallel to the .uv2 file... If i could just kill the GUI i would be happy. So calling uv3 -b foobar.uv2 from within emacs's compile mode seems like the ideal solution. The errors should get piped back into emacs so M-' should work (and should work much better than the IDEs F4 key which seems to be rather primitive). However uv3 -b insists in starting up the GUI and opening all the source file windows, before actually starting to do any compiling.....
I ... find the IDE terrible a kindred spirit - finally. I would, however rephrase to "I find any IDE terrible". I think the Keilers have done a decent job making the wrong concept work to some extent and - at least - they have not made it mandatory to use it, like some unmentionable company has. Erik PS: never used UNIX, that is not my reason, I just hate someone (in this case the IDE designer) telling me that (s)he knows better than me what I want.
I would, however rephrase to "I find any IDE terrible". :-) We are getting off topic, but... You might actually like emacs then. Its kind of an IDE without actually being an IDE. Its got all the usual tools of an IDE, like compiling, goto next error, cross referencing, an interface to debuggers, access to documentation, code repository tools etc. It does not implement these functions itself, it uses other tools to do it. eg searching is normally done with grep and find, spelling checking is normally done by ispell or aspell, compiling is normally done by calling make, etc. But you get to choose what tools it uses so you can use whatever tool you think is the best. Emacs as also been around a long time, 20 years, so its pritty mature unlike most IDEs. The version in cygwin seems to work best on M$ platforms.
View all questions in Keil forum