Am Tue, 28 Jul 2015 23:41:59 +0200
schrieb Björn Lindqvist bjou...@gmail.com:
I'm not sure I understand you. By default, resource: is setup as an
alias the the directory containing the image file. But you can
override it:
factor -resource-path=/bla/bla -i=factor.image
Essentially,
It's because the switch is -resource-path not just -resource.
2015-07-29 9:11 GMT+02:00 Georg Simon georg.si...@auge.de:
Am Tue, 28 Jul 2015 23:41:59 +0200
schrieb Björn Lindqvist bjou...@gmail.com:
I'm not sure I understand you. By default, resource: is setup as an
alias the the directory
Am Wed, 29 Jul 2015 12:00:04 +0200
schrieb Björn Lindqvist bjou...@gmail.com:
It's because the switch is -resource-path not just -resource.
My mistake. Sorry.
signature.asc
Description: PGP signature
--
I'm not sure I understand you. By default, resource: is setup as an
alias the the directory containing the image file. But you can
override it:
factor -resource-path=/bla/bla -i=factor.image
Essentially, resource: is just a convenient alias and you are free
to put your vocab roots anywhere on
Am Sun, 26 Jul 2015 12:35:01 +0200
schrieb Georg Simon georg.si...@auge.de:
Yes, it does matter.
http://docs.factorcode.org/content/article-io.pathnames.special.html
If a pathname begins with resource:, it is resolved relative
Factor 0.98 x86.64 (1565, heads/master-0-g592764d, Wed Dec 24 04:52:05
2014) [GCC 4.8.2] on linux
.factor-rc
USE: vocabs.loader
/home/factor/ add-vocab-root
Judging by the binary name factor-lang you have the factor package
installed from my ppa. But it appears that you have a fresher image
coming from github. You probably can't mix the two versions like that.
You can try and run:
resource:db absolute-path
in the listener. It should show you a
