From: David Reitter <david.reitter@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Seiji Zenitani <zenitani@mac.com>, emacs-devel@gnu.org
Subject: Re: [OS X] Title bar icon
Date: Mon, 27 Aug 2007 08:47:34 +0100 [thread overview]
Message-ID: <08247AD2-3118-4D5D-9FF5-EAA1DE15AC5F@gmail.com> (raw)
In-Reply-To: <wlabsdhlmg.wl%mituharu@math.s.chiba-u.ac.jp>
[-- Attachment #1.1: Type: text/plain, Size: 815 bytes --]
On 27 Aug 2007, at 01:22, YAMAMOTO Mitsuharu wrote:
> Switching to the minibuffer normally causes several visual changes in
> the menu bar and the tool bar. Even the title bar string will change
> under multiple frame environments by default. I don't think the proxy
> icon change attracts more user's attention than these changes.
Correct. Why not change this behavior completely?
Displaying *Minibuf-1* as title of the frame is confusing, because
this title is supposed to indicate the "document" shown in the frame,
which translates to the buffer in the biggest or last activated
window, but not whether a secondary input field (i.e., minibuffer) is
selected.
It would be much better if the frame title didn't change at all when
entering or exiting the minibuffer. This includes the proxy icon.
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-08-27 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 15:55 [OS X] Title bar icon Seiji Zenitani
2007-08-27 0:22 ` YAMAMOTO Mitsuharu
2007-08-27 1:45 ` Seiji Zenitani
2007-08-27 7:47 ` David Reitter [this message]
2007-08-27 8:57 ` YAMAMOTO Mitsuharu
2007-08-27 18:37 ` David Reitter
2007-08-27 3:07 ` Richard Stallman
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=08247AD2-3118-4D5D-9FF5-EAA1DE15AC5F@gmail.com \
--to=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=zenitani@mac.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.