cgdb-devel — Development activity -- bug reports, patches, related questions

[Cgdb-devel] [ cgdb-Bugs-2855779 ] Ctrl-D in gdb window exits immediately

[SourceForge.net <no...@so...>]

Bugs item #2855779, was opened at 2009-09-10 00:48
Message generated for change (Tracker Item Submitted) made by crouchingturbo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2855779&group_id=72581

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CGDB
Group: None
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Mike Mueller (crouchingturbo)
Assigned to: Mike Mueller (crouchingturbo)
Summary: Ctrl-D in gdb window exits immediately

Initial Comment:
In gdb, pressing Ctrl-D would normally prompt "are you sure?" if the program is currently being debugged.  CGDB doesn't confirm, it simply exits, which can be frustrating.  (Ctrl-D is a useful keystroke in the sourrce window, so this is an easy accident.)

CGDB should send the EOF character to GDB, and let GDB handle it in the normal way, rather than having special case code in cgdb.c to cleanup and quit.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=534974&aid=2855779&group_id=72581

Re: [Cgdb-devel] Bug: the default readline hotkeys Alt-X don't work in cgdb

[Kuang He <ic...@gm...>]

On Sat, Jul 25, 2009 at 6:51 PM, Bob Rossi<bo...@br...> wrote:
> Hi,
>
> I'm trying to prepare a release of CGDB, and I didn't like the way I
> implemented this feature, so I'm working on fixing it.
>
> My patch has the gdb prompt starting at the top of the gdb window
> and it moves down, like it would if you use gdb from the terminal
> directly. Also, I made it so that when you hit Ctrl+l, that the
> prompt goes back to the top.
>
> My question is this, currently, my patch clears the history in the
> gdb window, so that if you hit Ctrl+l, you can't see the previous
> history anymore with page up. Is this desirable? I could
> alternatively move the gdb prompt to the top of the window, and keep
> the history. That would be a little more work for me...
>
> Anyone care?

Dear Bob,

I would say that it is certainly desirable to keep the history after
clearing the screen using Ctrl+l. However, since you are the one who
provides this patch, I think you should make the call. :-)

Best regards,

-- 
Kuang He

Re: [Cgdb-devel] Bug: the default readline hotkeys Alt-X don't work in cgdb

[Bob R. <bo...@br...>]

On Tue, Jan 20, 2009 at 06:54:05PM +0800, Kuang He wrote:
> On Wed, Dec 17, 2008 at 10:14 AM, Bob Rossi <bo...@br...> wrote:
> > On Fri, Sep 26, 2008 at 01:03:10PM -0400, Kuang He wrote:
> >> By the way, when I press CTRL-L in the gdb window, it does not clear
> >> the screen, but rather generates a new input line. Is this intended,
> >> or a bug?
> >
> > I just fixed this upstream. Hopefully I'll be able to get a release out
> > soon. There is still a few more bug fixes I need to get done.
> >
> > If you type CTRL-L in CGDB, it now clears the entire GDB window with
> > newlines.
> 
> Hi Bob,
> 
> I've tested the feature, and it works OK!
> 
> One small problem though: each time I press Ctrl+L, it would generate
> a chunk of empty lines in the command history (shown using
> PageUp/PageDn). This is no big problem, but I feel that I should point
> it out. Maybe it is due to the design that texts are shown at the
> bottom rather than at the top of the screen after clearing the screen.

Hi,

I'm trying to prepare a release of CGDB, and I didn't like the way I
implemented this feature, so I'm working on fixing it.

My patch has the gdb prompt starting at the top of the gdb window
and it moves down, like it would if you use gdb from the terminal 
directly. Also, I made it so that when you hit Ctrl+l, that the
prompt goes back to the top. 

My question is this, currently, my patch clears the history in the
gdb window, so that if you hit Ctrl+l, you can't see the previous
history anymore with page up. Is this desirable? I could
alternatively move the gdb prompt to the top of the window, and keep
the history. That would be a little more work for me...

Anyone care?

Bob Rossi

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Kyle M. <ma...@gm...>]

