unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Carbon port and multi-tty
Date: Tue, 06 May 2008 22:55:12 -0700	[thread overview]
Message-ID: <200805070555.m475tCRi004681@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <wly76mwvwd.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Wed, 07 May 2008 14:00:50 +0900")

YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:

  > >>>>> On Tue, 06 May 2008 21:28:37 -0700, Dan Nicolaescu <dann@ics.uci.edu> said:
  > 
  > >> It actually introduced a bug in the part that is unrelated to
  > >> multi-tty.
  > 
  > > Please show us the exact bug, and I'll fix it or back out the
  > > change.  Had this information been available, this would have
  > > happened a year ago.
  > 
  > The change corresponds to this entry:
  > 
  > 2007-08-29  Dan Nicolaescu  <dann@ics.uci.edu>
  > 
  > 	(Fx_create_frame): Fix doc string.  Rename the parameter.  Set the
  > 	frame parameters following what is done in X11 and w32.
  > 
  > Actually the comment was not right.  This has changed the Mac code
  > from what is done in X11 to what is done in W32.

You mean the ChangeLog entry?  I used both X11 and w32 as inspiration.
There was an incorrect comment talking about an inexistent ALIST
parameter that the original patch fixed.

  > The bug introduced by this change is mentioned here:
  > http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg01069.html

OK, a 1 line change (in a ~1000 lines patch) that you seemed to have
known about for a while.

Interesting choice of action: raising all this hell instead of just
fixing it.  Fine, if your judgment tells you such a behavior is wise...

  > And the following change is totally unrelated to multi-tty.
  > 
  > 	(mac_window): Add 2 new parameters for consistency with other systems.
  > 
  > Again, the comment was not right.  The X11 counterpart (x_window) has
  > several versions, one of which has only one argument as in the
  > original mac_window.

This has not functional value, just esthetic, it has zero effect on
functionality.  I changed it anyway.

  > There might be others, but the above is what I could find.

Please find them, if they actually exist.




  reply	other threads:[~2008-05-07  5:55 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 16:55 Carbon port and multi-tty Chong Yidong
2008-05-06 17:49 ` Ted Zlatanov
2008-05-06 22:08 ` YAMAMOTO Mitsuharu
2008-05-07  1:58   ` Stefan Monnier
2008-05-07  2:36     ` YAMAMOTO Mitsuharu
2008-05-07  2:37       ` YAMAMOTO Mitsuharu
2008-05-07  3:13       ` Stefan Monnier
2008-05-07  3:18         ` YAMAMOTO Mitsuharu
2008-05-07  3:52           ` Nick Roberts
2008-05-07  4:01             ` YAMAMOTO Mitsuharu
2008-05-07  4:26               ` Stefan Monnier
2008-05-07  6:00             ` David Kastrup
2008-05-07  8:50             ` Eli Zaretskii
2008-05-07  4:28           ` Dan Nicolaescu
2008-05-07  5:00             ` YAMAMOTO Mitsuharu
2008-05-07  5:55               ` Dan Nicolaescu [this message]
2008-05-07  6:10                 ` YAMAMOTO Mitsuharu
2008-05-07  6:40                   ` David Kastrup
2008-05-07  6:47                     ` YAMAMOTO Mitsuharu
2008-05-07  7:56                       ` Stephen J. Turnbull
2008-05-07  8:42                         ` David Kastrup
2008-05-07  9:41                           ` Eli Zaretskii
2008-05-07 10:05                             ` David Kastrup
2008-05-07 10:26                               ` Eli Zaretskii
2008-05-07 10:51                                 ` David Kastrup
2008-05-07 13:40                                   ` Eli Zaretskii
2008-05-07 13:53                                     ` David Kastrup
2008-05-08  8:44                                 ` Richard M Stallman
2008-05-08  8:56                                   ` David Kastrup
2008-05-08 10:01                                     ` Eli Zaretskii
2008-05-08 10:11                                       ` David Kastrup
2008-05-08  9:53                                   ` Eli Zaretskii
2008-05-09 11:13                                     ` Richard M Stallman
2008-05-07 10:07                           ` YAMAMOTO Mitsuharu
2008-05-07 10:16                             ` David Kastrup
2008-05-07 10:32                               ` YAMAMOTO Mitsuharu
2008-05-07  7:15                   ` Dan Nicolaescu
2008-05-08  0:21                     ` YAMAMOTO Mitsuharu
2008-05-08  1:03                       ` Dan Nicolaescu
2008-05-08  1:25                         ` YAMAMOTO Mitsuharu
2008-05-08  2:07                       ` Stefan Monnier

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=200805070555.m475tCRi004681@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    --cc=monnier@iro.umontreal.ca \
    /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).