From: martin rudalics <rudalics@gmx.at>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 11298@debbugs.gnu.org
Subject: bug#11298: Recipe to surface *code-conversion-work* buffer
Date: Tue, 24 Apr 2012 13:39:25 +0200 [thread overview]
Message-ID: <4F9690ED.4020905@gmx.at> (raw)
In-Reply-To: <817gx5iehn.fsf@gmail.com>
>> This is my little excursion in to killing *scratch* (to death?)
>
> Now I am wondering whether:
> 1. *scratch* buffer re-generates itself
It does because Emacs needs at least one buffer it can display.
> 2. Why some buffers like *code-conversion-work* (and other internal
> buffers like "Minibuf", "Echo Area") gets /surfaced/ in some buffer
> listings, but totally disappears in the next buffer listing.
Usually they are not displayed because their names start with a space.
> For want of better place to put this, I am attaching it to *scratch*
> buffer bug report.
>
> Read on.
>
> Steps to reproduce:
> ------------------
>
> 1. Emacs -Q
> 2. C-x b TAB gives me
> ,----
> | Click <mouse-2> on a completion to select it.
> | In this buffer, type RET to select the completion near point.
> |
> | Possible completions are:
> | *Messages*
> `----
> 3. C-g. Now you are in *scratch*
> 4. Kill *scratch* => *Messages* shows up
> 5. Kill *Messages* => *Completions* shows up
> 6. Kill *Completions* => *scratch* shows up
>
> Now I get confused. Why does *scratch* show up again. Didn't I kill
> it before?
Because when you killed the last other buffer whose name didn't start
with a space, *scratch* got regenerated.
> 7. C-x b TAB TAB gets me this
> ,----
> | Click <mouse-2> on a completion to select it.
> | In this buffer, type RET to select the completion near point.
> |
> | Possible completions are:
> | *Echo Area 0* *Echo Area 1*
> | *Minibuf-0* *Minibuf-1*
> | *code-conversion-work*
> `----
>
> I choose to examine *code-conversion-work*. The name seems
> interesting. This is what I see there when I visit it:
>
> ,----
> | c:/Program Files/emacs-24.0.95/lisp/emacs-lisp/easymenu.elc
> `----
>
Usually, buffers whose names start with a space are not proposed. But
since you killed all other buffers what do you want Emacs to propose?
> 8. C-x b TAB now shows
> ,----
> | Click <mouse-2> on a completion to select it.
> | In this buffer, type RET to select the completion near point.
> |
> | Possible completions are:
> | *Completions*
> | *Messages*
> | *scratch*
> `----
>
> Note that special buffers that show up in step 7 has disappeared.
Because these buffer have been recreated in the meantime.
Is there anything bad about the behavior you observed?
martin
next prev parent reply other threads:[~2012-04-24 11:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 15:55 bug#11298: 24.0.95; (WISH) Re-look scratch buffers Jambunathan K
2012-04-21 19:53 ` Stefan Monnier
2012-04-21 20:50 ` Jambunathan K
2012-04-22 14:11 ` Richard Stallman
2012-04-24 10:21 ` Jambunathan K
2012-04-23 19:39 ` Stefan Monnier
2012-04-23 20:09 ` Lennart Borgman
2012-04-23 20:11 ` Drew Adams
2012-04-24 1:39 ` Stefan Monnier
2012-04-24 13:42 ` Drew Adams
2012-04-24 10:57 ` bug#11298: Recipe to surface *code-conversion-work* buffer Jambunathan K
2012-04-24 11:39 ` martin rudalics [this message]
2012-04-24 12:54 ` Jambunathan K
2012-04-24 12:20 ` bug#11298: Scratch buffer (Summary of Xah's proposals, as I see it) Jambunathan K
2012-04-24 12:31 ` Jambunathan K
2012-04-24 13:48 ` martin rudalics
2012-04-24 16:33 ` Jambunathan K
2012-04-24 14:17 ` Jan D.
2012-04-24 16:26 ` Jambunathan K
2012-04-25 12:33 ` Jan D.
2012-04-24 18:42 ` Stefan Monnier
2013-11-15 5:06 ` bug#11298: 24.0.95; (WISH) Re-look scratch buffers Jambunathan K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F9690ED.4020905@gmx.at \
--to=rudalics@gmx.at \
--cc=11298@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.