Help: ISPELL and Aqua EMACS (OSX)

Help: ISPELL and Aqua EMACS (OSX)

[Edward Dodge]

I downloaded and compiled the newest ispell:

International Ispell Version 3.2.06 08/01/01

And the latest ispell.el from:

http://www.kdstevens.com/~stevens/ispell-page.html

Then I put (require 'ispell) in my .emacs.

THE PROBLEM:

Aqua EMACS doesn't seem to source the whole PATH variable, because it
can't seem to find my ispell program.  In fact, I get an error when I
source my .emacs at startup because it can't find ispell.  Terminal
emacs ("% emacs -nw") doesn't have this problem and I can use ispell
without any issues.

Any help would be appreciated....

Edward

Re: Help: ISPELL and Aqua EMACS (OSX)

[Hans-Peter Binder]

Edward Dodge <someone@g3.com> wrote:

> THE PROBLEM:
> 
> Aqua EMACS doesn't seem to source the whole PATH variable, because it
> can't seem to find my ispell program.  In fact, I get an error when I
> source my .emacs at startup because it can't find ispell.  Terminal
> emacs ("% emacs -nw") doesn't have this problem and I can use ispell
> without any issues.

I have this in my .emacs:

	(setq ispell-program-name "/usr/bin/ispell") 

HTH

Regards/Gruesse
Hans-Peter Binder
-- 
"Who the f**k is General Failure
and why is he reading my hard disk?"

Re: Help: ISPELL and Aqua EMACS (OSX)

[Hugo Wolf]

In article <m27kf31uwu.fsf@g3.com>, Edward Dodge wrote:
> Aqua EMACS doesn't seem to source the whole PATH variable

If you launch emacs by double-clicking Emacs.app, it doesn't source
your shell rc.  That's the root of the problem.  

You can open from it a shell instead - in that case it will of course
use the current value of PATH.  If you create a Terminal document
which opens Emacs.app, you can double-click that to launch emacs and
the effect will be the same.

The other choice is to set exec-path explicitly in your .emacs.
That's what I do.  For instance if your shell rc adds the fink
directories to PATH, do this in .emacs:

  (setq exec-path (append '("/sw/bin" "/sw/sbin") exec-path))



Or you can set the ispell path specifically, but that won't help for
the next thing you try to run from emacs (eg stunnel if you want to
use vm with pop3s).

Re: Help: ISPELL and Aqua EMACS (OSX)

[Stefan Monnier <foo@acm.com>]

>> Aqua EMACS doesn't seem to source the whole PATH variable
> If you launch emacs by double-clicking Emacs.app, it doesn't source
> your shell rc.  That's the root of the problem.  

Not even your .login ?
Where can you setup your environment, then ?


        Stefan

Re: Help: ISPELL and Aqua EMACS (OSX)

[Schone Mullerin]

In article <5lhee5pueq.fsf@rum.cs.yale.edu>, Stefan Monnier <foo@acm.com> wrote:
>>> Aqua EMACS doesn't seem to source the whole PATH variable
>> If you launch emacs by double-clicking Emacs.app, it doesn't source
>> your shell rc.  That's the root of the problem.  
> 
> Not even your .login ?

I don't know whether or not .login environment settings will be
available if you double click Emacs.app.


> Where can you setup your environment, then ?

Afaik if you need your shell environment, you have to launch emacs
from a shell, with the 'open' command, eg

 open /Applications/Emacs.app

If you want a double-clickakable icon to do this, make an executable
.command file containing the 'open' command above (of course modified
as appropriate depending where you installed Emacs.app).

Re: Help: ISPELL and Aqua EMACS (OSX)

[Stefan Monnier <foo@acm.com>]

>> Where can you setup your environment, then ?
> Afaik if you need your shell environment, you have to launch emacs
> from a shell, with the 'open' command, eg

I'm not talking about my "shell environment" but about my environment,
which is a concept linked to processes, not to shells (although it is
traditionally set up in the rc file of your login shell).

I want *everything* to inherit my environment, since it includes things
like my locale, my preferred way to execute SSH from CVS, where to find
executables, where to find manual pages, where to find info pages, which
printer to use, ...


        Stefan

Re: Help: ISPELL and Aqua EMACS (OSX)

[Schone Mullerin]

In article <5l7kf1plq1.fsf@rum.cs.yale.edu>, Stefan Monnier
<foo@acm.com> wrote: 

> I'm not talking about my "shell environment" but about my
>  environment,

As defined by shell variables -- thus, "shell environment".

If you launch Emacs.app from a shell, directly or indirectly, you'll
get what you want.  If you launch it from the Finder, you won't.  I
don't know what else to tell you.

Re: Help: ISPELL and Aqua EMACS (OSX)

[Stefan Monnier <foo@acm.com>]

>> I'm not talking about my "shell environment" but about my
>> environment,
> As defined by shell variables -- thus, "shell environment".

No, environment variables are not the same as shell variables.
Shells muddy up the distinction between the two, so people often don't
understand that they are different, but think about what `export' in bash
and `setenv' in tcsh do.

> If you launch Emacs.app from a shell, directly or indirectly, you'll
> get what you want.  If you launch it from the Finder, you won't.  I
> don't know what else to tell you.

I fully understand that, but I want to set my locale and other env-vars at
one place and have them apply to all processes, whether launched from
a shell or not.  Hence my question: where can I setup my environment
other than in my .login since the .login is not always invoked ?


        Stefan


PS: XDM used to have the same kind of brain-damage.  I believe recent
RedHat configs fix that by always sourcing the .login when starting up
an X session such that those settings are then inherited by all processes
without the need to start them from a shell.

Re: Help: ISPELL and Aqua EMACS (OSX)

[Michael Hudson]

"Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:

> Hence my question: where can I setup my environment other than in my
> .login since the .login is not always invoked ?

You might be able to do something by fiddling with /etc/ttys and the
arguments passed to

/System/Library/CoreServices/loginwindow.app/loginwindow

but I'm a bit lost in there (last time I mucked with this stuff I
broke my ability to log in...).

Cheers,
M.

-- 
  It is never worth a first class man's time to express a majority
  opinion.  By definition, there are plenty of others to do that.
                                                        -- G. H. Hardy

Re: Help: ISPELL and Aqua EMACS (OSX)

[Kai Großjohann]

"Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:

> PS: XDM used to have the same kind of brain-damage.  I believe recent
> RedHat configs fix that by always sourcing the .login when starting up
> an X session such that those settings are then inherited by all processes
> without the need to start them from a shell.

In our working group, we still put a 

    #!/bin/bash --login

line into /etc/X11/Xsession, for this reason...

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Help: ISPELL and Aqua EMACS (OSX)

[Benjamin Riefenstahl]

> >> Aqua EMACS doesn't seem to source the whole PATH variable If you
> >launch emacs by double-clicking Emacs.app, it doesn't source your
> >shell rc.  That's the root of the problem.

"Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:
> Not even your .login ?
> Where can you setup your environment, then ?

The environment for the loginwindow and thus the Finder can be
statically configured in ~/.MacOSX/environment.plist, see <URL:
http://developer.apple.com/techpubs/macosx/Essentials/SystemOverview/BootingLogin/Customization_Techniques.html>

Re: Help: ISPELL and Aqua EMACS (OSX)

[Stefan Monnier <foo@acm.com>]

>>>>> "Edward" == Edward Dodge <someone@g3.com> writes:
> Aqua EMACS doesn't seem to source the whole PATH variable, because it
> can't seem to find my ispell program.  In fact, I get an error when I

Based on Benjamin's article, we can finally give you the proper answer:
set your PATH in your ~/.MacOSX/environment.plist rather than in your
shell's rc file.
(or maybe in both, in case you log in remotely with OpenSSH).


        Stefan

Re: Help: ISPELL and Aqua EMACS (OSX)

[Edward Dodge]

Hans-Peter Binder <tethys.pb@gmx.net> writes:

> Edward Dodge <someone@g3.com> wrote:
> 
> > THE PROBLEM:
> > 
> > Aqua EMACS doesn't seem to source the whole PATH variable, because it
> > can't seem to find my ispell program.  In fact, I get an error when I
> > source my .emacs at startup because it can't find ispell.  Terminal
> > emacs ("% emacs -nw") doesn't have this problem and I can use ispell
> > without any issues.
> 
> I have this in my .emacs:
> 
> 	(setq ispell-program-name "/usr/bin/ispell") 
> 
> HTH

Thanks Hans,

And thanks to everyone else in the thread.  This has been most
educational and I am inspired to learn more about elisp!

I think for now I will just put Hans' code in my system-dependent
section of my EMACS file:

(when (eq system-type 'darwin)
  (setq ispell-program-name "/usr/local/bin/ispell")
  (set-frame-font "fontset-mac")
  (set-keyboard-coding-system 'mac-roman-unix)
  (set-frame-font "-etl-fixed-medium-r-normal--14-140-75-75-m-140-iso8859-1")
  (modify-frame-parameters (selected-frame) '((font .
  "-*-Monaco-*-140-*"))))

------------------

If I run into any other problems,  I'll probably have to go with
something more along the lines of launching EMACS through a shell
script.

Edward