Re: [Cgdb-users] 'forward searching' and 'sending command next to debugger' have the same binding - 'n'

[Eugene V. L. <jac...@gm...>]

Bob Rossi wrote:
> On Sat, Dec 01, 2007 at 09:25:27AM +0200, Eugene V. Lyubimkin wrote:
>> Bob Rossi wrote:
>>> On Fri, Nov 30, 2007 at 10:03:52PM +0200, Eugene V. Lyubimkin wrote:
>>>> I noticed that key bindings for "send command 'next' to debugger" and
>>>> "next forward search in source window" are both - 'n'. I want to use
>>>> shortcuts, but therefore if I press 'n' gdb try to go the next line in
>>>> program, and I can't do a forward searching. Please fix it or provide a
>>>> workaround.
>>> Thanks for the report. Do you have any suggestions on what we could do
>>> to fix this problem? One suggestion I was given was to have the F1-F9
>>> keys handel the next/step/run functionality. Those are standardized on a
>>> lot of front ends.
>>>
>> Suggestion about F1-F9 seems good, anyway these keys aren't used now, 
>> are they?
>> But what do you think about changing 'forward search binding' key to 
>> 'y', for example? or 'w' - "forWard"?
> 
> OK, a little on how we got into this position. I added the shortcut keys
> I believe before we had the regex searching. 'n' seemed like the obvious
> key for 'next'. Then, I added the regex searching. A stated goal for
> CGDB is to have a similar feel, like vi/vim. So, the correct key for
> searching is 'n'. Now we had a collission. Along the way I had stopped
> using the shortcut keys. I was going to remove them from cgdb, but
> realized a lot of people had been using them.
> 
> So, I definately want to leave the next search as 'n'. However, I don't
> mind changing the shortcut keys, or adding another key  binding in
> shortcut mode that does the same thing.
> 
> With all of that said, the very next feature we plan to add to CGDB will
> be key mappings that allow you to bind a key to a particular piece of
> functionality. When that is done, you'll be able to map the
> functionality to whatever key you would like.
It will be great! :)
> 
> I'll add the F keys as a temporary solution, unless you can think of
> something immediately better.
Ok, this is also looks quite good.

-- 
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.