sorry fond email
> On 5 Jun 2015, at 12:21, Iain Gray wrote:
>
> June to my thred Re: [Factor-talk] osx emacs FUEL as it has gone missing here.
> thanks Iain
>
> maailserver boounced request
>> On 4 Jun 2015, at 15:34, John Benediktsson wrote:
>>
>> Excell
June to my thred Re: [Factor-talk] osx emacs FUEL as it has gone missing here.
thanks Iain
maailserver boounced request
> On 4 Jun 2015, at 15:34, John Benediktsson wrote:
>
> Excellent!
>
> Glad it's working. Based on your feedback I made a patch that tries to find
&
Excellent!
Glad it's working. Based on your feedback I made a patch that tries to find
emacsclient in your path, so some installations will work out of the box. For
Emacs.app, you will still have to set it manually.
We love newcomers and it's great to get a fresh perspective. Sometimes things
Doug your email has gone missing, retrieved from archive
success!
thank you all for your advice and patience with a newcomer
> On 3 Jun 2015, at 18:01, Iain Gray wrote:
>
> Sorry to try your patience again
>
> I found emacsclient locally in /usr/bin
> so my .factor-rc is now
>
> USING: e
You need to set the path to the full path of the emacsclient binary.
```factor
USING: editors.emacs namespaces ;
"/usr/bin/emacsclient" \ emacsclient-path set-global
```
You can debug what's happening because the array in the ``command`` slot of
``process`` is what Factor is launching.
```
Sorry to try your patience again
I found emacsclient locally in /usr/bin
so my .factor-rc is now
USING: editors.emacs namespaces ;
“‘’/usr/bin” \ emacsclient-path set-global
typing these into a listener followed by “io” edit gives
Process exited with error code 255
Launch descriptor:
T{ proce
Why is your process trying to run /Applications/Languages/Factor when you call
edit?
Shouldn't it be the /path/to/emacsclient?
This is what I mean (using the full path to your emacsclient):
USING: editors.emacs namespaces
"/Applications/Languages/Emacs.app/Contents/MacOS/bin-i386-10_5/emacscli
I get a similar error
Process exited with error code 255
Launch descriptor:
T{ process
{ command
{
"/Applications/Languages/factor"
"--no-wait"
"+1"
"/Applications/Languages/factor/core/io/io.factor"
}
}
{ detached t }
I just noticed that your error doesn't use your emacsclient-path (just the
default "emacsclient"):
T{ process
{ command
{
"emacsclient"
"--no-wait"
"+1"
"/Applications/Languages/factor/core/io/io.factor"
}
}
}
Is it possible
that works if I do
$ cd /Applications/Languages/factor
I feel very close!
> On 2 Jun 2015, at 14:32, John Benediktsson wrote:
>
> I'm sorry its not working, are you sure you have an emacs started and run
> ``M-x server-start`` from it?
>
> Our emacs "edit" integration just calls emacsclient,
I'm sorry its not working, are you sure you have an emacs started and run
``M-x server-start`` from it?
Our emacs "edit" integration just calls emacsclient, so it should be simple
to get working.
Does emacsclient work from your command-line?
$ cd factor
$ emacsclient --no-wait +1 README
My .factor-rc reads
USING: editors.emacs namespaces ;
“/Applications/languages/Emacs.app/Contents/MacOS/bin-i386-10_5”
emacsclient-path set-global
after doing all suggestions I still get
IN: scratchpad "io" edit
Process exited with error code 1
Launch descriptor:
T{ process
{ command
I downloaded Emacs.app, and this works for me:
"/Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_9/emacsclient"
emacsclient-path set-global
(There are binaries for different versions of OS X and architectures, use
the right one for your machine I guess):
/Applications/Emacs.app $ fi
The .factor-boot-rc is used during bootstrap, but if you just download and
use a release, you might want to put that code in .factor-rc which is run
each time Factor starts.
Also, I'm a bit confused -- your examples uses "emacspath" but the
documentation for editors.emacs says to set the path to e
still doesn’t work sorry
I found emacsclient deep inside Emacs,app
> On 1 Jun 2015, at 13:00, Björn Lindqvist wrote:
>
> You shouldn't need to set emacs-path if the emacs and emacsclient
> binaries are on your path. emacsclient is not called correctly from
> Factor, but as a workaround you can s
You shouldn't need to set emacs-path if the emacs and emacsclient
binaries are on your path. emacsclient is not called correctly from
Factor, but as a workaround you can start the server manually. First
start emacs and in it type M-x server-start. Then you should be able
to run "io" edit in the Fac
I have setup the file .factor-boot-rc as
USING: editors.emacs namespaces ;
“/Applications/languages” \ emacs-path sett-global
which sets up the path to emacs.app
running factor.app I get on doing “palindrome” edit
error code 1 which seems to be complaining about “emacsclient”
whereas loading pa
Could you explain in more detail what your problem is?
2015-05-30 19:04 GMT+02:00 Iain Gray :
> I have successfully integrated FUEL in emacs but cannot seem get it
> integrated with Factor. My emacs is 24..4.1 and an aoo and my os is OS X
> 10.3. Any advice appreciated. Iain
> --
I have successfully integrated FUEL in emacs but cannot seem get it integrated
with Factor. My emacs is 24..4.1 and an aoo and my os is OS X 10.3. Any advice
appreciated. Iain
--
__
19 matches
Mail list logo
