> From: Nikolay Kudryavtsev
> Date: Tue, 21 Dec 2021 14:29:27 +0300
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> Yes, Eli, I tested your patch on both.
Thanks, I've now uploaded a fixed binary distribution.
> Date: Tue, 21 Dec 2021 16:29:02 +0100
> From: Patrice Dumas
> Cc: Nikolay Kudryavtsev ,
> bug-texinfo@gnu.org
>
> > I think that code gets copied into both script. Gavin, am I right?
>
> I think that makeinfo is now a link to texi2any. But maybe it could
> also be a copy depending on t
On Tue, Dec 21, 2021 at 02:27:12PM +0200, Eli Zaretskii wrote:
> > From: Nikolay Kudryavtsev
> > Date: Tue, 21 Dec 2021 14:29:27 +0300
> > Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
> >
> > Yes, Eli, I tested your patch on both.
> >
> > But here I'm talking about texinfo repo master, wher
> From: Nikolay Kudryavtsev
> Date: Tue, 21 Dec 2021 14:29:27 +0300
> Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org
>
> Yes, Eli, I tested your patch on both.
>
> But here I'm talking about texinfo repo master, where only texi2any has
> been patched.
I think that code gets copied into both
Yes, Eli, I tested your patch on both.
But here I'm talking about texinfo repo master, where only texi2any has
been patched.
> From: Nikolay Kudryavtsev
> Date: Tue, 21 Dec 2021 02:12:14 +0300
> Cc: Eli Zaretskii , Texinfo
>
> Looked at c0c07af5f1, seems like it only touches texi2any, I think the
> same should be done for makeinfo.
Yes, as I said, the patch should be applied both to texi2any and to
makeinfo. Did yo
Looked at c0c07af5f1, seems like it only touches texi2any, I think the
same should be done for makeinfo.
Eli, I was able to apply your patch and confirm it works.
> From: Gavin Smith
> Date: Sun, 19 Dec 2021 11:20:00 +
> Cc: Eli Zaretskii , Texinfo
>
> On Sun, Dec 19, 2021 at 10:56 AM Gavin Smith wrote:
> > I can try to make this work (it may be as simple as reinstating the
> > above lines) but can't promise anything as this is an extra
> > complicat
> From: Gavin Smith
> Date: Sun, 19 Dec 2021 10:56:36 +
> Cc: Eli Zaretskii , Texinfo
>
> Do other programs from ezwinports not have the same issue with finding
> installed files?
Most of them don't. Some do, but support an environment variable that
can be sent to indicate that the tree ha
On Sun, Dec 19, 2021 at 10:56 AM Gavin Smith wrote:
> I can try to make this work (it may be as simple as reinstating the
> above lines) but can't promise anything as this is an extra
> complication above what is normally done with installed programs.
Done in commit c0c07af5f1. It appears to work
On Sun, Dec 19, 2021 at 2:17 AM Nikolay Kudryavtsev
wrote:
>
> Yes "Can't locate Texinfo/ModulePath.pm" is the error message.
>
> Sorry, maybe I should have joined in and corrected immediately, but the
> latest working version is actually 6.5, not 6.6, I do not have a 6.6
> binary in my collection
Yes "Can't locate Texinfo/ModulePath.pm" is the error message.
Sorry, maybe I should have joined in and corrected immediately, but the
latest working version is actually 6.5, not 6.6, I do not have a 6.6
binary in my collection, so I had no knowledge if this problem exists there.
As to how 6.
On 12/18/21 06:59, Gavin Smith wrote:
On Sat, Dec 18, 2021 at 2:54 PM Eli Zaretskii wrote:
Is this part supposed to work also when Texinfo is installed in a
directory different from the prefix with which it was configured?
No, it is only for running from the source/build directory, not for
On Sat, Dec 18, 2021 at 2:54 PM Eli Zaretskii wrote:
> Is this part supposed to work also when Texinfo is installed in a
> directory different from the prefix with which it was configured?
No, it is only for running from the source/build directory, not for
the installed program.
> From: Gavin Smith
> Date: Sat, 18 Dec 2021 14:44:39 +
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Thu, Dec 16, 2021 at 05:52:45PM -0600, Jacob Bachmeyer wrote:
> > If they can have a location fixed relative to the script, the Perl core
> > module FindBin and pragmatic module lib can he
> From: Gavin Smith
> Date: Sat, 18 Dec 2021 14:43:18 +
> Cc: bug-texinfo@gnu.org
>
> On Fri, Dec 17, 2021 at 08:58:04AM +0200, Eli Zaretskii wrote:
> > No, I think this was before 6.7. If I compare makeinfo between 6.6
> > and 6.7, I see that these parts were modified:
> >
> > # To fin
On Thu, Dec 16, 2021 at 05:52:45PM -0600, Jacob Bachmeyer wrote:
> If they can have a location fixed relative to the script, the Perl core
> module FindBin and pragmatic module lib can help here:
>
> use FindBin;
> use lib "$FindBin::Bin/../lib";
texi2any already can find itself for running from
On Fri, Dec 17, 2021 at 08:58:04AM +0200, Eli Zaretskii wrote:
> No, I think this was before 6.7. If I compare makeinfo between 6.6
> and 6.7, I see that these parts were modified:
>
> # To find Texinfo::ModulePath
> if (!defined($ENV{'top_builddir'})) {
> $ENV{'top_builddir'} = Fil
> Date: Fri, 17 Dec 2021 09:28:42 -0800
> Cc: bug-texinfo@gnu.org
> From: Per Bothner
>
> On 12/17/21 04:57, Eli Zaretskii wrote:
> > I mean relative to the directory of the makeinfo script, which is
> > installed in ${prefix}/bin (at least by default).
>
> Right, but the problem is how does the
On 12/17/21 04:57, Eli Zaretskii wrote:
I mean relative to the directory of the makeinfo script, which is
installed in ${prefix}/bin (at least by default).
Right, but the problem is how does the script find out the directory
it is running in? It is non-trivial problem, which is why the Perl
> Date: Fri, 17 Dec 2021 04:27:33 -0800
> Cc: bug-texinfo@gnu.org
> From: Per Bothner
>
> On 12/16/21 23:29, Eli Zaretskii wrote:
> > Personally, I find the relative-path method much easier, but I will go
> > with anything Gavin considers as the preferable solution.
>
> I'm not sure what you mea
On 12/16/21 23:29, Eli Zaretskii wrote:
Personally, I find the relative-path method much easier, but I will go
with anything Gavin considers as the preferable solution.
I'm not sure what you mean by "the relative-path" method and how it differs
from my example code. Reading the file "../share/
> Date: Thu, 16 Dec 2021 16:21:09 -0800
> From: Per Bothner
>
> On 12/16/21 15:52, Jacob Bachmeyer wrote:
> > If they can have a location fixed relative to the script, the Perl core
> > module FindBin and pragmatic module lib can help here:
>
> Or if using bash or similar you take do something
> Date: Thu, 16 Dec 2021 17:52:45 -0600
> From: Jacob Bachmeyer
>
> >> Could we please resurrect this ability in a future release of Texinfo?
>
> This feature may have worked by pure dumb luck before
Yes, I think so.
> but it should be fairly simple to support explicitly.
That's what I'm aski
> From: Gavin Smith
> Date: Thu, 16 Dec 2021 23:12:15 +
> Cc: bug-texinfo@gnu.org
>
> On Thu, Dec 16, 2021 at 11:52:19AM +0200, Eli Zaretskii wrote:
> > Hi,
> >
> > I routinely make my MS-Windows/MinGW builds of Texinfo for others to
> > use, here:
> >
> > https://sourceforge.net/projects
For DomTerm (https://domterm.org) whose main executable
is C/C++ I use whereami: https://github.com/gpakosz/whereami
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
On Thu, Dec 16, 2021 at 05:52:45PM -0600, Jacob Bachmeyer wrote:
>
> This feature may have worked by pure dumb luck before, but it should be
> fairly simple to support explicitly.
It could also be, if I recall well, because at some point in the past
texi2html was made relocatable for inclusion in
On 12/16/21 15:52, Jacob Bachmeyer wrote:
If they can have a location fixed relative to the script, the Perl core module
FindBin and pragmatic module lib can help here:
Or if using bash or similar you take do something like this,
which is a simplified version of the Kawa start-up script:
#!/b
Gavin Smith wrote:
On Thu, Dec 16, 2021 at 11:52:19AM +0200, Eli Zaretskii wrote:
Hi,
I routinely make my MS-Windows/MinGW builds of Texinfo for others to
use, here:
https://sourceforge.net/projects/ezwinports/
Recently, a user complained to me that starting with Texinfo 6.7, the
Texinfo
On Thu, Dec 16, 2021 at 11:52:19AM +0200, Eli Zaretskii wrote:
> Hi,
>
> I routinely make my MS-Windows/MinGW builds of Texinfo for others to
> use, here:
>
> https://sourceforge.net/projects/ezwinports/
>
> Recently, a user complained to me that starting with Texinfo 6.7, the
> Texinfo Perl s
Hi,
I routinely make my MS-Windows/MinGW builds of Texinfo for others to
use, here:
https://sourceforge.net/projects/ezwinports/
Recently, a user complained to me that starting with Texinfo 6.7, the
Texinfo Perl scripts won't work unless the binary distro is installed
in the same directory for
32 matches
Mail list logo
