> Even though they'd get lost when VDR writes it, allowing comments there would be an improvement so distros (and VDR itself) could ship the file with some comments in it that instruct users what they need to do before things will work, or what the file is for, or... Same thing applies to remote.conf, setup.conf, and timers.conf. The mentioned files are nothing else than a table of the database VDR. There is no solution out there, where it is possible to edit the channel list outside the normal operation, or even to think about comments within it. It is not possible within MythTV, not on commercial settop boxes, PVRs or any builtin receivers in TV devices, not even with the famous DBox'es and Dreamboxes. If you're lucky there might be tool where you could connect from another PC to the box and edit your channel list within small boundaries, so advantage VDR, 15:0 ... So, the information has to be managed from datebases frontend, in case of VDR the OSD or "svdrp". The only sufficient solution might be to have a switch in OSDs channel editor, to disable or enable a entry in channels list, like it is available on commercial solutions. Same for all relevant conf-Files, whereas I don't see any reason to put comments into timers.conf, weird ... Regards fnu -----Ursprüngliche Nachricht----- Von: vdr-bounces@xxxxxxxxxxx [mailto:vdr-bounces@xxxxxxxxxxx] Im Auftrag von Ville Skyttä Gesendet: Sonntag, 15. Januar 2012 12:29 An: vdr@xxxxxxxxxxx Betreff: Re: howto ignore lines in channels.conf On 2012-01-15 13:01, Klaus Schmidinger wrote: > VDR reads the channels.conf file and doesn't store any information > about "comments". It only stores the channel data. > When it writes the file, it writes only the channel data, and at that > point any comments in the original file would be lost. Even though they'd get lost when VDR writes it, allowing comments there would be an improvement so distros (and VDR itself) could ship the file with some comments in it that instruct users what they need to do before things will work, or what the file is for, or... Same thing applies to remote.conf, setup.conf, and timers.conf. If the "AllowComments" parameter exists just for the purpose of disallowing comments in files where VDR doesn't preserve them, I suggest removing that restriction altogether and allowing comments everywhere. Allowing comments and preserving them are two different things. For files where VDR doesn't preserve them it could note that on the first line of such files, for example like: # Warning: VDR will overwrite this file without preserving comments. _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
