all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim McNamara <timmcn@bitstream.net>
Subject: Re: C-x C-w on mac (carbon) emacs
Date: 16 Oct 2003 13:39:49 -0500	[thread overview]
Message-ID: <m2ekxdf2mi.fsf@localhost.bitstream.net> (raw)
In-Reply-To: slrnbotk6h.4df.hwolf@esb.dsl.bbn.com

Hugh Wolf <hwolf@deutsches.lieder.de> writes:
 
> The single most likely reason the OP is having trouble is that he's
> running a year-old build of a cvs snapshot, built by someone other
> than him with unknown configuration options in an unknown environment.
> Probably this will all go away if he rebuilds it himself from the
> current sources.

Since he's a Mac OS X user (like me) it's quite likely that he is
running someone else's build.  Mac users are not accustomed to
compiling from source, the Mac OS not having the tools available to
the general public prior to OS X.  His post states he's using the
Carbon version, which is likely compiled using Andrew Choi's patches
to the Emacs source.  There are two commonly available Carbon builds
for OS X (one for 10.1.* and one for 10.2.*), both of which have known
problems that seem to be related to adapting Emacs to the Mac menu bar
interface.

As I've mentioned previously, I'm running 10.1.5 (a fit of resistance
to Apple's full-list-price "upgrade" policy) and the www.porkrind.org
21.1 build, and am not able to duplicate the OP's experience.  Perhaps
trying a different build would be in order?

      reply	other threads:[~2003-10-16 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13  5:30 C-x C-w on mac (carbon) emacs Leo
2003-10-15 16:49 ` data64
2003-10-15 18:38   ` Hugh Wolf
2003-10-15 20:37     ` Tim McNamara
2003-10-16 12:55       ` Hugh Wolf
2003-10-16  2:30     ` Leo
2003-10-16  4:20       ` Tim McNamara
2003-10-16 15:47     ` Barry Margolin
2003-10-16 17:09       ` Hugh Wolf
2003-10-16 18:39         ` Tim McNamara [this message]

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=m2ekxdf2mi.fsf@localhost.bitstream.net \
    --to=timmcn@bitstream.net \
    /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.