unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adrian Robert <adrian.b.robert@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "emacs.app dev list" <emacs-app-dev-@lists.sourceforge.net>,
	David Reitter <david.reitter@gmail.com>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: [Emacs.app dev]: Emacs.app now in GNU Emacs CVS
Date: Tue, 15 Jul 2008 23:01:18 -0400	[thread overview]
Message-ID: <7A6F7386-15AB-404E-A8ED-1D3AF46FE982@gmail.com> (raw)
In-Reply-To: <jwv8ww2a9ef.fsf-monnier+emacs@gnu.org>


On Jul 15, 2008, at 9:49 PM, Stefan Monnier wrote:

>>> easy-mmode IS needed, right now.
>
> That seems wrong.  Can you explain why you think it's needed?

OK, it seems it's NOT needed.  I was confused since it looked like  
define-minor-mode was defined in easy-mmode.  Hmm..  Anyway, my bad.   
Removed in CVS.

HOWEVER, others are still getting problems with define-minor-mode  
calls in ns-win where I am not.  It would be interesting to know why  
ns-win is special, since define-minor-mode is called in many other  
lisp files that are loaded from loadup.el.


> PS: Furthermore, it was not mentioned in the ChangeLog:
>
> 	* loadup.el: Load ns-win.el if ns-windowing is active.
>
> ...
> You need to be more careful with your ChangeLog entries.

I was trying to be brief.  ;-)

Seriously, I wasn't sure what balance to strike between detail and not  
writing a novel, but I'll go back and edit whatever desired.

Regarding Glenn's suggestion of adding ns-win.el and friends to  
SOME_MACHINE_LISP, it appears that the only GUI that does this is X.   
Should all three of w32-win, mac-win, and ns-win be added?






  reply	other threads:[~2008-07-16  3:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <476AEFF3-F98D-4D19-A8B0-219C790536F7@gmail.com>
     [not found] ` <19e566510807151217q7276dd61wa93aaa13b842e296@mail.gmail.com>
     [not found]   ` <170476C2-EF90-40DC-BB6F-0C54AFA10884@gmail.com>
     [not found]     ` <64B63861-E635-420F-BC96-8DA189246E72@gmail.com>
2008-07-16  0:23       ` [Emacs.app dev]: Emacs.app now in GNU Emacs CVS David Reitter
2008-07-16  1:09         ` Glenn Morris
2008-07-16  5:22           ` David Reitter
2008-07-16  6:18             ` CHENG Gao
2008-07-16 12:36             ` Adrian Robert
2008-07-16  1:49         ` Stefan Monnier
2008-07-16  3:01           ` Adrian Robert [this message]
2008-07-16  3:09             ` Cezar Halmagean
2008-08-09 18:36               ` Peter Dyballa
2008-07-16  4:15             ` CHENG Gao
2008-07-16  2:03         ` Seiji Zenitani
2008-07-16  3:06         ` Miles Bader
2008-07-16  6:28           ` Miles Bader
2008-07-16  6:36             ` Miles Bader
2008-07-16 17:54             ` Yavor Doganov
     [not found]             ` <87tzepiuk0.GNU\'s_Not_Unix!%yavor@gnu.org>
2008-07-17 19:03               ` Adrian Robert

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=7A6F7386-15AB-404E-A8ED-1D3AF46FE982@gmail.com \
    --to=adrian.b.robert@gmail.com \
    --cc=david.reitter@gmail.com \
    --cc=emacs-app-dev-@lists.sourceforge.net \
    --cc=emacs-devel@gnu.org \
    --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).