Helmut - hacking the readtable to remember source-locations was a stroke of genius! It's great to see that "place compiler note inside nasty backquote form" test-case finally pass. Very cool :-) -Luke
Luke Gorrie <luke@bluetail.com> writes:
Helmut - hacking the readtable to remember source-locations was a stroke of genius! It's great to see that "place compiler note inside nasty backquote form" test-case finally pass. Very cool :-)
Thanks for the praise. Do you think we should add an extra buffer to browse the compiler notes? Lispworks has a something like that. There you can sort the compiler conditions by filename, by severity, or by something else I don't remember now. This would also be useful for notes without a good source location. Helmut.
"Helmut" == Helmut Eller <e9626484@stud3.tuwien.ac.at> writes: Helmut> Luke Gorrie <luke@bluetail.com> writes: Helmut - hacking the readtable to remember source-locations was a stroke of genius! It's great to see that "place compiler note inside nasty backquote form" test-case finally pass. Very cool :-)
Helmut> Thanks for the praise. Helmut> Do you think we should add an extra buffer to browse the Helmut> compiler notes? Lispworks has a something like that. There Helmut> you can sort the compiler conditions by filename, by severity, Helmut> or by something else I don't remember now. This would also be Helmut> useful for notes without a good source location. I'll mention a related item from my personal wishlist. I'd like all windows popped-up by SLIME to have electric keybindings, with "p" and "n" moving to the previous and next item, respectively (highlighting it, too), "q" _always_ closing the window (returning me where I was) and RET doing the Right Thing. This applies to apropos windows, description windows, compiler note lists, and any other window that is automatically opened (and possibly contains a list). Obviously it doesn't fully apply to the restart prompt, as there is no Right Thing to do, so "q" would not work -- still, I'd like to navigate the list of restarts by using "p" and "n", with the current entry highlighted. This would go a long way towards increasing usability. I'm always annoyed when a window pops up, my point is placed in it, and pressing "q" self-inserts, which means I have to "C-x o C-x 1". Actually, now that I think of it, a rule of thumb for Emacs usability design could be "if the user has to press "C-x 1", you've done something wrong. --J.
While we're on the subject of usability, Slime is now annoyingly insistent about popping up the compile window in the current frame, even when it's already visible in another window, and even when you've tried to suppress it. e.g. reading mail during a compile, it will repeatedly replace the message buffer. I suggest one of two changes, but prefer the first: * pop the compile buffer up once for any compile command, rather than doing so on any output. * change the comint-output-filter-functions function we add to use "(get-buffer-window (current-buffer) t)" instead of "(get-buffer-window (current-buffer)" so that it will find the buffer in another frame. /s
participants (4)
-
Helmut Eller -
Jan Rychter -
Luke Gorrie -
Sean O'Rourke