Carbon Emacs won't start when installed in certain paths

Carbon Emacs won't start when installed in certain paths

[David Reitter]

There is still the bug that the Carbon port won't start up when  
installed in a directory that contains non 7-bit ASCII characters,  
such as "Développement".

For the release, I would suggest to at least document this in  
PROBLEMS (see below).

I recall that Yamamoto Mitsuharu had been looking into this. Mr  
Yamamoto, would you like me to test your patch posted to -bugs on May  
10th, and if so, does this replace the earlier patches you posted for  
this bug?



*** etc/PROBLEMS	22 May 2007 16:44:33 +0100	1.229
--- etc/PROBLEMS	22 May 2007 16:52:44 +0100	
***************
*** 1836,1841 ****
--- 1836,1848 ----

   ** Mac OS X

+ *** Mac OS X (Carbon): Emacs won't start if installed in certain  
paths.
+
+ Starting the application fails if Emacs is installed in directories
+ whose names contain non 7-bit ASCII characters (such as
+ "Développement"). The workaround is to move the Emacs.app application
+ bundle out of such directories.
+
   *** Mac OS X (Carbon): Environment Variables from dotfiles are  
ignored.

   When starting Emacs from the Dock or the Finder on Mac OS X, the

Re: Carbon Emacs won't start when installed in certain paths

[YAMAMOTO Mitsuharu]

>>>>> On Tue, 22 May 2007 16:57:29 +0100, David Reitter <david.reitter@gmail.com> said:

> There is still the bug that the Carbon port won't start up when  
> installed in a directory that contains non 7-bit ASCII characters,  
> such as "Développement".

> For the release, I would suggest to at least document this in
> PROBLEMS (see below).

I think the description is imprecise.  First, it is possible to
install/move the application bundle to a non-ASCII directory if Carbon
Emacs is build with the default setting (i.e., non-self-contained,
ASCII-only prefix).  Second, the underlying problem is not specific to
Carbon.  Namely, Emacs does not launch in the following cases also on
other platforms.

   * A non-ASCII prefix is specified when running `configure'.
   * Non-ASCII directories are specified as EMACSLOADPATH.

I'd add some note like "due to a restriction about the name of
directories for runtime resources, you may not move a self-contained
application bundle to a non-ASCII directory" to mac/INSTALL.

> I recall that Yamamoto Mitsuharu had been looking into this. Mr
> Yamamoto, would you like me to test your patch posted to -bugs on
> May 10th, and if so, does this replace the earlier patches you
> posted for this bug?

I think we need to discuss how to deal with a chicken-and-egg problem
(some coding systems are not ready until some lisp files are loaded at
the startup time) first.  This is not specific to Carbon.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp

Re: Carbon Emacs won't start when installed in certain paths

[Chong Yidong]

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

>> There is still the bug that the Carbon port won't start up when  
>> installed in a directory that contains non 7-bit ASCII characters,  
>> such as "Développement".
>
>> For the release, I would suggest to at least document this in
>> PROBLEMS (see below).
>
> I think the description is imprecise.

I've checked in the following into PROBLEMS:

*** Installing to a directory with non-ASCII characters in the name fails.

Installation may fail, or the Emacs executable may not start
correctly, if a directory name containing non-ASCII characters is used
as a `configure' argument (e.g. `--prefix').  The problem can also
occur if a non-ASCII directory is specified in the EMACSLOADPATH
envvar.

Re: Carbon Emacs won't start when installed in certain paths

[Stefan Monnier]

> I've checked in the following into PROBLEMS:

> *** Installing to a directory with non-ASCII characters in the name fails.

I think it belong in TODO (on the trunk).  PROBLEMS is for things we don't
intend to fix, IIRC (so it also belongs there, but in the release branch,
I guess).


        Stefan