On Tue, Nov 28, 2006 at 01:06:54PM +0100, Karsten Sievert wrote:
> 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.
This is a planned feature, but it'll be a long time before
it's implemented. I'm currently very busy, and in the
small time I get, am working on the communication between
cgdb and gdb.
> 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:
Well, the svn version of CGDB has support for macros. That is,
it supports the "map" command. It hasn't been released yet
because it's not fully tested, and there is no documentation
for the commands, and if you do a 'map a a' it will loop
forever, and never return. With that in mind, you could try
the svn version, and see if you could make some macro's that
would suit your needs. Currently it only supports the 'map'
and 'unmap' command. However, if you desired support for the
'imap' command, I could code that up without to much effort
based on the existing code. Let me know if you are interested
in any of this.
> 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.
OK, something isn't correct here. There was no intention of
changing CGDB's behavior between .5.3 and .6.3. In fact, when
I run .5.3 and .6.3 in a white xterm, both versions show the
vertical line as being bold.
The code in .6.3 that draws the vertical bar looks like:
if (focus)
wattron(sview->win, A_BOLD);
waddch(sview->win, VERT_LINE);
if (focus)
wattroff(sview->win, A_BOLD);
> 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? ;-)
There isn't a highlight group which represents the separator.
It's hardcoded to A_BOLD. It wouldn't be much effort to add
the new group if you are not happy with the A_BOLD functionality.
I can explain how, and will accept a patch, but I don't have the
time to work on it.
If you are happy with the A_BOLD functionality, but this
changes the color of your vertical line somehow, we need more info.
Have you tested both .5.3 and .6.3 in the same term environment and
noticed these differences?
Thanks,
Bob Rossi
|