Well, you could use the infile and outfile redirect functionality. I
don't know how it's done in fpc, but the manual should get you the
proper syntax. Simply redirect the text output to a file or buffer,
then redirect the input file buffer as well, and feed the output from
the first command t
On Mon, 1 May 2023 14:25:28 -0400, Travis Siegel via fpc-pascal
wrote:
>You could just add the line:
>
>#!/bin/bash
>
>to the first line of your script, then just call the script from your
>program.
>
>Alternatively, you could call the bash command, and pass the command to
>it that way, either
Good Evening All.
Many thanks for all your replies. I have finally managed to form the GitLab
repo. I have no idea what the problem was, but it occurred tonight on my first
attempt, but my second attempt with the same settings, worked fine.
To answer your questions:
The error occurred when I c
On 5/1/23 18:55, Graeme Geldenhuys via fpc-pascal wrote:
> I just tried, and had no problems. It took about 40 seconds to clone and
> checkout the `main` branch. The download seemed to be just over 200MB.
Just tried the Gitlab repo too - same result. No problems.
G.
_
On 4/30/23 15:23, Norman Dunbar via fpc-pascal wrote:
> Any advice gratefully reeceived. Thanks.
I just tried, and had no problems. It took about 40 seconds to clone and
checkout the `main` branch. The download seemed to be just over 200MB.
On 4/30/23 15:59, Michael Van Canneyt via fpc-pascal wrote:
> One possible reason is that the repo is simply too big: it has 26 years of
> commits.
I can't imagine that being the reason. I just did a fresh clone, and it
was just over 200MB download, and the commit count on the main branch is
less
On 01/05/2023 20:02, Norman Dunbar via fpc-pascal wrote:
On 1 May 2023 17:27:52 BST, Christo Crause via fpc-pascal
wrote:
> FWIW, there are currently 68 forks of
> the FPC source repository on GitLab. ...
I noticed that when I tried to fork it. Unfortunately I am not able to
fork those now e
As mentioned in another post, you'll need to run a shell, (whether it be
bash or another system provided shell), in order to process the
commands. If you run the commands directly, there is no shell
interpretation, and the | which passes the output of one command to the
input of the next one w
On 1 May 2023 17:27:52 BST, Christo Crause via fpc-pascal
wrote:
> FWIW, there are currently 68 forks of
> the FPC source repository on GitLab. ...
I noticed that when I tried to fork it. Unfortunately I am not able to fork
those now either.
Admittedly, I didn't try to fork all of them though
On Mon, May 1, 2023 at 4:24 PM Norman Dunbar via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> On 30/04/2023 16:59, Michael Van Canneyt via fpc-pascal wrote:
>
> > The repo is not private.
> Ok, thanks. my assumption was obviously incorrect then.
>
>
> > One possible reason is that the re
Le 01/05/2023 à 17:00, Bo Berglund via fpc-pascal a écrit :
I have created a shellscript with the same command string
May be running directly your script in bash:
RunCommand('/bin/bash', ['your_script.sh' ], OutData)
___
fpc-pascal maillist - fpc-
I don't have an example at hand but I think you should run a bash
interpreter, something like :
RunCommand('/bin/bash', ['-c', ListCmd], OutData)
but I'm not 100% sure.
There is a good documentation at:
https://wiki.freepascal.org/Executing_External_Programs
May be you need to split your comma
I am trying to create a function to list the available serial ports on a Linux
device. But I have trouble getting commands which work on a terminal to also
work when run from my console program.
When I run this conmmand in the terminal I get the correct reply:
$ ls -l /sys/class/tty/*/device/driv
On 30/04/2023 16:59, Michael Van Canneyt via fpc-pascal wrote:
The repo is not private.
Ok, thanks. my assumption was obviously incorrect then.
One possible reason is that the repo is simply too big: it has 26 years of
commits.
We had serious problems importing it for this very reason.
Aga
14 matches
Mail list logo
