From: David Reitter <david.reitter@gmail.com>
To: Adrian Robert <adrian.b.robert@gmail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Christian Lynbech <christian@defun.dk>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Serious performance problem with process output on Mac OSX
Date: Tue, 30 Mar 2010 09:05:30 -0400 [thread overview]
Message-ID: <E24B1474-5FE8-48C6-8E59-ADC9164BE07A@gmail.com> (raw)
In-Reply-To: <D4265899-3CE2-42E3-873F-83F0ECC906DB@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Mar 30, 2010, at 3:43 AM, Adrian Robert wrote:
>> One other thing I noticed which looking through the code is that the
>> Nextstep port assigns a special value, `t', to frame-title-format, and
>> processes it specially. Is there any reason to do this? If not, I
>> think this should be removed; this looks like a misfeature to me, since
>> it is not compatible with the variable as documented and can confuse
>> other people's Lisp code.
>
> Ah, OK -- this variable and value was checked for in the code I moved in my patch, but I had no idea it was set specially by NS lisp code. I'll look into it.
IIRC, NS displays the file's name as the title and requires you to set it that way if drag&drop of the file proxy icons (displayed next to the name of the frame) is supposed to work. That's all standard functionality on NS or at least on the Mac. If the frame name is different, I think drag&drop doesn't work right. See xdisp.c:9503ff and also ns_set_name_as_filename() in nsfns.m.
Introducing a ns-* variable to override would confuse users (frame-title-format won't work as expected), but if we set the file name with this NS function iff ns-frame-title-format is "%f", then that would be consistent with the other platforms.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2010-03-30 13:05 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 15:22 MS-Windows build broken in Fmake_network_process Eli Zaretskii
2010-03-26 15:48 ` Helmut Eller
2010-03-26 17:56 ` Eli Zaretskii
2010-03-26 18:05 ` Helmut Eller
2010-03-26 18:09 ` Eli Zaretskii
2010-03-26 18:17 ` Helmut Eller
2010-03-26 20:05 ` Eli Zaretskii
2010-03-26 21:14 ` Helmut Eller
2010-03-27 8:50 ` Eli Zaretskii
2010-03-27 10:09 ` Helmut Eller
2010-03-27 11:11 ` Eli Zaretskii
2010-03-27 13:56 ` Helmut Eller
2010-03-27 0:48 ` Chong Yidong
2010-03-27 7:42 ` Eli Zaretskii
2010-03-27 16:49 ` Jason Rumney
2010-03-27 16:55 ` Eli Zaretskii
2010-03-27 22:28 ` Christoph
2010-03-28 0:12 ` Florian Beck
2010-03-28 0:37 ` Óscar Fuentes
2010-03-28 7:26 ` Eli Zaretskii
2010-03-28 18:55 ` Chong Yidong
2010-03-28 20:10 ` Eli Zaretskii
2010-03-28 23:23 ` Jason Rumney
2010-03-29 23:39 ` Richard Stallman
2010-03-31 4:57 ` Stephen J. Turnbull
2010-03-31 8:38 ` Eli Zaretskii
2010-03-31 10:38 ` Juanma Barranquero
2010-03-31 11:19 ` Eli Zaretskii
2010-03-31 15:39 ` Stephen J. Turnbull
2010-03-31 16:39 ` Juanma Barranquero
2010-03-31 17:30 ` Stephen J. Turnbull
2010-03-31 17:36 ` Juanma Barranquero
2010-03-31 18:05 ` OT: (was: MS-Windows build broken in Fmake_network_process) Stefan Monnier
2010-03-31 15:28 ` MS-Windows build broken in Fmake_network_process Stephen J. Turnbull
2010-03-31 16:12 ` Eli Zaretskii
2010-03-31 16:59 ` Stephen J. Turnbull
2010-03-31 17:27 ` Eli Zaretskii
2010-03-31 18:08 ` Stephen J. Turnbull
2010-04-06 7:50 ` David Kastrup
2010-04-07 3:21 ` Richard Stallman
2010-04-07 7:59 ` David Kastrup
2010-03-28 0:39 ` Christoph
2010-03-28 7:21 ` Windows 9X compatibility Eli Zaretskii
2010-03-28 14:59 ` Óscar Fuentes
2010-03-28 15:24 ` Lennart Borgman
2010-03-28 15:56 ` Eli Zaretskii
2010-03-28 16:09 ` Juanma Barranquero
2010-03-28 18:03 ` joakim
2010-03-29 23:39 ` Richard Stallman
2010-03-28 19:57 ` Óscar Fuentes
2010-03-28 20:32 ` Eli Zaretskii
2010-03-28 22:26 ` Juanma Barranquero
2010-03-28 19:27 ` Christoph
2010-03-28 20:18 ` Eli Zaretskii
2010-03-28 21:04 ` Christoph
2010-03-28 7:17 ` Windows 9X compatibility (was: MS-Windows build broken in Fmake_network_process) Eli Zaretskii
2010-03-28 7:33 ` MS-Windows build broken in Fmake_network_process Jason Rumney
2010-03-28 8:12 ` Eli Zaretskii
2010-03-29 23:39 ` Richard Stallman
2010-03-28 9:11 ` Serious performance problem with process output on Mac OSX Christian Lynbech
2010-03-28 14:41 ` Adrian Robert
2010-03-29 21:58 ` Adrian Robert
2010-03-29 23:26 ` David Reitter
2010-03-29 23:54 ` Chong Yidong
2010-03-30 7:43 ` Adrian Robert
2010-03-30 13:05 ` David Reitter [this message]
2010-03-30 17:39 ` Jimmy Yuen Ho Wong
2010-03-30 17:47 ` Chong Yidong
2010-03-31 2:38 ` Jimmy Yuen Ho Wong
2010-03-31 4:00 ` Chong Yidong
2010-03-31 13:41 ` Jimmy Yuen Ho Wong
2010-03-31 14:28 ` Chong Yidong
2010-03-31 14:29 ` Adrian Robert
2010-03-29 23:48 ` MS-Windows build broken in Fmake_network_process Davis Herring
2010-03-30 5:41 ` Jason Rumney
2010-03-26 23:03 ` Juanma Barranquero
2010-03-27 0:51 ` YAMAMOTO Mitsuharu
2010-03-27 8:44 ` Eli Zaretskii
2010-03-27 13:01 ` Óscar Fuentes
2010-03-27 13:18 ` Juanma Barranquero
2010-03-28 17:29 ` Kim F. Storm
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=E24B1474-5FE8-48C6-8E59-ADC9164BE07A@gmail.com \
--to=david.reitter@gmail.com \
--cc=adrian.b.robert@gmail.com \
--cc=christian@defun.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
/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).