Looks like output to *slime-repl* forces the cursor to the end. When compiling this is annoying because I wish to read notes as they appear and have control of where in the buffer I am looking. I believe that ilisp only scrolled when the cursor was aleady at the end of the buffer, which is a prefered method of operation. Thanks, William Halliburton Just a note: If left alone I will probably get annoyed enough to fix it myself soon.
"William" == William C Halliburton <will@licentiae.com>: William> Looks like output to *slime-repl* forces the cursor to the William> end. When compiling this is annoying because I wish to read William> notes as they appear and have control of where in the buffer I William> am looking. I believe that ilisp only scrolled when the cursor William> was aleady at the end of the buffer, which is a prefered William> method of operation.
Funny -- I was about to report that for me it doesn't force it to the end, it forces it to one or more prompts _before_ the end. The more I evaluate (C-M-x), the more prompts I have left between the cursor and the end of the *slime-repl* buffer. Which seems to be an obvious bug. That's using XEmacs, BTW. --J.
Jan Rychter <jan@rychter.com> writes:
Funny -- I was about to report that for me it doesn't force it to the end, it forces it to one or more prompts _before_ the end. The more I evaluate (C-M-x), the more prompts I have left between the cursor and the end of the *slime-repl* buffer. Which seems to be an obvious bug. That's using XEmacs, BTW.
Does this happen when you press C-M-x in the slime-repl buffer? C-M-x in the slime-repl was bound accidentally bound to lisp-eval-defun and not slime-eval-defun. I've changed that, but C-M-x in the slime-repl is not that useful at the moment, because it usually sends the prompt to Lisp. Needs a bit more work. Helmut.
"Helmut" == Helmut Eller <e9626484@stud3.tuwien.ac.at>: Helmut> Jan Rychter <jan@rychter.com> writes: Funny -- I was about to report that for me it doesn't force it to the end, it forces it to one or more prompts _before_ the end. The more I evaluate (C-M-x), the more prompts I have left between the cursor and the end of the *slime-repl* buffer. Which seems to be an obvious bug. That's using XEmacs, BTW.
Helmut> Does this happen when you press C-M-x in the slime-repl buffer? [...] No, it happens when I use C-M-x in a lisp buffer. An example of what I mean: -- start XEmacs -- M-x slime: now I have two windows, top one being *inferior-lisp*, bottom one *slime-repl* -- "C-x o" to go to the top window -- open a lisp buffer -- "C-c C-k" to compile it -- after compilation, the bottom *slime-repl* buffer doesn't scroll to the bottom. When I do a "C-x o", the point is placed after the _first_ CL-USER> prompt, with all the compiler messages after that. Which means I have to manually "M->" to get a usable REPL. Does this explain better what I mean? --J.
"William C. Halliburton" <will@licentiae.com> writes:
Looks like output to *slime-repl* forces the cursor to the end. When compiling this is annoying because I wish to read notes as they appear and have control of where in the buffer I am looking. I believe that ilisp only scrolled when the cursor was aleady at the end of the buffer, which is a prefered method of operation.
I've changed this in CVS. Thanks. Helmut.
participants (3)
-
Helmut Eller -
Jan Rychter -
William C. Halliburton