> Nick> Is it a new problem? i.e. did it work previously? > > Yes and yes
Then I think it's due to the recent changes in eval-after-load not gdb-ui. > >> I could trace this down to the following lines in my .emacs file: > >> (eval-after-load "gdb-ui" > >> '(progn > >> (message "Configuring gdb-ui") > >> ;(setq gdb-show-main t) > >> ;(setq gdb-many-windows t) > >> ;(setq gdb-use-separate-io-buffer t) > >> )) > Nick> > Nick> I think you should do: > Nick> > Nick> (add-hook 'gdb-mode-hook > Nick> '(lambda () > Nick> (message "Configuring gdb-ui") > Nick> (setq gdb-show-main t) > Nick> (setq gdb-many-windows t) > Nick> (setq gdb-use-separate-io-buffer t))) > > Yes I know that there are different ways to configure the variables for > gdb-ui. But I believe that this simple eval-after-load (especially with all > settings commented out) shouldn't break gdb. Besides why should I do it in a > hook that is run every time I call gdb, when configuring it once should be > enough. Timing. Do you know when and where gdb-ui gets loaded? Its in the middle of gud-filter, if you start with M-x gdb. Gdb-mode-hook always runs at the end of `gdb'. That said, I don't know why eval-after-load shouldn't work (and clearly at one time it did. It just seems safer. -- Nick http://www.inet.net.nz/~nickrob _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
