leopard emacs has carbon support built in

[D P Schreber]

The /usr/bin/emacs that comes with Leopard includes carbon support.
That doesn't mean you can invoke directly and get a graphic version,
at least not that I can see. It does mean you don't have to depend on
random builds of carbon emacs that are floating around the web, and
you don't have to build it yourself.

All you have to do is get a copy of the barebones Emacs.app bundle
from emacs.org and then

cp /usr/bin/emacs Emacs.app/Contents/MacOS/Emacs

[a hard link will also work]

Voila, a current graphic emacs that shares all the same libraries etc
with the standard installation.

[Dave Peck]

Um, care to be more specific? What "emacs.app" bundle are you
referring to? There is no such thing as "emacs.org"

I'm calling shenanigans on your post until you give more details.

Cheers,
Dave

[D P Schreber]

On 2007-11-05, Dave Peck <dave...@gmail.com> wrote:
> Um, care to be more specific? What "emacs.app" bundle are you
> referring to? There is no such thing as "emacs.org"
>
> I'm calling shenanigans on your post until you give more details.

As you should :)

Sorry about haste-makes-waste post.

First, that should have been gnu.org, not emacs.org.

Second, the application bundle. Carbon emacs is an osx application
bundle of the usual sort, with some resources etc and a place to put
the executable. Usually it's called Emacs.app. Some of the ones
floating around the web contain a full emacs distribution: copies of
all the stuff that also lives in /usr/share/emacs. This is what you
can now ignore. All you need now is the most minimal bundle:

Emacs.app
Emacs.app/Contents
Emacs.app/Contents/Info.plist
Emacs.app/Contents/MacOS
Emacs.app/Contents/MacOS/Emacs <<< copy of /usr/bin/emacs goes here
Emacs.app/Contents/PkgInfo
Emacs.app/Contents/Resources
Emacs.app/Contents/Resources/Emacs.icns
Emacs.app/Contents/Resources/Emacs.rsrc
Emacs.app/Contents/Resources/English.lproj
Emacs.app/Contents/Resources/English.lproj/InfoPlist.strings

You can get this minimal bundle from the emacs cvs tree:

cvs -z3 -d:pserver:anon...@cvs.savannah.gnu.org:/sources/emacs co emacs/mac/Emacs.app

The checkout will have everything except Contents/MacOS/Emacs, so it's
ideal:

- do the checkout
- cd emacs/mac/Emacs.app/Contents/MacOS
- cp [or ln if you prefer] /usr/bin/emacs Emacs

You're done: emacs/mac/Emacs.app can now be run as a Mac application
in Leopard.

[Warren Oates]

In article <1194241245.3...@v29g2000prd.googlegroups.com>,
Dave Peck <dave...@gmail.com> wrote:

> Um, care to be more specific? What "emacs.app" bundle are you
> referring to? There is no such thing as "emacs.org"
>
> I'm calling shenanigans on your post until you give more details.

I think he means:

http://sourceforge.net/projects/emacs-app

I haven't tried this particular version, but he's right, you can use the
emacs executable that's packaged in the Emacs.app as a CLI emacs in the
way he mentions. This one seems updated to Sept 11 2007, which is recent
enough to be useful; I assume it's emacs-22.

I build emacs 23 from CVS on Tiger, and you can do what the OP
describes. CVS actually builds 2 emacsen, one Emacs.app and one for
/usr/local/bin. (setq suspenders-and-a-belt t). Hmm. Now that I've said
that, I find that it's not working that way, nor it the GUI version the
happiest little app in the Dock. I don't really care, I almost never
open the GUI version

My CVS build fails on Leopard, but. And I love the Spaces thing, keep
emacs open all the time somewhere.
--
W. Oates

[D P Schreber]

On 2007-11-05, Warren Oates <warren...@gmail.com> wrote:
> I think he means:
>
> http://sourceforge.net/projects/emacs-app