On Jul 22, 2009, at 19:13, Bob Rossi wrote:
>>>> Additionally, Mac OS X commonly uses files with
>>>> extensions .cp, .m, .mm and .M.  These files are not currently
>>>> colorized by the cgdb tokenizer.  The C tokenizer does a very good
>>>> job
>>>> with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C+ 
>>>> +).  A
>>>> simple patch to tokenizer.c allows the C tokenizer to colorize  
>>>> these.
>>>> The patch is attached to cgdb bug 2806868 here:
>>>>
>>>>  https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974
>>
>> What about the ".cp" extension?  That's a normal C++ file?  Please  
>> add
>> the .cp extension to the list of extensions handled by the existing
>> lexer -- ".cp" is a commonly used C++ extension in a variety of open
>> source file projects.
>
> OK, I will do this.
>
>>> I can show you what to do if you want. It's mostly just a flex  
>>> scanner
>>> under the hood. All you really need to do is enumerate all the
>>> keywords.
>>
>> Sure, I'll be happy to create a flex scanner since it will be  
>> basically a
>> copy of the C/C++ one that's already there plus recognition of the  
>> few
>> special Objective-C keywords/types that are added and '#import'.  The
>> existing C/C++ scanner already does 99% of what it needs to do for
>> Objective-C/Objective-C++ sources.
>>
>> Just point me to the code.
>
> OK, I will, give me some time to refresh my memory and I'll give you
> some good instructions.

Okay, I've attached a patch that adds a new lexer for Objective-C/ 
Objective-C++ files.  The attached patch (lexer-patch.gz) is against  
revision 929 (the latest on trunk) of the cgdb subversion repository  
(and can be applied with patch -p1 to a checkout of http://cgdb.svn.sourceforge.net/svnroot/cgdb/cgdb/trunk) 
.

The patch also includes the addition of ".cp" to the c_extensions list  
and includes the C-specific enhancements I added for objclexer.l as a  
patch to the C lexer as well:

   * Now recognizes hexadecimal integer literals
   * Now recognizes \octal and \xHEX character constants as literals  
('\x55' '\012')
   * Now recognizes 'NULL' as a literal
   * Now recognizes false and true as literals (they are defined as  
the two boolean literals in the standard) not keywords.
   * Now recognizes integer suffixes and optional minus sign as part  
of the number literal
   * Now recognizes floating point constant literals
   * Now recognizes the leading 'L' as part of the literal for wide  
character and wide string literals

And tokenizer-driver.c was updated as well to support 'objc' as a  
lexer name.

It builds, runs and highlights properly for me.  Other than the new  
objclexer.l file (which is about 80% the same as clexer.l), the  
changes are pretty minor.

Kyle

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Bob R. <bo...@br...>]

On Wed, Jul 22, 2009 at 05:58:34PM -0700, Kyle McKay wrote:
> On Jul 21, 2009, at 18:36, Bob Rossi wrote:
>> On Mon, Jun 15, 2009 at 04:18:51PM -0700, Kyle McKay wrote:
>>> cgdb-0.6.4 has difficulties building for Mac OS X 10.5.  It needs to
>>> have HAVE_OPENPTY defined.
>>>
>>> You can either do:
>>>
>>>   CFLAGS=-DHAVE_OPENPTY ./configure
>>>
>>> Or apply a patch to configure.init.  The patches are attached to cgdb
>>> bug 2806868 here:
>>>
>>>   https://sourceforge.net/tracker/?func=detail&aid=2806854&group_id=72581&atid=534974
>>
>> OK, I've applied this patch, please try this test release,
>>  http://brasko.net:81/bob/cgdb-20090721.tar.gz
>> and let me know how it works out. If it works for you, I'll put it
>> in the next release.
>
> It configured, built and ran on both Mac OS X 10.4.11 and Mac OS X  
> 10.5.7.  See attached gzipped script output.  (Note that I had already  
> separately installed a compatible version of readline first as the  
> native Mac OS X readline (4.2) is too old -- that installation is not  
> included in the script output.)

OK, this has been accepted and applied. Thank you so much for this
patch, it has been reported before, but never was resolved.

>>> Additionally, Mac OS X commonly uses files with
>>> extensions .cp, .m, .mm and .M.  These files are not currently
>>> colorized by the cgdb tokenizer.  The C tokenizer does a very good  
>>> job
>>> with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C++).  A
>>> simple patch to tokenizer.c allows the C tokenizer to colorize these.
>>> The patch is attached to cgdb bug 2806868 here:
>>>
>>>   https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974
>
> What about the ".cp" extension?  That's a normal C++ file?  Please add  
> the .cp extension to the list of extensions handled by the existing  
> lexer -- ".cp" is a commonly used C++ extension in a variety of open  
> source file projects.

OK, I will do this.

>> I can show you what to do if you want. It's mostly just a flex scanner
>> under the hood. All you really need to do is enumerate all the  
>> keywords.
>
> Sure, I'll be happy to create a flex scanner since it will be basically a 
> copy of the C/C++ one that's already there plus recognition of the few 
> special Objective-C keywords/types that are added and '#import'.  The 
> existing C/C++ scanner already does 99% of what it needs to do for 
> Objective-C/Objective-C++ sources.
>
> Just point me to the code.

OK, I will, give me some time to refresh my memory and I'll give you
some good instructions.

Thanks,
Bob Rossi

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Kyle M. <ma...@gm...>]

On Jul 21, 2009, at 18:36, Bob Rossi wrote:
> On Mon, Jun 15, 2009 at 04:18:51PM -0700, Kyle McKay wrote:
>> cgdb-0.6.4 has difficulties building for Mac OS X 10.5.  It needs to
>> have HAVE_OPENPTY defined.
>>
>> You can either do:
>>
>>   CFLAGS=-DHAVE_OPENPTY ./configure
>>
>> Or apply a patch to configure.init.  The patches are attached to cgdb
>> bug 2806868 here:
>>
>>   https://sourceforge.net/tracker/?func=detail&aid=2806854&group_id=72581&atid=534974
>
> OK, I've applied this patch, please try this test release,
>  http://brasko.net:81/bob/cgdb-20090721.tar.gz
> and let me know how it works out. If it works for you, I'll put it
> in the next release.

It configured, built and ran on both Mac OS X 10.4.11 and Mac OS X  
10.5.7.  See attached gzipped script output.  (Note that I had already  
separately installed a compatible version of readline first as the  
native Mac OS X readline (4.2) is too old -- that installation is not  
included in the script output.)

>> Additionally, Mac OS X commonly uses files with
>> extensions .cp, .m, .mm and .M.  These files are not currently
>> colorized by the cgdb tokenizer.  The C tokenizer does a very good  
>> job
>> with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C++).  A
>> simple patch to tokenizer.c allows the C tokenizer to colorize these.
>> The patch is attached to cgdb bug 2806868 here:
>>
>>   https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974

What about the ".cp" extension?  That's a normal C++ file?  Please add  
the .cp extension to the list of extensions handled by the existing  
lexer -- ".cp" is a commonly used C++ extension in a variety of open  
source file projects.

> I'd prefer not to do a solution like this. However, if you want to  
> write
> the entire scanner for the Objective-C++ language, I'll accept it.

I will be happy to do that.  Since the Objective-C language has  
exactly the same tokenizer as the C language it likely wouldn't  
require much effort to create an Objective-C/Objective-C++ highlighter  
from the existing C/C++ one already in cgdb.

FYI here is some valid C:

#define doubleit * 2
typedef int id;

id array[20];
id value = 7;
id x = array[value doubleit]; /* index integer array */

Here is some valid Objective-C:

#include <objc/objc.h>
id value = nil; /* id and nil are defined in objc.h */
id x = [value doubleit]; /* send doubleit message to value object */

Objective-C provides minor extensions to the C grammar.  Objective-C  
is a very thin layer on top of C, and moreover is a strict superset of  
C.  Objective-C treats token sequences between '[' and ']' specially  
when the '[' ... ']' sequence appears in certain grammar contexts.   
Objective-C does introduce some special two-token keywords that start  
with '@' such as '@class', '@interface', '@implementation', '@end',  
etc. and if the first token after the '[' of a special '[' ... ']'  
sequence is the identifier 'self' or 'super' it is treated specially.   
Finally Objective-C adds the '#import' directive that's identical to  
'#include' except it's guaranteed to only include files once.   
Objective-C++ is identical to Objective-C except that the extensions  
are provided to the C++ grammar rather than the C grammer.

