Am Tue, 23 Dec 2014 11:22:49 -0800
schrieb John Benediktsson :
Hi John,
> USE: command-line
> executable get
> command-line get
works. Thank you.
for now I cannot make deploy work in the new the nightly build. I
started a new thread: "deploy no longer working with new nightly build"
Hi Georg,
The nightly builds are updated now if you want to try them (Win64 is not yet
ready because of some updates that @erg is currently doing on the Win64 build
server).
I made it so that, similar to Python, you can get the executable separate from
the command-line arguments.
USE: co
Am Mon, 22 Dec 2014 22:45:55 -0800
schrieb John Benediktsson :
Hi John,
thank you.
So I can wait for the next nightly build I assume.
Georg
> Hi Georg,
>
> I pushed a fix to provide you the executable name.
>
> Basically the ``(command-line)`` word in the command-line vocabulary
> is the "ra
Hi Georg,
I pushed a fix to provide you the executable name.
Basically the ``(command-line)`` word in the command-line vocabulary is the
"raw" command-line, which includes all command-line arguments including the
executable. The ``command-line`` symbol is where we keep the other
arguments to the
We try and make it consistent between deployed and non-deployed applications.
It looks like we are not storing the executable name right now (argv[0]).
Probably we should fix that I guess!
If we fix it in master are you comfortable running a nightly build? (They are
well tested before the buil
Am Mon, 22 Dec 2014 06:51:22 -0800
schrieb John Benediktsson :
> Hi Georg,
>
> I don't see a difference between deploy and when a script/vocabulary
> is run directly.
>
> Is your question about deploy, or how to obtain the
> command/executable name?
>
> Thanks,
> John.
Hi John,
yes I wanted t
Hi Georg,
I don't see a difference between deploy and when a script/vocabulary is run
directly.
Is your question about deploy, or how to obtain the command/executable name?
Thanks,
John.
On Mon, Dec 22, 2014 at 2:21 AM, Georg Simon wrote:
>
> http://docs.factorcode.org/content/word-command-li
