... If I launch gdb this way I don't have any means to navigate through
previously executed gdb lines using M-p and M-n, but following a
(gdb) run
or
(gdb) continue
I can use M-p and M-n to recall previous R commands
If I launch gdb in other ways M-p and M-n function as expected. I
suppose there
is a confusion between gdb's M-p and ESS's M-p so that M-p only functions in
the ESS session.
I quite like running gdb using R's -d flag, but not being able to navigate
through the line history is sub-optimal. I'd be interested to hear if other
people running gdb this way encountered this problem and how they
resolved it.
This had a one line solution (section 19.3, page 216, gdb manual)
gdb> set history save on
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