> I can show you what to do if you want. It's mostly just a flex scanner
> under the hood. All you really need to do is enumerate all the  
> keywords.

Sure, I'll be happy to create a flex scanner since it will be  
basically a copy of the C/C++ one that's already there plus  
recognition of the few special Objective-C keywords/types that are  
added and '#import'.  The existing C/C++ scanner already does 99% of  
what it needs to do for Objective-C/Objective-C++ sources.

Just point me to the code.

Thanks,

Kyle

> Thanks,
> Bob Rossi
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel

Re: [Cgdb-devel] cgdb license.

[Gilboa D. <gi...@gm...>]

On Tue, 2009-07-21 at 11:28 -0400, Bob Rossi wrote:
> On Wed, Jul 15, 2009 at 07:46:32PM +0300, Gilboa Davara wrote:
> > Hello all,
> > 
> > I'm the maintainer of cgdb under both RHEL and Fedora.
> > Seems that Fedora is about to switch to a GPLv3 readline library.
> > To the best of my knowledge, cgdb still uses GPLv2 (and not GPLv2+)
> > which is incompatible with GPLv3.
> > 
> > Any chance that future versions of cgdb will switch to GPLv2+?
> 

Hello Bob,

Thanks for the answer.

> Would releasing the next version under GPLv3 solve the problem?

Yes.

> 
> I sort of don't like the idea of releasing with the license GPLv2+.
> My objection to that is simply that I don't like releasing software
> under a license that I have not had the opportunity to read yet.
> 

No problem.
F12 is ~5 months away.
Take your time :)

> Thanks,
> Bob Rossi

- Gilboa

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Bob R. <bo...@br...>]

On Mon, Jun 15, 2009 at 04:18:51PM -0700, Kyle McKay wrote:
> cgdb-0.6.4 has difficulties building for Mac OS X 10.5.  It needs to  
> have HAVE_OPENPTY defined.
> 
> You can either do:
> 
>    CFLAGS=-DHAVE_OPENPTY ./configure
> 
> Or apply a patch to configure.init.  The patches are attached to cgdb  
> bug 2806868 here:
> 
>    https://sourceforge.net/tracker/?func=detail&aid=2806854&group_id=72581&atid=534974

OK, I've applied this patch, please try this test release,
  http://brasko.net:81/bob/cgdb-20090721.tar.gz
and let me know how it works out. If it works for you, I'll put it 
in the next release.

> Additionally, Mac OS X commonly uses files with  
> extensions .cp, .m, .mm and .M.  These files are not currently  
> colorized by the cgdb tokenizer.  The C tokenizer does a very good job  
> with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C++).  A  
> simple patch to tokenizer.c allows the C tokenizer to colorize these.   
> The patch is attached to cgdb bug 2806868 here:
> 
>    https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974

I'd prefer not to do a solution like this. However, if you want to write
the entire scanner for the Objective-C++ language, I'll accept it.
I can show you what to do if you want. It's mostly just a flex scanner
under the hood. All you really need to do is enumerate all the keywords.

Thanks,
Bob Rossi

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Kyle M. <ma...@gm...>]

On Jul 21, 2009, at 08:32, Bob Rossi wrote:
> On Fri, Jun 19, 2009 at 10:45:00AM -0700, Kyle McKay wrote:
>> Sorry, I don't have any publicly-visible machines.  I do have both
>> 10.5.7 and 10.4.11 running on different machines though and would be
>> happy to build specific revisions and/or tarballs cgdb on those
>> machines and send you the script output so you can verify a  
>> successful
>> build (a manual tinderbox).
>
> Hi Kyle,
>
> Sorry for the delay. I would like to help get these patches into CGDB
> as soon as possible. I'm going to patch them into CGDB, and then
> provide you with a tarball that perhaps you could test on your
> mac machines? Sending me the build output would be great.

