Can RnD be able to handle editorsetup.conf with tabs
Posted: Thu May 21, 2026 10:08 pm
Hi, I just replied to a post and wrote "I am now more reticent to keep on posting ideas and "I wants"." And now I am making a new post, with a new request!
My editorsetup.conf has lots of this kind of thing:
char_space
char_r
char_n
char_d
bd_diamond
diamond
pearl
crystal
So two blocks of 4 elements, arranged with spaces so I can glance at it and say 'yes it looks like there are 4 elements per block, so these blocks should line up OK' (as long as all the blocks before also have 4 els per block, not 1, 2, 3, 5 or any number other than a multiple of 4).
However this requires new lines to make it readable, and I end up including comments, and it turns into a beast.
I would like to turn it into a structure file, like a rows-by-columns block in a spreadsheet, eg:
char_space char_r char_n char_d
bd_diamond diamond pearl crystal
I played around with a few versions of editorsetup.conf, where elements were separated by:
- tab only
- colon followed by tab
- semicolon followed by tab
But RnD only read either, the first element on the line, or no elements at all.
So, please could RnD be enhanced to be able to make sense of an editorsetup.conf with token keys many to a line?
i.e. just process them, one after the other, just like it does with tokens one per line.
So instead of requiring the delimiter to be newline, maybe also accept tab char.
Many thanks
John
p.s. I am also going to make a post requesting another enhancement: allow a level NOT to have its own editorsetup.conf file - of course this is allowed already - but more importantly, enhance RnD so that for a level without its own editorsetup.conf file, it checks in the group folder above for an editorsetup.conf file, and if it finds one, use that, and if not, check the folder above, and so on, all the way up to the levels folder. So that a levels folder with many levelsets, could contain only one editorsetup.conf file, and yet all the levels make use of the same editorsetup.conf file, unless they have their own, or their folders are child folders of a folder with its own.
I am mentioning that here because it seems to be that both these enhancements could be done and released together.
My editorsetup.conf has lots of this kind of thing:
char_space
char_r
char_n
char_d
bd_diamond
diamond
pearl
crystal
So two blocks of 4 elements, arranged with spaces so I can glance at it and say 'yes it looks like there are 4 elements per block, so these blocks should line up OK' (as long as all the blocks before also have 4 els per block, not 1, 2, 3, 5 or any number other than a multiple of 4).
However this requires new lines to make it readable, and I end up including comments, and it turns into a beast.
I would like to turn it into a structure file, like a rows-by-columns block in a spreadsheet, eg:
char_space char_r char_n char_d
bd_diamond diamond pearl crystal
I played around with a few versions of editorsetup.conf, where elements were separated by:
- tab only
- colon followed by tab
- semicolon followed by tab
But RnD only read either, the first element on the line, or no elements at all.
So, please could RnD be enhanced to be able to make sense of an editorsetup.conf with token keys many to a line?
i.e. just process them, one after the other, just like it does with tokens one per line.
So instead of requiring the delimiter to be newline, maybe also accept tab char.
Many thanks
John
p.s. I am also going to make a post requesting another enhancement: allow a level NOT to have its own editorsetup.conf file - of course this is allowed already - but more importantly, enhance RnD so that for a level without its own editorsetup.conf file, it checks in the group folder above for an editorsetup.conf file, and if it finds one, use that, and if not, check the folder above, and so on, all the way up to the levels folder. So that a levels folder with many levelsets, could contain only one editorsetup.conf file, and yet all the levels make use of the same editorsetup.conf file, unless they have their own, or their folders are child folders of a folder with its own.
I am mentioning that here because it seems to be that both these enhancements could be done and released together.