From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Hofmann To: development@lists.ipfire.org Subject: Re: Looking for configuration file format Date: Mon, 21 Mar 2022 21:12:48 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7547717965464002774==" List-Id: --===============7547717965464002774== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, Thank you, I just tried it. As you suspected, General::readhasharray() accept= s only numeric keys. This format would work: 1,logs.cgi/config.dat,configuration/logs/logsettings But I need the path as a key, because I don't want to write a clumsy search r= outine. I'll wait for other suggestions and then build my own readmanualpages() if ne= eded! Best regards, Leo Am 21.03.2022 um 20:29 schrieb Michael Tremer: > 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= the first value as key whatever it is. > > -Michael > >> On 21 Mar 2022, at 19:27, Leo Hofmann wrote: >> >> Hi all, >> >> To fix an issue with the manualpages feature, I had planned to use this ke= y/value file format: >> >> logs.cgi/config.dat=3Dconfiguration/logs/logsettings >> >> But unfortunately this is not possible with the existing General::readhash= () function, because it removes non-alphanumeric keys. >> >> Before I write yet another readsomething() function: Is there a file forma= t available somewhere in the IPFire CGIs that supports this? >> >> Best regards, >> Leo >> --===============7547717965464002774==--