From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Looking for configuration file format
Date: Mon, 21 Mar 2022 19:29:24 +0000
Message-ID: <B7FDB6B7-2F3C-46A2-B047-5C5827A4642C@ipfire.org>
In-Reply-To: <9efcb360-3ca2-383d-ef4e-c3a66ed7fd70@leo-andres.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7965505705480160682=="
List-Id: <development.lists.ipfire.org>

--===============7965505705480160682==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hey Leo,

Did you try &General::readhasharray()?

Then this file would just be a CSV file.

I believe that readhasharray might want a numeric key, but maybe it accepts t=
he first value as key whatever it is.

-Michael

> On 21 Mar 2022, at 19:27, Leo Hofmann <hofmann(a)leo-andres.de> wrote:
>=20
> Hi all,
>=20
> To fix an issue with the manualpages feature, I had planned to use this key=
/value file format:
>=20
> logs.cgi/config.dat=3Dconfiguration/logs/logsettings
>=20
> But unfortunately this is not possible with the existing General::readhash(=
) function, because it removes non-alphanumeric keys.
>=20
> Before I write yet another readsomething() function: Is there a file format=
 available somewhere in the IPFire CGIs that supports this?
>=20
> Best regards,
> Leo
>=20


--===============7965505705480160682==--