Your message dated Thu, 23 Jan 2014 04:27:09 +0000 with message-id <[email protected]> and subject line Closing old emacs21 bugs has caused the Debian Bug report #216609, regarding bury-buffer inconsistent: won't display unburied *Man xxx* buffers; breaks buffer stacking/popping to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 216609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216609 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: emacs21 Version: 20.7-13.1 The bury-buffer command works inconsistently. Normally, burying a buffer displays the next buffer (the buffer that was just "below" the buffer that was buried). However, if the next buffer is a manual page buffer (*Man xxx*), bury-buffer refuses to display it, instead displaying the next non-manual-page buffer. 1. This behavior is internally inconsistent as shown above. 2. This behavior is inconsistent with other commands in Emacs. Consider this: - open file A - open file B - open file C - delete the buffer for file C - you're back to file B Note how the stacking behavior helps you keep track of things. When you're done with the top of the stack, you can get rid of it and return to whatever the previous item was. For most files, bury-buffer works similarly: - open file A - open file B - open file C - bury the buffer for file C - you're back to file B Now consider manual pages: Deleting buffers works consistently: - view manual page A - view manual page B - view manual page C - delete the buffer for manual page C - you're back to manual page B. However, the combination of bury-buffer and manual pages screws up the stack-popping feature: - view manual page A - view manual page B - view manual page C - bury delete the buffer for manual page C - you're NOT back to manual page B; you're back to whatever was there before manual page A (unless that is a manual page buffer, in which case...) The bury-buffer behavior is also inconsistent with the "b" command in *Buffer List*. 3. This behavior prevents the user from using the buffer-stacking feature and the bury-buffer command with manual page buffers. For example: - I see a list of commands. - I open manual page buffers on all of them. - When I'm done reading the last one I opened, I want to return to the next one on the buffer stack (the second-to-last one I opened). - I do bury-buffer. - My second-to-last manual page is not displayed. In fact, I can bury buffers all day long and the manual page buffers NEVER show up. I assume that Emacs developer didn't like burying code buffers to "unbury" and display manual pages, and grossly hacked Emacs for his or her own whim without ever considering the irregularity or that it would break other people's usage. This should be fixed, or it should be easily configurable and the the documentation should say how to configure it. (The bury-buffer command is completely undocumented in the Emacs info pages. describe-function on bury-buffer and other-buffer says nothing about the irregular behavior.) Daniel -- Daniel Barclay [email protected]
--- End Message ---
--- Begin Message ---Hi! I'm closing this bug, since it affected emacs21, and the current version is 23. If you still encounter this problem, please feel free to re-open it and move it to the appropriate package, or ask me to do it. Solveig
--- End Message ---
