From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: 23.0.50; MacOS X 10.4: very slow visuals, multi-tty patch suspected
Date: Thu, 06 Sep 2007 12:33:41 -0500 [thread overview]
Message-ID: <m2sl5ru2a2.fsf@lifelogs.com> (raw)
In-Reply-To: 200709061715.l86HFHXx020325@oogie-boogie.ics.uci.edu
On Thu, 06 Sep 2007 10:15:17 -0700 Dan Nicolaescu <dann@ics.uci.edu> wrote:
DN> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Thu, 06 Sep 2007 09:10:09 -0700 Dan Nicolaescu <dann@ics.uci.edu> wrote:
>>
DN> No, it would be much more complex that just simply fixing the mac
DN> port. I think the input processing is simply not initialized
DN> correctly/completely. My guess is that it would be a few lines of code
DN> to fix this. But someone that cares about that platform would need to
DN> do the work.
>>
>> I think caring about MacOS shouldn't matter.
DN> Why not? Please explain.
You said this was "more complex than just fixing the mac port." I
understood it to mean that this is not necessarily just a MacOS bug, and
thus should not matter only to those who care about MacOS. If I
misunderstood, sorry. Also see below.
>> If the multi-tty merge brought in input processing bugs that are
>> only visible on MacOS, that doesn't mean they are only happening
>> on MacOS.
DN> Can you please explain what are you implying here?
Just because *any* bug only shows up on MacOS doesn't necessarily mean
it only happens on MacOS, or that it only matters on MacOS. You seem to
be saying that is the case for this particular bug. I'm sure you know
the internals much better than me, but you haven't said that it's known
to only matter on MacOS so I'm not assuming it. You said it was
reported before, that's all. I actually couldn't find that previous bug
report, so if you could point me to it I'd appreciate it.
Ted
next prev parent reply other threads:[~2007-09-06 17:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 10:02 23.0.50; MacOS X 10.4: very slow visuals, multi-tty patch suspected Ted Zlatanov
2007-09-06 10:15 ` Ted Zlatanov
2007-09-06 10:44 ` Nick Roberts
2007-09-06 14:14 ` Dan Nicolaescu
2007-09-06 15:45 ` Ted Zlatanov
2007-09-06 16:10 ` Dan Nicolaescu
2007-09-06 16:38 ` Ted Zlatanov
2007-09-06 17:15 ` Dan Nicolaescu
2007-09-06 17:33 ` Ted Zlatanov [this message]
2007-09-06 18:43 ` Dan Nicolaescu
2007-09-06 19:24 ` Ted Zlatanov
2007-09-06 20:02 ` David Kastrup
2007-09-06 20:16 ` Dan Nicolaescu
2007-09-07 2:45 ` Ted Zlatanov
2007-09-10 14:12 ` Ted Zlatanov
2007-09-25 14:36 ` Ted Zlatanov
2007-09-25 15:03 ` Jason Rumney
2007-09-25 16:53 ` Ted Zlatanov
2007-09-25 16:58 ` Ted Zlatanov
2007-09-25 20:43 ` Jason Rumney
2007-09-25 20:58 ` Ted Zlatanov
2007-09-25 23:50 ` YAMAMOTO Mitsuharu
2007-09-26 11:48 ` Ted Zlatanov
2007-09-26 5:44 ` Dan Nicolaescu
2007-09-26 7:35 ` Jason Rumney
2007-09-26 7:44 ` Jason Rumney
2007-09-26 9:19 ` Eli Zaretskii
2007-09-26 11:52 ` Ted Zlatanov
2007-09-26 5:42 ` Dan Nicolaescu
2007-09-06 21:08 ` Jason Rumney
2007-09-07 6:32 ` 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=m2sl5ru2a2.fsf@lifelogs.com \
--to=tzz@lifelogs.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 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.