No problem.  That's easy to do.  I'll send you a gzipped script output  
file of the build.

Kyle

> If you say it works for you, I'll consider that an improvement, and
> we can release with those changes.
>
> Thanks,
> Bob Rossi
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel

Re: [Cgdb-devel] cgdb license.

[Bob R. <bo...@br...>]

On Wed, Jul 15, 2009 at 07:46:32PM +0300, Gilboa Davara wrote:
> Hello all,
> 
> I'm the maintainer of cgdb under both RHEL and Fedora.
> Seems that Fedora is about to switch to a GPLv3 readline library.
> To the best of my knowledge, cgdb still uses GPLv2 (and not GPLv2+)
> which is incompatible with GPLv3.
> 
> Any chance that future versions of cgdb will switch to GPLv2+?

Would releasing the next version under GPLv3 solve the problem?

I sort of don't like the idea of releasing with the license GPLv2+.
My objection to that is simply that I don't like releasing software
under a license that I have not had the opportunity to read yet.

Thanks,
Bob Rossi

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Bob R. <bo...@br...>]

On Fri, Jun 19, 2009 at 10:45:00AM -0700, Kyle McKay wrote:
> Sorry, I don't have any publicly-visible machines.  I do have both  
> 10.5.7 and 10.4.11 running on different machines though and would be  
> happy to build specific revisions and/or tarballs cgdb on those  
> machines and send you the script output so you can verify a successful  
> build (a manual tinderbox).

Hi Kyle,

Sorry for the delay. I would like to help get these patches into CGDB
as soon as possible. I'm going to patch them into CGDB, and then 
provide you with a tarball that perhaps you could test on your
mac machines? Sending me the build output would be great.

If you say it works for you, I'll consider that an improvement, and
we can release with those changes.

Thanks,
Bob Rossi

[Cgdb-devel] cgdb license.

[Gilboa D. <gi...@gm...>]

Hello all,

I'm the maintainer of cgdb under both RHEL and Fedora.
Seems that Fedora is about to switch to a GPLv3 readline library.
To the best of my knowledge, cgdb still uses GPLv2 (and not GPLv2+)
which is incompatible with GPLv3.

Any chance that future versions of cgdb will switch to GPLv2+?

- Gilboa

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Kyle M. <ma...@gm...>]

On Jun 19, 2009, at 04:04, Bob Rossi wrote:
> On Mon, Jun 15, 2009 at 04:18:51PM -0700, Kyle McKay wrote:
>> cgdb-0.6.4 has difficulties building for Mac OS X 10.5.  It needs to
>> have HAVE_OPENPTY defined.
>>
>> You can either do:
>>
>>   CFLAGS=-DHAVE_OPENPTY ./configure
>>
>> Or apply a patch to configure.init.  The patches are attached to cgdb
>> bug 2806868 here:
>>
>>   https://sourceforge.net/tracker/?func=detail&aid=2806854&group_id=72581&atid=534974
>>
>> Additionally, Mac OS X commonly uses files with
>> extensions .cp, .m, .mm and .M.  These files are not currently
>> colorized by the cgdb tokenizer.  The C tokenizer does a very good  
>> job
>> with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C++).  A
>> simple patch to tokenizer.c allows the C tokenizer to colorize these.
>> The patch is attached to cgdb bug 2806868 here:
>>
>>   https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974
>
> Hi Kyle,
>
> Thanks for the work here. We would love to add these patches to cgdb
> and finally get another release out. One thing we are researching is,
> how to get access to a Mac maching for testing purposes. Up until now,
> we can't seem to get access to one. Would you have an account  
> available
> somewhere you could provide us with, temporarily of course?
>
> Thanks,
> Bob Rossi

Bob,

Sorry, I don't have any publicly-visible machines.  I do have both  
10.5.7 and 10.4.11 running on different machines though and would be  
happy to build specific revisions and/or tarballs cgdb on those  
machines and send you the script output so you can verify a successful  
build (a manual tinderbox).

Kyle

Re: [Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Bob R. <bo...@br...>]

