> Richard H. wrote:
> Typing to Terminal „pdftotext“ I get a List with command-options.
> With get shell(„pdftotext“) with and without quotes
> I get the answer „/bin/sh: line 1: pdftotext: command not found“
> What is wrong? May you please help? (MacOS Catalina).
You could add
Shell() always uses the default folder path. Example (mac/Linux):
Set the defaultFolder to specialFolderPath(“home”)
put shell(“ls”)
Breakpoint
Set the defaultFolder to specialFolderPath(“documents”)
put shell(“ls”)
Breakpoint
I put any non native shell commands I want into my engine path,
To elaborate further, if you can use pdftotext from the command line, but this
is failing, it is because the path declared for your login shell is not getting
picked up, or a different shell is being used by livedcode.
Come to think of it, I have *no* idea which shell livecode defaults to—I’d
erminal „pdftotext“ I get a List with command-options.
With
get shell(„pdftotext“) with and without quotes
I get the answer „/bin/sh: line 1: pdftotext: command not found“
What is wrong? May you please help?
Richard.
___
use-livecode mailing li
t; But extracting doesn´t work and I get the answer:
>
> /bin/sh: line 1: pdftotext /users ……pdf: No such file or directory
>
> and the result ist 127.
>
>
>
> Typing to Terminal „pdftotext“ I get a List with command-options.
>
> With
> get shell(„pdft
)
answer it & return & the result
——
But extracting doesn´t work and I get the answer:
/bin/sh: line 1: pdftotext /users ……pdf: No such file or directory
and the result ist 127.
Typing to Terminal „pdftotext“ I get a List with command-options.
With
get shell(„pdftotext“) with and with
