Thread: [CEDET-devel] Speedbar info support bug?
Brought to you by:
zappo
From: Hannu K. <az...@ik...> - 2009-03-06 13:17:14
|
Hi, If speedbar is loaded, apparently TAB is bound to speedbar-next instead of Info-next-reference in Info-mode. Unfortunately speedbar-next seems to move line by line (whether the line has some random text or a cross-reference) and not from cross-reference to another. What is the purpose of speedbar-next? Is this a bug? Documentation says "Move to the next argth line in a speedbar buffer." and the speedbar frame contents match the cross-references in the buffer, so one might expect it to jump from cross-reference to another, but it doesn't do that. Current CEDET from CVS, Emacs(W32) 23.0.91 on Windows. -- Hannu |
From: Eric M. L. <er...@si...> - 2009-03-09 11:50:54
|
Hi, I don't have this behavior in my Emacs. I'm also running Emacs and CEDET from CVS. My TAB in an info buffer says Info-next-reference. Perhaps there is a window-focus problem when there is an open speedbar frame? Eric >>> Hannu Koivisto <az...@ik...> seems to think that: >Hi, > >If speedbar is loaded, apparently TAB is bound to speedbar-next >instead of Info-next-reference in Info-mode. Unfortunately >speedbar-next seems to move line by line (whether the line has some >random text or a cross-reference) and not from cross-reference to >another. > >What is the purpose of speedbar-next? Is this a bug? >Documentation says "Move to the next argth line in a speedbar >buffer." and the speedbar frame contents match the cross-references >in the buffer, so one might expect it to jump from cross-reference >to another, but it doesn't do that. > >Current CEDET from CVS, Emacs(W32) 23.0.91 on Windows. > -- Eric Ludlam: er...@si... Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net |
From: Hannu K. <az...@ik...> - 2009-03-09 18:19:40
|
"Eric M. Ludlam" <er...@si...> writes: > I don't have this behavior in my Emacs. I'm also running Emacs and > CEDET from CVS. My TAB in an info buffer says Info-next-reference. > Perhaps there is a window-focus problem when there is an open speedbar > frame? I stupidly forgot to test with -q -- it was a configuration issue, my speedbar-reconfigure-keymaps-hook function assumed that it would be run with speedbar-buffer being the current buffer. Sorry about that. -- Hannu |