On Mon, Jun 15, 2009 at 04:18:51PM -0700, Kyle McKay wrote:
> cgdb-0.6.4 has difficulties building for Mac OS X 10.5.  It needs to  
> have HAVE_OPENPTY defined.
> 
> You can either do:
> 
>    CFLAGS=-DHAVE_OPENPTY ./configure
> 
> Or apply a patch to configure.init.  The patches are attached to cgdb  
> bug 2806868 here:
> 
>    https://sourceforge.net/tracker/?func=detail&aid=2806854&group_id=72581&atid=534974
> 
> Additionally, Mac OS X commonly uses files with  
> extensions .cp, .m, .mm and .M.  These files are not currently  
> colorized by the cgdb tokenizer.  The C tokenizer does a very good job  
> with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C++).  A  
> simple patch to tokenizer.c allows the C tokenizer to colorize these.   
> The patch is attached to cgdb bug 2806868 here:
> 
>    https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974

Hi Kyle,

Thanks for the work here. We would love to add these patches to cgdb
and finally get another release out. One thing we are researching is,
how to get access to a Mac maching for testing purposes. Up until now,
we can't seem to get access to one. Would you have an account available
somewhere you could provide us with, temporarily of course?

Thanks,
Bob Rossi

[Cgdb-devel] Mac OS X 10.5 cgdb Patches

[Kyle M. <ma...@gm...>]

cgdb-0.6.4 has difficulties building for Mac OS X 10.5.  It needs to  
have HAVE_OPENPTY defined.

You can either do:

   CFLAGS=-DHAVE_OPENPTY ./configure

Or apply a patch to configure.init.  The patches are attached to cgdb  
bug 2806868 here:

   https://sourceforge.net/tracker/?func=detail&aid=2806854&group_id=72581&atid=534974

Additionally, Mac OS X commonly uses files with  
extensions .cp, .m, .mm and .M.  These files are not currently  
colorized by the cgdb tokenizer.  The C tokenizer does a very good job  
with these (.cp = C++, .m = Objective-C, .mm/.M = Objective-C++).  A  
simple patch to tokenizer.c allows the C tokenizer to colorize these.   
The patch is attached to cgdb bug 2806868 here:

   https://sourceforge.net/tracker/?func=detail&aid=2806868&group_id=72581&atid=534974

Kyle

Re: [Cgdb-devel] Patch: Vertical split mode

[David W. <dwh...@gm...>]

Hi Bob,

Unfortunately, my brief window of free time closed shortly after I  
posted the patch.  If after you have taken a look at the patch you  
think it may be worth including, I could try to find some time to  
clean it up, but It probably won't be for a couple of months.

Thanks,
David


On Feb 14, 2009, at 2:08 PM, Bob Rossi wrote:

> * Replies will be sent through Spamex to cgd...@li...
> * For additional info click -> http://www.spamex.com/i/?v=30895725
>
> On Mon, Jan 19, 2009 at 07:37:34AM -0800, David Whetstone wrote:
>> I've added a patch to the patch tracker that allows a vertical split
>> in addition to the current horizontal split.  Great for wide-screen
>> monitors.
>>
>> https://sourceforge.net/tracker2/?func=detail&aid=2517429&group_id=72581&atid=534976
>
> Hi David,
>
> Thanks for the work. I've been very busy and have not had time to look
> at this. Have you made any improvements since you've uploaded this?
>
> I'll try to take a look at this patch within the next week or two.
>
> Thanks,
> Bob Rossi
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel

Re: [Cgdb-devel] Patch: Vertical split mode

[Bob R. <bo...@br...>]

On Mon, Jan 19, 2009 at 07:37:34AM -0800, David Whetstone wrote:
> I've added a patch to the patch tracker that allows a vertical split  
> in addition to the current horizontal split.  Great for wide-screen  
> monitors.
> 
> https://sourceforge.net/tracker2/?func=detail&aid=2517429&group_id=72581&atid=534976

Hi David,

Thanks for the work. I've been very busy and have not had time to look
at this. Have you made any improvements since you've uploaded this?

I'll try to take a look at this patch within the next week or two.

Thanks,
Bob Rossi

Re: [Cgdb-devel] Patch: Vertical split mode

