Forums Scripts & Popups question for yml files

Does anyone know of a method in mirc that can be used to read yml files should work similarly to $read and $readini.

I only know that yml files are structured differently. and I can hardly read them out via $read or $readini..

mIRC does not have such a built-in method, but you can create it yourself in the form of $your_identifier() using aliases, and add your own switches, parameters and properties to it, which will help process data in different ways when extracting text from a yml file.

🕮 https://en.wikichip.org/wiki/mirc/aliases

i Need a Feature or a funtions to read and write to yml files similar to the $readini $read and /write funktion in Mirc.

The reason why I need this is because mirc doesn't take spaces and indentations or tabs etc into account and so it's not possible to set a variable in the following form.

An example:

In a Test.yml
There is the following entry.


I would have to be able to address the section using the new function, which is similar to the $readini function.

The new function would have to be called as follows.

$readyml(file, Section)

So now if I use $readyml(test.yml, BlacklistedBlocks)

The input should reflect the following, taking into account the indentation and spaces.

The output should then be:


It would be nice if someone could put something like that together for me.

I can't solve this using $read and $readini because readini only recognizes a section marked with [] and 2. doesn't take spaces or indents or tabs into account

/set %var also doesn't work because it also eats up the spaces.

I have created this script for you that will work as your own identifier "$readyml()" to read files "yml".
But I'm not sure that it will work as effectively if there is another data structure that is different from the one you provided in the example.

Try testing this script code with your file:


Syntax: $readyml(filename, section [,N])


Test1 - (get all items of a section): //echo -a $readyml(test.yml, BlacklistedBlocks)

Test2 - (get 3rd item of section): //echo -a $readyml(test.yml, BlacklistedBlocks, 3)

Test3 - (get the number of section items): //echo -a $readyml(test.yml, BlacklistedBlocks, 0)

Test4 - (get the 5th item of the section): //echo -a $readyml(test.yml, BlacklistedBlocks, 5)

Thanks for i the given example was only a example of a section of a yml file...
But the forum here eats spaces too...

the structure of a orginal yml are so:


the white points befor the -
Serve to display the spaces.

The correct output would then be:

However, the structure of the yml should be taken into account when outputting, i.e.: If in the example yml under Blacklistedblocks there are entries with spaces, they should not be missing in the output...

Note
Other yml files could store a different structure so that the given code no longer works, so there must be a general code for all yml files.

Not that an extra alias has to be written for each yml in order to read it out. That's not the case with $read or $readini either... $read randomly reads a line from a file. The disadvantage is that it eats the spaces at the beginning of a file, so $read doesn't work with yml files.

The same applies to $readini..

With Readini, the sections have to be marked with [], so it doesn't work with yml files either.

So we are looking for a function similar to $read and $readini that works for yml files.

If you want the help provided to you by the developers to be more effective in the form of working code, then it will be better if you attach a link to your post to the "file.yml" you are using for efficient testing and so as not to encounter distortions in the data structure when directly publishing data excerpts from a file.

It would also be a good idea to add links to reference documentation that describe various variations of the data structure of the file with the "yml" extension.

Apparently, the usual built-in mIRC tools will not be able to read and get the result from this file type the way you want.
Either will have to develop a third-party application for reading and writing "yml" files that will be able to interact with mIRC, or will need to leave a request for the required functionality.