[Cgdb-users] Going from 5.3 to 6.3, identifying the active window became harder

[Karsten S. <kar...@sy...>]

Hi, Team,

let me first mention that I am very happy about CGDB.
It's fast, lean, and matches my preferred editor's user
interface -- great.

The feature which I'm missing most is the stack window,
and a way to display variables from the source window,
but that's another story.

Since I mentioned this:  I find myself typing "p varname"
into the source window again and again, and only then
realize that I just set a breakpoint and triggered other
random actions, dependent on the variable name.  Can I
create a macro which sets me into "insert" (tgdb) mode
or on the command line (probably more consistent) when I
type the 'p', and returns me to the source window after
hitting 'Enter'?  That would be neat.  But back to the
subject:

With the new highlighting scheme, (which is great!) I
noticed that it has become harder to identify the active
window.  In 5.3, the vertical bar which separated the
line numbers from the source code used to be bold if the
source window was active; not it changes from black to
blue, which on white BG is very subtle.  Now, the cursor
on the tgdb prompt is the better indication, but that's
as far away from the source code as can be.

Have I overlooked a highlight group which represents this
separator, or is the color change on it hard coded?
Does anybody have a non-approved patch, may be, which
helps me?  ;-)


Thanks for the work and support!
-Karsten