help suggestions #52

CptJimKirk commented 2023年05月03日 03:25:06 +02:00

`argv[] but no mention of implicit x as used in ngn/k examples. 
`exit is not mentioned in \`. any other `symbol functions missing from the \` documentation would be helpful to add. 
`x explanation in \` is not clear to me. I have an executable k script, which uses `#!k`, runs from the terminal, but I could not determine how to properly execute as a `x command. 
/ example
`x(("path/to/myScript.k";args);"")
`x(,"path/to/myScript.k";args)
/ this was my solution, but not what is happening in ngn/k/l/runparts.k
`x(("path/to/k/k";"path/to/myScript.k");args)
An example of `x that includes how to start another k process would be helpful. 
no mention of \l which uses files in other directories. Is current directory or abs path the only option? No relative path? 

``` `argv[] but no mention of implicit x as used in ngn/k examples. `exit is not mentioned in \`. any other `symbol functions missing from the \` documentation would be helpful to add. `x explanation in \` is not clear to me. I have an executable k script, which uses `#!k`, runs from the terminal, but I could not determine how to properly execute as a `x command. / example `x(("path/to/myScript.k";args);"") `x(,"path/to/myScript.k";args) / this was my solution, but not what is happening in ngn/k/l/runparts.k `x(("path/to/k/k";"path/to/myScript.k");args) An example of `x that includes how to start another k process would be helpful. no mention of \l which uses files in other directories. Is current directory or abs path the only option? No relative path? ```

ngn commented 2023年05月03日 20:02:51 +02:00

`x explanation in \` is not clear to me.

the argument is a pair consisting of:

• a list of strings specifying argv of the new process - *argv is the path to the executable and 1_argv are the arguments
• a string specifying content to be written to the child process's stdin; it can be empty

so i guess what you want is

`x((,"path/to/myScript.k"),args;"")

---

\l
No relative path?

relative paths (relative from the current working directory) should work.

btw, it's a bit annoying that built-in libraries (the l directory) are not easily accessible, e.g. with \l l/utf8.k unless you're in the project's root. there are many ideas but no solution for that right now.

> ``` `x ``` explanation in ``` \` ``` is not clear to me. the argument is a pair consisting of: * a list of strings specifying `argv` of the new process - `*argv` is the path to the executable and `1_argv` are the arguments * a string specifying content to be written to the child process's `stdin`; it can be empty so i guess what you want is `x((,"path/to/myScript.k"),args;"") --- > `\l` > No relative path? relative paths (relative from the current working directory) should work. btw, it's a bit annoying that built-in libraries (the `l` directory) are not easily accessible, e.g. with `\l l/utf8.k` unless you're in the project's root. there are many ideas but no solution for that right now.

CptJimKirk commented 2023年05月03日 23:33:28 +02:00

so if I have

/root
- /dir1
 - file.k
- main.k

then should be able to say
\l ../main.k inside /dir1/file.k?

Or do you mean, if running the program from /root then I should be able to say
\l main.k inside /dir1/file.k?

I don't follow

so if I have ``` /root - /dir1 - file.k - main.k ``` then should be able to say `\l ../main.k` inside `/dir1/file.k`? Or do you mean, if running the program from `/root` then I should be able to say `\l main.k` inside `/dir1/file.k`? I don't follow

ngn commented 2023年05月05日 00:04:06 +02:00

if running the program from /root then I should be able to say
\l main.k inside /dir1/file.k?

this

> if running the program from `/root` then I should be able to say `\l main.k` inside `/dir1/file.k`? this