Actually, no, that's something else entirely. It appears to be a true
Cocoa (as opposed to Carbon) emacs. Definitely interesting, but not
what I was attempting to describe.

> I haven't tried this particular version, but he's right, you can use the
> emacs executable that's packaged in the Emacs.app as a CLI emacs in the
> way he mentions.

You're right, but, again, that's not what I was describing.

I was presenting the converse: a trivially simple way to get a
(carbon) gui emacs from the cli emacs Apple provides with leopard,
without having to build anything or depend on random builds done by
anyone else.

[Dave Peck]

> The checkout will have everything except Contents/MacOS/Emacs, so it's
> ideal:
>
> - do the checkout
> - cd emacs/mac/Emacs.app/Contents/MacOS
> - cp [or ln if you prefer] /usr/bin/emacs Emacs
>
> You're done: emacs/mac/Emacs.app can now be run as a Mac application
> in Leopard.

This is great and bodes well for future emacs + OSX goodness.

Thanks for the detailed response even in the face of shenanigans-
calling! :-)

Cheers,
Dave

[rahul....@gmail.com]

My emacs.app is working fine but I have one issue:

When I want to open multiple files in different windows I cannot. All
files are opened in the same window. For example,

cd someDir
emacs lala.txt <new emacs window comes up>
cd test
emacs test.txt

The test.txt file opens in the original window. My preferred behavior
would be that it opend in a new window. Any suggestions?
I am using the following in my .emacs for opening emacs from the
terminal

open "$@" -a Emacs.app

Thanks.

[rahul....@gmail.com]

My emacs.app is working fine but I have one issue:

When I want to open multiple files in different windows I cannot. All
files are opened in the same window. For example,

cd someDir
emacs lala.txt <new emacs window comes up>
cd test
emacs test.txt

The test.txt file opens in the original window. My preferred behavior
would be that it opend in a new window. Any suggestions?
I am using the following in my .emacs for opening emacs from the
terminal

open "$@" -a Emacs.app

Thanks.

On Nov 5, 2:53 pm, Dave Peck <davep...@gmail.com> wrote:

[rahul....@gmail.com]

My emacs.app is working fine but I have one issue:

When I want to open multiple files in different windows I cannot. All
files are opened in the same window. For example,

cd someDir
emacs lala.txt <new emacs window comes up>
cd test
emacs test.txt

The test.txt file opens in the original window. My preferred behavior
would be that it opend in a new window. Any suggestions?
I am using the following in my .emacs for opening emacs from the
terminal

open "$@" -a Emacs.app

Thanks.

On Nov 5, 2:53 pm, Dave Peck <davep...@gmail.com> wrote:

[D P Schreber]

On 2007-11-28, rahul....@gmail.com <rahul....@gmail.com> wrote:
> My emacs.app is working fine but I have one issue:

You also have an issue with your usenet client...

> When I want to open multiple files in different windows I cannot. All
> files are opened in the same window.

Offhand I can't think of a way to create a new emacs frame (to use its
terminology) in an existing Emacs.app process using the osx "open"
command. Of course you can create new frames with one of the 'C-x 5'
emacs commands. But that doesn't help if you want to do it from a
shell using "open".

You can however create an entirely new Emacs.app instance this way:

open -n <file> ...<file> -a Emacs

What you would be doing in this case is running a separate emacs
process per invocation, each with its own initial frame. This is in
fact more like what happens in, say, linux under X11 if you invoke
"emacs <file> ... <file>". Every invocation creates a new emacs X11
client process, with each of the given files in its own buffer in that
process.

> I am using the following in my .emacs for opening emacs from the
> terminal
>
> open "$@" -a Emacs.app

In your .emacs? Or is this an alias in your .cshrc/.bashrc ? In any
case, add the "-n" option and you'll get a separate "window" for each
call, at the price of creating a separate process for each call.

[rahul....@gmail.com]

Thanks for the response. Works great.

On Nov 28, 6:40 am, D P Schreber <schrebe...@rayban.net> wrote: