> It appears to be possible to upload to subdirectories of
> ftp.gnu.org/gnu/texinfo, pursuant to Info node "(maintain)FTP Upload
> Directory Trees".
>
> I have done this so the new files are at
>
> https://ftp.gnu.org/gnu/texinfo/htmlxref.d/
>
> We could upload a stub file to replace htmlxref.
On Tue, Feb 18, 2025 at 12:10:09AM +0100, Patrice Dumas wrote:
> On Mon, Feb 17, 2025 at 07:00:37PM +, Gavin Smith wrote:
> > On Mon, Feb 17, 2025 at 07:44:53PM +0100, Patrice Dumas wrote:
> > > On Mon, Feb 17, 2025 at 06:33:30PM +, Gavin Smith wrote:
> > > > It should be easy to create an
On Mon, Feb 17, 2025 at 07:00:37PM +, Gavin Smith wrote:
> On Mon, Feb 17, 2025 at 07:44:53PM +0100, Patrice Dumas wrote:
> > On Mon, Feb 17, 2025 at 06:33:30PM +, Gavin Smith wrote:
> > > It should be easy to create an htmlxref.d directory and upload the
> > > two files there.
> >
> > Sho
On Mon, Feb 17, 2025 at 07:44:53PM +0100, Patrice Dumas wrote:
> On Mon, Feb 17, 2025 at 06:33:30PM +, Gavin Smith wrote:
> > It should be easy to create an htmlxref.d directory and upload the
> > two files there.
>
> Should I document that in the manual?
Sorry, I'm not sure what you mean. W
On Mon, Feb 17, 2025 at 06:33:30PM +, Gavin Smith wrote:
> It should be easy to create an htmlxref.d directory and upload the
> two files there.
Should I document that in the manual?
> There would be the question of whether we then delete the uploaded
> (unitary) htmlxref.cnf. We would not b
On Thu, Feb 13, 2025 at 11:14:21PM +0100, Patrice Dumas wrote:
> On Sat, Jan 18, 2025 at 11:22:07PM +0100, Patrice Dumas wrote:
> > In any case, I said above, my preference now would be to use both an
> > htmlxref.cnf and files in htmlxref.d/*.cnf in all the directories where
> > htmlxref.cnf are s
On Sat, Jan 18, 2025 at 11:22:07PM +0100, Patrice Dumas wrote:
> In any case, I said above, my preference now would be to use both an
> htmlxref.cnf and files in htmlxref.d/*.cnf in all the directories where
> htmlxref.cnf are searched for currently and no include directive.
This is done. I also
On Tue, Feb 04, 2025 at 05:22:06PM +0100, Patrice Dumas wrote:
> On Sat, Jan 18, 2025 at 11:22:07PM +0100, Patrice Dumas wrote:
> > In any case, I said above, my preference now would be to use both an
> > htmlxref.cnf and files in htmlxref.d/*.cnf in all the directories where
> > htmlxref.cnf are s
On Sat, Jan 18, 2025 at 11:22:07PM +0100, Patrice Dumas wrote:
> In any case, I said above, my preference now would be to use both an
> htmlxref.cnf and files in htmlxref.d/*.cnf in all the directories where
> htmlxref.cnf are searched for currently and no include directive.
I will implement that
On Sat, Jan 18, 2025 at 09:59:38PM +, Gavin Smith wrote:
> On Sat, Jan 18, 2025 at 03:27:05PM +0100, Patrice Dumas wrote:
> > Hello,
> >
> > I propose to use the following syntax using glob for files to be found
> > in a directory relative to the htmlxref.conf where the htmlxrefinclude
> > dir
On Sat, Jan 18, 2025 at 03:27:05PM +0100, Patrice Dumas wrote:
> Hello,
>
> I think that it would be better if it was possible to specify a
> directory to be searched for files in htmlxref.conf to get more entries.
> This would allow
> * to have diverse community maintaining the different files
>
Hello,
I think that it would be better if it was possible to specify a
directory to be searched for files in htmlxref.conf to get more entries.
This would allow
* to have diverse community maintaining the different files
* easier customization, by dropping a file in a directory instead of
changi
12 matches
Mail list logo