0

I am reading this function and still don't see why it doesn't delete both the buffer and window. Currently it open a new window, and when I hit C-g another buffer (even duplicated to the one I am editing) appears in that window, created unwanted layout. See attach screenshot.

enter image description here

What I want is to get the window behavior like *Help buffer when one calls M-x describe-key for example: It opens its own window, move focus there, and closes it when I hit q or C-g.

0

For now I change (kill-buffer buf) in the following section to (delete-window-on buf):

From:

(when (and (commandp command)
                   (bufferp buf)
                   (or (not (symbolp command)) ;; kill on lambdas
                       (not (string-match "window" (symbol-name command)))))
          (kill-buffer buf)) ;; bury does not work here :( (Emacs bug?)

To this:

(when (and (commandp command)
                   (bufferp buf)
                   (or (not (symbolp command)) ;; kill on lambdas
                       (not (string-match "window" (symbol-name command)))))
          (delete-window-on buf)) ;; bury does not work here :( (Emacs bug?)

Still feel the window created by describe-object-at-point is too intrusive. It should be like "*Help*" window. But I don't have time to dig more into this right now.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.