Re: Latest Development Version - @image with @value

[Christopher Dimech]

I often end up with may @ifset and @ifclear in my documents.
Is it acceptable to call the following command?  It does work
as expected.

@inlineifset{igrank-1, @set imgpth /home/hagbard}

imgpth: @value{imgpth}


> Sent: Saturday, December 05, 2020 at 12:30 AM
> From: "Patrice Dumas" <pertusus@free.fr>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Gavin Smith" <gavinsmith0123@gmail.com>, "help-texinfo gnu" 
> <help-texinfo@gnu.org>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 11:43:09PM +0100, Christopher Dimech wrote:
> > Fantastic.  Things age working now.  texinfo.tex is mentioned in the README 
> > file.
> >
> > There are three files README, INSTALL, INSTALL.generic.  When reading them, 
> > they continue
> > referring around between themselves.
>
> The INSTALL.generic is "out of our control" it is the generic
> INSTALL file for autoconf/automake based packages.  So we add
> a specific INSTALL file for the texinfo specifics in link with
> installing.
>
> > Can there be just one README (otherwise have just one INSTALL file) with 
> > abbreviated
> > set of instructions of typical installation, at the beginning?
>
> I am not that convinced that it is a good idea.  The reference to
> INSTALL appears at the beginning of the README and I think that INSTALL*
> are best separate as otherwise the INSTALL specific parts would get in the
> way of having a short README.  As I said above, the INSTALL.generic is
> outside of our control, which makes the only real option merging the
> specific INSTALL in the README.
>
> > Thank you both for bearing with me.  But it was not so clear and quick
> > about what exactly one should do when trying development versions.
>
> It is indeed not clear nor quick.
>
> It seems to me that README-hacking contains most of the information
> (though not about building in a different directory from the source),
> and then the INSTALL file.  It is a bit scattered, but the problem is
> that different persons will not need the same information depending on
> where they come from and need to do (from a release, the developpment
> source, testing or installing).  Also the overall build system is not
> simple, there is an intrinsic complexity that we can't really remove by
> instructions (the whole autoconf/automake/gettext, with two translated
> sets, and additionally some Makefile parts being generated).
>
> It is not so clear to me what/if we need to add more information, people
> testing from the development tree are very few, answering to questions
> by mail could be more efficient than trying to document everything.
>
> That being said, if you have specific ideas of changes to the files, do
> not hesitate to propose, in particular in the form of patches.
>
> > --------
>
> In general there is also a need to run
> ./autogen.sh
> in the source thee before going into the build directory.
>
> >
> > % mkdir build
> > % cd build
> > % srcdir/configure [options] [target]
> > % make
> > % make install
> > % cp srcdir/doc/texinfo.tex workdir
> >
> > Where workdir is the directory of your main Texinfo input file.
> >
> > --------
> >
> >
> > > Sent: Friday, December 04, 2020 at 10:53 PM
> > > From: "Patrice Dumas" <pertusus@free.fr>
> > > To: "Christopher Dimech" <dimech@gmx.com>
> > > Cc: "Gavin Smith" <gavinsmith0123@gmail.com>, "help-texinfo gnu" 
> > > <help-texinfo@gnu.org>
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote:
> > > > > Sent: Friday, December 04, 2020 at 10:30 PM
> > > > > From: "Patrice Dumas" <pertusus@free.fr>
> > > > > To: "Christopher Dimech" <dimech@gmx.com>
> > > > > Cc: "Gavin Smith" <gavinsmith0123@gmail.com>, "help-texinfo gnu" 
> > > > > <help-texinfo@gnu.org>
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> > > > > >
> > > > > > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > > > > > From: "Patrice Dumas" <pertusus@free.fr>
> > > > > > > To: "Christopher Dimech" <dimech@gmx.com>
> > > > > > > Cc: "Gavin Smith" <gavinsmith0123@gmail.com>, "help-texinfo gnu" 
> > > > > > > <help-texinfo@gnu.org>
> > > > > > > Subject: Re: Latest Development Version - @image with @value
> > > > > > >
> > > > > > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech 
> > > > > > > wrote:
> > > > > > > > I done the whole thing again, however the version is still 
> > > > > > > > showing
> > > > > > > >
> > > > > > > > Loading texinfo [version 2020-10-24.12]
> > > > > > > >
> > > > > > > > hagbard@fuckup:
> > > > > > > > + ~/01cuneus/tdr/03ch
> > > > > > > > ls -lrt /usr/local/bin/texi2pdf
> > > > > > > > -rwxr-xr-x 1 root root 1246 Dec  4 19:09 /usr/local/bin/texi2pdf
> > > > > > > >
> > > > > > > > hagbard@fuckup:
> > > > > > > > + ~/01cuneus/tdr/03ch
> > > > > > > > ls -lrt
> > > > > > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec  4 18:03 texinfo.tex
> > > > > > >
> > > > > > > You can look at the beginning of the file to check that it is 
> > > > > > > indeed
> > > > > > > the latest one.  If it is not used, it would be very strange.
> > > > > >
> > > > > > I see texinfo.tex is saying
> > > > > > \def\texinfoversion{2020-10-24.12}
> > > > >
> > > > > Then it is not the one from git, the one from git has
> > > > > \def\texinfoversion{2020-11-14.10}
> > > >
> > > > I did a git clone.  Where do you put the file?  Apologies, but I cannot 
> > > > determine
> > > > where texinfo.tex is located.
> > >
> > > It is in texinfo/doc/texinfo.tex
> > >
> > > --
> > > Pat
> > >
>