[David W. <dwh...@gm...>]

> I've tested your patch with the feature I've longed for, and I loved
> it! Thanks for your efforts! Wide screen monitors are very common
> nowadays, and vertically split windows make very efficient use of
> screen spaces.

Thanks for trying it. I'm glad it works for you!

> A small bug I've found: when in vertical split mode, '_'/'+'
> decreases/increaes the width of the window by 25% of the height rather
> than 25% of the width.

Good catch.  I'll clean that up.  I'm sure there are probably a few  
more nits
lurking in there somewhere.

> As a related note, I think that 25% of the width might be too large a
> decrement/increment when one has a very wide terminal window. For
> example, the size of my full-screen terminal window is 76 lines by 237
> columns, so 1/4 of the width is almost 60 columns -- too large when it
> comes to adjusting the width of the window using '_'/'+'. I suppose
> this problem might be solved by setting the interval to a small value
> (e.g. 1/6 or 1/8 of the width/height) when the width/height exceeds a
> certain value (e.g. 120).

I think you're right about the 25%.  Maybe a percentage jump just  
doesn't
make sense for vertical split adjustments.  Perhaps a fixed adjustment
amount would be more sensible?

Re: [Cgdb-devel] Patch: Vertical split mode

[Kuang H. <ic...@gm...>]

On Mon, Jan 19, 2009 at 11:37 PM, David Whetstone <dwh...@gm...> wrote:
> I've added a patch to the patch tracker that allows a vertical split
> in addition to the current horizontal split.  Great for wide-screen
> monitors.
>
> https://sourceforge.net/tracker2/?func=detail&aid=2517429&group_id=72581&atid=534976

Hi David,

I've tested your patch with the feature I've longed for, and I loved
it! Thanks for your efforts! Wide screen monitors are very common
nowadays, and vertically split windows make very efficient use of
screen spaces.

A small bug I've found: when in vertical split mode, '_'/'+'
decreases/increaes the width of the window by 25% of the height rather
than 25% of the width.

As a related note, I think that 25% of the width might be too large a
decrement/increment when one has a very wide terminal window. For
example, the size of my full-screen terminal window is 76 lines by 237
columns, so 1/4 of the width is almost 60 columns -- too large when it
comes to adjusting the width of the window using '_'/'+'. I suppose
this problem might be solved by setting the interval to a small value
(e.g. 1/6 or 1/8 of the width/height) when the width/height exceeds a
certain value (e.g. 120).

Best regards,

-- 
Kuang He

Re: [Cgdb-devel] Bug: the default readline hotkeys Alt-X don't work in cgdb

[Kuang H. <ic...@gm...>]

On Wed, Dec 17, 2008 at 10:14 AM, Bob Rossi <bo...@br...> wrote:
> On Fri, Sep 26, 2008 at 01:03:10PM -0400, Kuang He wrote:
>> By the way, when I press CTRL-L in the gdb window, it does not clear
>> the screen, but rather generates a new input line. Is this intended,
>> or a bug?
>
> I just fixed this upstream. Hopefully I'll be able to get a release out
> soon. There is still a few more bug fixes I need to get done.
>
> If you type CTRL-L in CGDB, it now clears the entire GDB window with
> newlines.

Hi Bob,

I've tested the feature, and it works OK!

One small problem though: each time I press Ctrl+L, it would generate
a chunk of empty lines in the command history (shown using
PageUp/PageDn). This is no big problem, but I feel that I should point
it out. Maybe it is due to the design that texts are shown at the
bottom rather than at the top of the screen after clearing the screen.

-- 
Kuang He

[Cgdb-devel] Patch: Vertical split mode

[David W. <dwh...@gm...>]

I've added a patch to the patch tracker that allows a vertical split  
in addition to the current horizontal split.  Great for wide-screen  
monitors.

https://sourceforge.net/tracker2/?func=detail&aid=2517429&group_id=72581&atid=534976

Re: [Cgdb-devel] Bug: the default readline hotkeys Alt-X don't work in cgdb

[Bob R. <bo...@br...>]

