> Date: Sat, 8 Aug 2015 09:00:14 +0100 > From: Gavin Smith <gavinsmith0...@gmail.com> > Cc: Rob Browning <r...@defaultvalue.org>, 793...@bugs.debian.org, > Texinfo <bug-texi...@gnu.org> > > One idea I had, which could be useful for Windows and other systems > lacking symlinks, is to make an Info file itself operate as a kind of > symlink. When the target is a non-split file, the indirect file would > have the form of a split Info file, with a single file mentioned in > its indirect sub-file table, being the absolute path of the target > file. This would work because sub-files of split files are identical > in format to non-split files. The two possible problems I foresee are > that indirect sub-file tables have hitherto never contained absolute > paths
Why would it need to, since this is only about renaming the basename of the Info file, isn't it? > >> and why is it important enough to add an extra feature for them that > >> isn't needed on other operating systems, complicating the situation > >> for everybody else who isn't using them? > > > > Init files are a widely used feature, it's not a complication at all. > > Clearly it is a complication to design an init file format, write code > to parse it, and explain to users how to write such init files. Sorry, I don't follow: Info already supports an init file, so the above code already exists, right? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
