Re: Fullscreen Mode, Emacs 23 and OS X

Re: Fullscreen Mode, Emacs 23 and OS X

[Stefan Monnier]

> When I downloaded 23.1.1, I was surprised to discover that the little
> "mac" directory had disappeared.  Emacs 23 seems to be heading down
> the path of merging Mac OS X/OpenStep/GNUStep code.  To excerpt a
> section of etc/NEWS (from the emacs source distribution):

The original reason for the change was that nobody wanted to maintain
the "Carbon" port (i.e. the OSX code used in Emacs-22).  Now that we
switched, we have no intention to go back, so please help us improve the
NS code in Emacs-23 by reporting (via M-x report-emacs-bug) the problems
you encounter.


        Stefan

Re: Fullscreen Mode, Emacs 23 and OS X

[Steve Revilak]

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

srevilak> When I downloaded 23.1.1, I was surprised to discover that
srevilak> the little "mac" directory had disappeared.  Emacs 23 seems
srevilak> to be heading down the path of merging Mac OS
srevilak> X/OpenStep/GNUStep code.  To excerpt a section of etc/NEWS
srevilak> (from the emacs source distribution):

monnier> The original reason for the change was that nobody wanted to
monnier> maintain the "Carbon" port (i.e. the OSX code used in
monnier> Emacs-22).  Now that we switched, we have no intention to go
monnier> back, so please help us improve the NS code in Emacs-23 by
monnier> reporting (via M-x report-emacs-bug) the problems you
monnier> encounter.

Stefan,

Thanks for the nudge.  I have reported more bugs :)

Steve

[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]

Tracking Emacs Development (was: Fullscreen Mode, Emacs 23 and OS X)

[Steve Revilak]

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

srevilak> When I downloaded 23.1.1, I was surprised to discover that
srevilak> the little "mac" directory had disappeared.  Emacs 23 seems
srevilak> to be heading down the path of merging Mac OS
srevilak> X/OpenStep/GNUStep code.  To excerpt a section of etc/NEWS
srevilak> (from the emacs source distribution):

monnier> The original reason for the change was that nobody wanted to
monnier> maintain the "Carbon" port (i.e. the OSX code used in
monnier> Emacs-22).  Now that we switched, we have no intention to go
monnier> back, so please help us improve the NS code in Emacs-23 by
monnier> reporting (via M-x report-emacs-bug) the problems you
monnier> encounter.

srevilak> Thanks for the nudge.  I have reported more bugs :)

I'd like to ask a question on a more serious note.

To me, emacs is a very important piece of software, and I would like
to do what I can to help it improve.  

What is the best way to follow emacs development?  Just check out the
trunk [1] and rebuild on a regular basis?  Are there incremental
branches done between release versions?

Steve


[1] i.e. http://savannah.gnu.org/cvs/?group=emacs

[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]

Re: Tracking Emacs Development (was: Fullscreen Mode, Emacs 23 and OS X)

[Peter Dyballa]

Am 07.12.2009 um 03:27 schrieb Steve Revilak:

> What is the best way to follow emacs development?  Just check out the
> trunk [1] and rebuild on a regular basis?

Yes, and also trying to compile the sources differently to see how  
robust they are. I am using libraries from Fink and from MacPorts and  
see (or better: saw on Tiger, on Leopard I haven't had the opportunity  
yet to compile GNU Emacs) differences.

> Are there incremental branches done between release versions?


GNU Emacs versions are released...

--
Greetings

   Pete

Bake pizza not war!

Re: Tracking Emacs Development

[Stefan Monnier]

monnier> The original reason for the change was that nobody wanted to
monnier> maintain the "Carbon" port (i.e. the OSX code used in
monnier> Emacs-22).  Now that we switched, we have no intention to go
monnier> back, so please help us improve the NS code in Emacs-23 by
monnier> reporting (via M-x report-emacs-bug) the problems
monnier> you encounter.
srevilak> Thanks for the nudge.  I have reported more bugs :)

Thanks.

> To me, Emacs is a very important piece of software, and I would like
> to do what I can to help it improve.
> What is the best way to follow Emacs development?  Just check out the
> trunk [1] and rebuild on a regular basis?

Yes, that is ideal.  If you do that, you'll probably want to keep an eye
on emacs-devel@gnu.org (it's a fairly high-traffic list, tho), for known
breakage and things like that.

> Are there incremental branches done between release versions?

No.  We do have pretests, tho (the one for 23.2 will start
real-soon-now), so you could help a lot by trying out the pretests and
hammering on them to try and fix more bugs before the release.


        Stefan

Re: Tracking Emacs Development

[Steve Revilak]

[-- Attachment #1: Type: text/plain, Size: 816 bytes --]

srevilak> What is the best way to follow emacs development?  Just
srevilak> check out the trunk [1] and rebuild on a regular basis?

Peter_Dyballa> Yes, and also trying to compile the sources differently
Peter_Dyballa> to see how robust they are. I am using libraries from
Peter_Dyballa> Fink and from MacPorts and see (or better: saw on
Peter_Dyballa> Tiger, on Leopard I haven't had the opportunity yet to
Peter_Dyballa> compile GNU Emacs) differences.

monnier> Yes, that is ideal.  If you do that, you'll probably want to
monnier> keep an eye on emacs-devel@gnu.org (it's a fairly
monnier> high-traffic list, tho), for known breakage and things like
monnier> that.

Peter and Stefan,

Thank you for the suggestions.  I'll go back to building from the
trunk (and pretest versions, when they're available).

Steve

[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]