On Fri, Sep 26, 2008 at 01:03:10PM -0400, Kuang He wrote:
> By the way, when I press CTRL-L in the gdb window, it does not clear
> the screen, but rather generates a new input line. Is this intended,
> or a bug?

I just fixed this upstream. Hopefully I'll be able to get a release out
soon. There is still a few more bug fixes I need to get done.

If you type CTRL-L in CGDB, it now clears the entire GDB window with
newlines.

Bob Rossi

Re: [Cgdb-devel] Patch: enable people to make cgdb-specific customizations in ~/.inputrc

[Kuang H. <ic...@gm...>]

On Sat, Oct 4, 2008 at 1:20 PM, Bob Rossi <bob...@co...> wrote:
> On Fri, Sep 26, 2008 at 03:28:08AM -0400, Kuang He wrote:
>> Hi,
>>
>> A small patch to enable people to make cgdb-specific customizations in
>> their ~/.inputrc files.
>>
>> For example, a possible snippet of ~/.inputrc:
>>
>> $if cgdb
>> "\C-p": history-search-backward
>> "\C-n": history-search-backward
>> $endif
>>
>>
>> $ diff -ub ./various/rline/src/rline.c.old ./various/rline/src/rline.c
>> --- ./various/rline/src/rline.c.old     2008-09-26 01:57:43.000000000 -0400
>> +++ ./various/rline/src/rline.c 2008-09-26 03:23:13.000000000 -0400
>> @@ -96,6 +96,7 @@
>>    rline->rline_rl_last_func = NULL;
>>    rline->rline_rl_completion_query_items = rl_completion_query_items;
>>
>> +  rl_readline_name = "cgdb";
>>    rl_instream = rline->input;
>>    rl_outstream = rline->output;
>
> The future me committed this a week ago.

Hi Bob,

This email was a duplicate. I did not see this coming up in the
mailing list several days after I sent it, so I sent another one. Now
it did show up -- must be either sf.net or gmail's problem. Sorry
about that.

Best regards,

-- 
Kuang He

Re: [Cgdb-devel] Patch: enable people to make cgdb-specific customizations in ~/.inputrc

[Bob R. <bob...@co...>]

On Fri, Sep 26, 2008 at 03:28:08AM -0400, Kuang He wrote:
> Hi,
> 
> A small patch to enable people to make cgdb-specific customizations in
> their ~/.inputrc files.
> 
> For example, a possible snippet of ~/.inputrc:
> 
> $if cgdb
> "\C-p": history-search-backward
> "\C-n": history-search-backward
> $endif
> 
> 
> $ diff -ub ./various/rline/src/rline.c.old ./various/rline/src/rline.c
> --- ./various/rline/src/rline.c.old     2008-09-26 01:57:43.000000000 -0400
> +++ ./various/rline/src/rline.c 2008-09-26 03:23:13.000000000 -0400
> @@ -96,6 +96,7 @@
>    rline->rline_rl_last_func = NULL;
>    rline->rline_rl_completion_query_items = rl_completion_query_items;
> 
> +  rl_readline_name = "cgdb";
>    rl_instream = rline->input;
>    rl_outstream = rline->output;

The future me committed this a week ago.

Bob Rossi

Re: [Cgdb-devel] Bug: the default readline hotkeys Alt-X don't work in cgdb

[Bob R. <bob...@co...>]

On Fri, Sep 26, 2008 at 01:03:10PM -0400, Kuang He wrote:
> Hi Bob,
> 
> On Fri, Sep 26, 2008 at 10:08 AM, Bob Rossi <bob...@co...> wrote:
> > On Fri, Sep 26, 2008 at 03:21:59AM -0400, Kuang He wrote:
> I see from the mailing list archive that you've been meaning to
> release this for some time. Looking forward to it!

Yes, as soon as I hash out this issue I'll do a release.

> By the way, when I press CTRL-L in the gdb window, it does not clear
> the screen, but rather generates a new input line. Is this intended,
> or a bug?

This is intended, although, it's annoying, I must agree. It's because we
use readline with it's TERM set to "dumb". Perhaps I should have cgdb 
capture that specific key, and clear the window. I'll look into this as
well.

Bob Rossi