Re: environment productivity
On 3/8/2013 11:38 PM, Paavo Helde wrote:
Balog Pal <pasa@lib.hu> wrote in news:khdhim$c8l$1@news.ett.com.ua:
Switching views in a non-IDE is Alt-Tab or equivalent, but I have not yet
found convenient ways to switch views inside an IDE without reaching to
the mouse.
In VS you can bind any key to any command -- built-in or written by you.
Can be even dependent on what kind of document you're in. I'm not sure
if you can re-bind system-wide stuff like alt-tab, I never wanted, as it
is there to switch to outside windows. (I recall how annoying it was
when I worked with virtual machines and alt-tab switched windows inside
the VM when I wanted the next natural desktop window :)
I also use the shell history and its search functions (e.g.
Ctrl-R in bash) a lot, so I never have to type the same thing twice.
Keeping history of anything is probably the first thing any IDE (or
GUI program) learned.
The history of debug launch commands with different command-line
arguments is still missing in my primary IDE
Indeed, though if you have a just a number of variants, in VS you can
add projects that has no content just the debug setting. Then can launch
any easily. Probably it can be covered by a macro too. I have only a few
variants so never bothered with better way.
, after 10+ years. I have
resorted to starting the program from the bash command-line, then
attaching the debugger, but this is cumbersome as well.
From command line you can launch gdb or ddd providing the full command
line for the of the program, so it should not be really more hassle.
And as I already said, nothing forbids to have a bash running to
supplement the IDE. While the other way around does not work.
+1 for that, having multiple CygWin bash shells running all the time. But
I would not be so sure which one is primary and which is supplement.
Shouldn't matter -- the point is to have everything at fingertip so
activity is used on new work rather than retype incantations or info the
system really knows.
(That's not proof, because most people seem not
to use their tools efficiently at all, no matter what the tools
are.)
Yeah, Iwas pretty shocked to observe that with all those supposedly
excellent unix-based tools my colleagues (who were linux guru level)
could not do as much as walking a list of compiler errors with F4 --
instead had to do actions to open the related sources and navigate
to lines. :-((( I thought we left that behind in last century.
Ironically, this is the only reason I launch our chosen Linux IDE
(CodeBlocks, and I did not choose it) - the only thing which it is good
at is navigating to errors (editing sucks, debugging does not work at
all, compile without attempted recompile of earlier dependencies not
possible, find-in-project-files missing, recently edited windows list
missing (i.e. Alt-W-2 not working), etc.), so the only use is actually to
fix some random compilation errors time after time (usually caused by so-
called "MS language extensions" compiling fine on Windows and failing on
Linux).
A few years ago someone suggested CB, I dropped it after very little try
as hopeless. Too bad, as it looks like something used up much
development time, so could be useful.
I recall my early years -- Borland C++ 3.1 IDE just rocked. Had
practically everything I could imagined at the time, and so many
successors were much bigger but didn't come even close.