unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Seiji Zenitani <zenitani@mac.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: emacs-devel@gnu.org
Subject: Re: [OS X] Title bar icon
Date: Sun, 26 Aug 2007 21:45:45 -0400	[thread overview]
Message-ID: <3E48581A-0908-42D9-92B3-C2C31A63BAF4@mac.com> (raw)
In-Reply-To: <wlabsdhlmg.wl%mituharu@math.s.chiba-u.ac.jp>

On 2007/08/26, at 20:22, YAMAMOTO Mitsuharu wrote:

>>>>>> On Sun, 26 Aug 2007 11:55:11 -0400, Seiji Zenitani  
>>>>>> <zenitani@mac.com> said:
>
>> Hi, When visiting a file, the Carbon (OS X) port displays a small
>> proxy icon in the window title bar, like other OS X applications.
>
>> However, the proxy icon disappears when the cursor temporary visits
>> the mini buffer (i.e. saving the buffer to another file by C-x C-w),
>> often enough to attract the user's attention.
>
> 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.
>
Thanks for your response.  Both the menu bar change and the tool bar  
change (dimming out) are quite reasonable, while I feel uncomfortable  
with the proxy icon change.

But I agree that the proxy icon should be updated in the mini  
buffer.  As you pointed out, my proposal will introduce inconsistency  
under multiple frame environments -- it is easy to delete the buffer,  
which is related to the proxy icon in other frame.

Seiji Zenitani
zenitani@mac.com

  reply	other threads:[~2007-08-27  1:45 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 [this message]
2007-08-27  7:47   ` David Reitter
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E48581A-0908-42D9-92B3-C2C31A63BAF4@mac.com \
    --to=zenitani@mac.com \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).