GNU bug report logs -
#4059
Several other problems in gdb-mi [RE: bug#3794: Error in json from gdb-ui]
Previous Next
Full log
Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
[Message part 1 (text/plain, inline)]
> > 6. Completion should be done with the emacs completion feature,
> > i.e. try-completion, completing-read etc.
>
> Do you mean the completion of commands in GUD buffer?
Yes. Currently, completion behaves like this (the vertical bar `|'
indicates the cursor):
(gdb) b redis| ;; Hit TAB.
b redisplay_dont_pause
b redisplay_interface
b redisplay_internal
b redisplay_mode_lines
b redisplay_performed_directly_p
b redisplay_preserve_echo_area
b redisplay_window
b redisplay_window_0
b redisplay_window_1
b redisplay_window_error
b redisplay_windows
b redisplaying_p
(gdb) b redisplay | ;; There is an extra space character
;; after `redisplay'. This seems to
;; be due to `redisplay' being an
;; available completion.
Previously, completion in gdb is done this way:
(gdb) b redis| ;; Hit TAB.
(gdb) b redisplay| ;; The first time TAB is hit,
;; completes to that match.
(gdb) b redisplay| ;; Hit TAB again.
(gdb) b redisplay| ;; And the *Completions* window is
;; popped up to show all available
;; completions.
At that point, the user can type RET to accept `redisplay' as the
match, or type more characters and then try other completions.
Regards,
Guanpeng Xu
_________________________________________________________________
Share your memories online with anyone you want.
http://www.microsoft.com/middleeast/windows/windowslive/products/photos-share.aspx?tab=1
[Message part 2 (text/html, inline)]
This bug report was last modified 14 years and 241 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.