Re: can one run tk/Ruby gui code from an emacs shell with compile?

[Peter Dyballa]

Am 20.11.2005 um 01:16 schrieb Anne G:

> Turning the le into el and rebooting, emacs now gives me a
> permission denied on line 1,
> Just entered the command at the prompt.

And the command was .bashrc?

That's not needed! bash reads that file automatically when it launches. 
It's like Emacs reads .emacs (and other files, for example .emacs_bash 
when you create the shell buffer in Emacs). So the 'permission denied' 
message tells you that .bashrc can't be executed, which is normal, 
since you usually do not create files in Emacs (or by vi) that are 
executable from the start. You would have to make them executable (with 
chmod; did you already try in Emacs M-x manual-entry <RET>? At the 
prompt you can type chmod and give it a <RET>.)

> turning the .el back to .le did not get it to work again.
> There is no Dyld that I can see.

Because you cut away lines starting with A, B, C, D ... Try exactly 
this with the single quotes to see in *Shell Command Output* maximally 
two lines:

        M-! env | egrep -w 'PATH|DYLD_LIBRARY_PATH'

M-! inveokes Emacs' shell-command function. Then env (list the shell's 
environment) is excuted. Its output is filtered with egrep, which is 
told to look up whole words (-w). The words are described in the 
regular expression following. This has a vertical bar (|) which has a 
special meaning in a shell, so it has to be escaped by putting it into 
single quotes.


> Turning the le into el and rebooting,

Anne, you don't need to reboot your Mac when you change an Elisp (Emacs 
Lisp) file's name. Just re-launch that application.


It's here already after midnight. It's Sunday. And I'm going to bed. I 
won't have much time before local noon and I'll be out of house for 
some hours in the afternoon. I think there is no real error, you just 
made a mistake in shell. Earlier I forgot one file to mention: 
~/.emacs_bash! That's the one with the unset command. If you try to 
find out whether /usr/local/bin/ruby works correctly with 
DYLD_LIBRARY_PATH then you should comment that unset statement. This 
comment *will* raise another error, but don't get confused of this, 
it's normal interaction of Emacs and bash. Nothing fails there, it's 
just that the unset command can't be executed, so shell will have 
DYLD_LIBRARY_PATH set.

--
Greetings

  Pete

A lot of us are working harder than we want, at things we don't like to
do.  Why? ...In order to afford the sort of existence we don't care to 
live.
        -- Bradford Angier