> 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 on startup
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
To find the full path, this may work - open Terminal and type:
which pdftotext
and it should display the path to the copy of pdftotext that the OS runs
when you type the 'pdftotext' command.
Phil Davis
On 1/12/20 2:00 PM, Brian Milby via use-livecode wrote:
My guess is that shell
My guess is that shell can’t find your executable. Try using full paths.
Thanks,
Brian
On Jan 12, 2020, 2:54 PM -0500, Hillen Richard via use-livecode
, wrote:
> Hello,
>
> I want to extract .txt from a pdf-file using Livecode 9.5 on macOS Catalina.
>
> Therefore I installed from
