From: Leo Hofmann <hofmann@leo-andres.de>
To: development@lists.ipfire.org
Subject: Re: Looking for configuration file format
Date: Mon, 21 Mar 2022 21:12:48 +0100 [thread overview]
Message-ID: <ec7613da-3d82-8b26-a3ed-1f72d6dd54f3@leo-andres.de> (raw)
In-Reply-To: <B7FDB6B7-2F3C-46A2-B047-5C5827A4642C@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Hi Michael,
Thank you, I just tried it. As you suspected, General::readhasharray() accepts 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 routine.
I'll wait for other suggestions and then build my own readmanualpages() if needed!
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 <hofmann(a)leo-andres.de> wrote:
>>
>> Hi all,
>>
>> To fix an issue with the manualpages feature, I had planned to use this key/value file format:
>>
>> logs.cgi/config.dat=configuration/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 format available somewhere in the IPFire CGIs that supports this?
>>
>> Best regards,
>> Leo
>>
next prev parent reply other threads:[~2022-03-21 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 19:27 Leo Hofmann
2022-03-21 19:29 ` Michael Tremer
2022-03-21 20:12 ` Leo Hofmann [this message]
2022-03-22 12:01 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec7613da-3d82-8b26-a3ed-1f72d6dd54f3@leo-andres.de \
--to=hofmann@leo-andres.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox