[bug #24500] wrong line number in warning in case of @xref within @footnote

URL: http://savannah.gnu.org/bugs/?24500 Summary: wrong line number in warning in case of @xref within @footnote Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: jeu 09 oct 2008 05:45:57 GMT

[bug #24599] @ref unduely produces preceeding see

URL: http://savannah.gnu.org/bugs/?24599 Summary: @ref unduely produces preceeding see Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: sam 18 oct 2008 11:58:06 GMT Category: makeinfo

Some suggestions and bug report

Hi, The two attached emails were never answered. The second one is a bug report, I am using (a patched version of): makeinfo (GNU texinfo) 4.13 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free

Re: Some suggestions and bug report

Dear Karl, Thank-you for your kind answers and your valuable suggestions. I have received no email on nov 28. Maybe there was some issue with my email client on that day. Thank you for forwarding your answer. I agree that a comment is just fine to help the inter-lingual maintenance, but my

[bug #35395] bad picture path with --html and --without --no-split

URL: http://savannah.gnu.org/bugs/?35395 Summary: bad picture path with --html and --without --no-split Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: dim. 29 janv. 2012 19:32:30 GMT

[bug #35395] bad picture path with --html and --without --no-split

Follow-up Comment #4, bug #35395 (project texinfo): Salut, I also think that absolute path don't make sense, because one likes to move a manual around. Also, you need to keep in mind that texi2any issues a warning when the image file is not found, so when you run texi2any, you have an idea

[bug #35395] bad picture path with --html and --without --no-split

Follow-up Comment #7, bug #35395 (project texinfo): Salut Patrice and al., After some further thoughts my suggestion would be as follows: - provide a new command line option --link-prefix that allows the user to force some prefix for relative links - if the user does not explicitely give some

[bug #35395] bad picture path with --html and --without --no-split

Follow-up Comment #9, bug #35395 (project texinfo): Bonsoir Patrice, Concerning the problem with html file not generated in the right place, I did use the latest CVS. However, it seems that the problem is connected with filename format in MSWindows, and this is why you could not reproduce it.

Re: [bug #35395] bad picture path with --html and --without --no-split

Following up only by email, as recommended by Karl. Concerning the option name (if any command line option is ever to be added), should that be --image-link-prefix or just --link-prefix I am wondering: don't you have the same issue with command line option --css-ref. In the command line

Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Eli Zaretskii a écrit : Date: Sun, 21 Apr 2013 13:05:55 + From: Vincent Belaïche invalid.nore...@gnu.org There must not be any CR in the Info files, only LF. ?? Why? Looping also through bbdb-i...@lists.sourceforge.net for info. 1) install-info is unable to handle them

[bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Follow-up Comment #2, bug #38795 (project texinfo): Answering on list... ___ Reply to this item at: http://savannah.gnu.org/bugs/?38795 ___ Message posté via/par Savannah

Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Karl Berry a écrit : Vincent, Finally getting back to this mail. Date: Sun, 21 Apr 2013 19:02:39 +0200 = install-info (GNU texinfo) 4.11 = Copyright (C) 2007 Free Software Foundation, Inc. That's pretty old. As far as I can see, both the current install-info (maybe I eventually

[bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Additional Item Attachment, bug #38795 (project texinfo): File name: makeinfo-dos.cpp Size:1 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?38795 ___ Message

[bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Additional Item Attachment, bug #38795 (project texinfo): File name: bbdb.info Size:64 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?38795 ___ Message

[bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Additional Item Attachment, bug #38795 (project texinfo): File name: cr.png Size:73 KB File name: bbdb.png Size:119 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?38795

Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Hello Karl, Answers embedded below, Karl Berry a écrit : Hi Vincent, I need to be able to reproduce the problem on my machine. Sorry, but I have no clue what to do with the Info files you uploaded. Nor am I going to be doing anything on MSYS or compiling any C++ wrappers. BTW, the files in

Re: [bug #38795] texi2any makes CR in output when input is mixed CR-LF and LF files

Karl Berry a écrit : Hi Vincent - Emacs display issues are surely something to report to bug-emacs or emacs-devel, if you can find something reproducible with the current version and starting up with -q --no-site-file. I have experienced many issues over the years wrt crlf display, so a bug in

[bug #42895] Can't run autoreconf

URL: http://savannah.gnu.org/bugs/?42895 Summary: Can't run autoreconf Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: ven. 01 août 2014 07:16:36 GMT Category: None

[bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

URL: http://savannah.gnu.org/bugs/?42897 Summary: texi2any does not bark at incorrect menu entry, and makes erroneous info output Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: ven. 01 août 2014

[bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

Follow-up Comment #1, bug #42897 (project texinfo): Sorry, in the previous message I did a plain cut and paste for showing what the EMACS viewer shows. However it is not what I see, because the cut and paste also takes invisible text. So I made two screen captures, in attached file

Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

Eli Zaretskii a écrit : Date: Sat, 2 Aug 2014 00:01:52 +0100 From: Gavin Smith gavinsmith0...@gmail.com I couldn't find out how to display an arbitrary file in emacs Info Like this: C-u C-h i /path/to/arbitrary-info-file RET You can also do as follows: 1) open Dired mode by `C-x

Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

Vincent Belaïche a écrit : Eli Zaretskii a écrit : Date: Sat, 2 Aug 2014 00:01:52 +0100 From: Gavin Smith gavinsmith0...@gmail.com I couldn't find out how to display an arbitrary file in emacs Info Like this: C-u C-h i /path/to/arbitrary-info-file RET You can also do as follows

[bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

Additional Item Attachment, bug #42897 (project texinfo): File name: temp3.texi Size:1 KB File name: temp3.info Size:0 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?42897

Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

Gavin Smith a écrit : Like this: [...] It would be better if there was some colon escape command in Texinfo, like @comma{}, @{, @} and @@ for other special characters, and that this colon escape would be used in place of colon when it is part of the node/label name. Maybe a @string

Re: [bug #42897] texi2any does not bark at incorrect menu entry, and makes erroneous info output

Karl Berry a écrit : It looks like the menu entry label is thought to stretch across multiple lines. FWIW, I am not aware that menu labels are intended to work, or have ever worked, when broken across lines. It doesn't make sense to me, in any case. Menu labels shouldn't be that

[bug #43045] texi2any does not collapse to one space multiple spaces within node names

URL: http://savannah.gnu.org/bugs/?43045 Summary: texi2any does not collapse to one space multiple spaces within node names Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: jeu. 21 août 2014 21:48:50 GMT

Re: [bug #43042] Texinfo manual typo and improvement in info node 'Node Line Requirements'

Gavin Smith a écrit : On Thu, Aug 21, 2014 at 6:22 PM, Vincent Belaïche [...] = Clarifying _References_ = Furthermore, what _References_ means it a bit ambiguous. I understand that it means references in the texinfo manual source code, and that it is one of the following: * a @ref

RE: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'

Hello Eli, Gavin, Patice, Karl. Looping also through Patrice Dumas and Karl Berry and texinfo-bug list. Useful links: http://savannah.gnu.org/bugs/?43045 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18308 Answers comments below: Date: Fri, 22 Aug

[bug #43122] texi2dvi does not compile enough times to get toc

URL: http://savannah.gnu.org/bugs/?43122 Summary: texi2dvi does not compile enough times to get toc Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: lun. 01 sept. 2014 09:36:59 GMT

[bug #43126] Macros defined through @include make a spurious space before @end macro

URL: http://savannah.gnu.org/bugs/?43126 Summary: Macros defined through @include make a spurious space before @end macro Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: lun. 01 sept. 2014 18:15:31 GMT

RE: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'

; bug-texinfo@gnu.org (adding bug-texinfo) On Fri, Aug 22, 2014 at 11:04 PM, Vincent Belaïche vincent@hotmail.fr wrote: Finally, as an EMACS user, it would be more important to me * if docstring could be written in a sort of texinfo-light format (when you create a package or anything

Re: [bug #43126] Macros defined through @include make a spurious space before @end macro

Gavin Smith a écrit : On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche invalid.nore...@gnu.org wrote: I have attached an example. There are two macros with identical definition (only naming changed in order to avoid erroneous duplication of macro definition). One of the macro is defined

Re: [bug #43126] Macros defined through @include make a spurious space before @end macro

Vincent Belaïche a écrit : Gavin Smith a écrit : On Mon, Sep 1, 2014 at 7:15 PM, Vincent Belaïche [...] Dear Gavin et alii, I think that you have put the finger on it: it does not have to do with @include but with line endings. I did the following experiment: * both bug_texinfo.texi

RE: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'

Just to clarify that I was suggesting three completely different things: One first thing was better support of internationalization for *Manuals*, in that context I was speaking about node name translation for presentation to user (there should remain a node true name that should remain the

[bug #43122] texi2dvi does not compile enough times to get toc

Follow-up Comment #2, bug #43122 (project texinfo): Nothing new about the problem itself, I just attached a finalized (well nothing is ever finalized) of my translation of metafont-for-beginner to French --- with porting from LaTeX2.09 to Texinfo format. It is more of removing plenty of bad

Re: [bug #43042] Texinfo manual typo and improvement in info node 'Node Line Requirements'

space when in the menu entry. Vincent. Gavin Smith a écrit : On Thu, Aug 21, 2014 at 6:22 PM, Vincent Belaïche invalid.nore...@gnu.org wrote: = Clarifying _References_ = Furthermore, what _References_ means it a bit ambiguous. I understand that it means references in the texinfo manual

[bug #43122] texi2dvi does not compile enough times to get toc

Additional Item Attachment, bug #43122 (project texinfo): File name: metafont-for-beginners.texiSize:48 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?43122 ___ Message

Re: [bug #45759] Can't find Texinfo::ModulePath

with the other perl installation (activestate perl), rather than the MSYS perl. I let you know then. VBR, Vincent Belaïche --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. http://www.avast.com

Re: [bug #45759] Can't find Texinfo::ModulePath

Hello Gavin, See https://savannah.gnu.org/bugs/index.php?45759#comment1 VBR, Vincent Belaïche --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. http://www.avast.com

[bug #45759] Can't find Texinfo::ModulePath

Follow-up Comment #1, bug #45759 (project texinfo): Ok, now I tried it with the activestate perl, but it seems that MSYS autotools aren't able to manage it correctly, as I got the following: -| /bin/sh ../libtool --tag=CC --mode=compile

[bug #45771] texi2any barks at non recursive macro being recursive

URL: http://savannah.gnu.org/bugs/?45771 Summary: texi2any barks at non recursive macro being recursive Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: dim. 16 août 2015 16:36:40 GMT

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Hello, My answers inserted below. Le 21/08/2015 13:42, Gavin Smith a écrit : On 20 August 2015 at 22:41, Vincent Belaïche vincent.belai...@gmail.com wrote: Hello Gavin, Your email confirms what I thought, my problem is that my log file does not contain any \openout traces while yours have

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Ooops... I had missed your latest email Le 21/08/2015 14:30, Gavin Smith a écrit : On 21 August 2015 at 12:42, Gavin Smith gavinsmith0...@gmail.com wrote: [...] From my reading of the source of texi2dvi, it looks in the filesystem to see what files were produced; it doesn't look at what

Re: [bug #43122] texi2dvi does not compile enough times to get toc

My answers below: Le 21/08/2015 17:25, Gavin Smith a écrit : So yes the .toc and the other output files are there, and that does not suffice for texi2dvi to trigger one more run. As I said the problem is that MikTeX pdftex does not traces the \openout into the log file. Here's a report of a

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 22/08/2015 00:26, Karl Berry a écrit : At this point, I guess I have to conclude it is better to use -recorder if it is available. k See my previous email, I checked again with catting the logs to standard output, and none of the MikTeX engines does the \openout tracing job. So using

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Answer below... Le 21/08/2015 23:40, Gavin Smith a écrit : On 21 August 2015 at 22:18, Vincent Belaïche vincent.belai...@gmail.com wrote: As you can see there is no such thing as any \openout trace in the .log file, for any of pdftex, luatex or xetex engines. I can't see it, because you

[bug #43122] texi2dvi does not compile enough times to get toc

Follow-up Comment #4, bug #43122 (project texinfo): Dear Karl et alii, Sorry for the very-very long delay before doing any feedback. So, following Karl's request, I got the latest texi2dvi and texinfo.tex from the SVN repo and did the test again, and it still fails to make the toc complete after

Re: [bug #43122] texi2dvi does not compile enough times to get toc

a écrit : On 17 August 2015 at 15:38, Vincent Belaïche invalid.nore...@gnu.org wrote: Follow-up Comment #5, bug #43122 (project texinfo): Hello Gavin, First of all, I don't know why Karl could not reproduce the problem and he got the toc complete in one texi2pdf run (equating two tex runs Under

[bug #45759] Can't find Texinfo::ModulePath

URL: http://savannah.gnu.org/bugs/?45759 Summary: Can't find Texinfo::ModulePath Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: ven. 14 août 2015 11:26:28 GMT Category: makeinfo

Re: [bug #45759] Can't find Texinfo::ModulePath

Hello Gavin, My answers below On 14 August 2015 at 20:03, Vincent Belaïche vincen...@users.sourceforge.net wrote: Can't locate Texinfo/ModulePath.pm in @INC (@INC contains: c:/Nos_Programmes/msys/lib/perl5/site_perl/5.8/../tp /usr/lib/perl5/5.8/msys /usr/lib/perl5/5.8 /usr/lib/perl5

Re: [bug #43122] texi2dvi does not compile enough times to get toc

. By setting environnement variable TEXI2DVI_USE_RECORDER you can suppress the additional prior testing and make this novel texi2dvi almost as fast as it used to be. VBR, Vincent Belaïche --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Salut, Le 30/08/2015 01:12, Karl Berry a écrit : I can't look at the patch any time soon, sorry. I'm sure Gavin will do a good review :). I think using -recorder (when it's available) should be the default, as I wrote privately to Gavin a few days ago. I don't know what he thinks. It is

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Salut, Le 30/08/2015 01:12, Karl Berry a écrit : I can't look at the patch any time soon, sorry. I'm sure Gavin will do a good review :). I think using -recorder (when it's available) should be the default, as I wrote privately to Gavin a few days ago. I don't know what he thinks. It is

[bug #45862] Texinfo manual does not compile with texi2pdf

Follow-up Comment #1, bug #45862 (project texinfo): My texindex: $ texindex --version texindex (GNU texinfo) 4.11 Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and

Re: [bug #43122] texi2dvi does not compile enough times to get toc

>Salut Gavin, > >My answers inserted below... > > >[...] > > >FYI, there is one manual which I cannot compile : texinfo manual, in the >trunk/doc directory, I get the following: > > >$ texi2pdf

Re: [bug #43122] texi2dvi does not compile enough times to get toc

My answers below... Le 04/09/2015 12:20, Gavin Smith a écrit : > On 3 September 2015 at 22:02, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> Hello Gavin, >> >> I had a look to your second patch, and I have some comments >> >> 1) on the

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Answers below... Le 04/09/2015 18:24, Gavin Smith a écrit : > On 4 September 2015 at 14:04, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> Ok, I had not understood the motivation. If generated_file_get is called >> several times for the same tex run, then

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Hello Gavin, I had a look to your second patch, and I have some comments 1) on the way that you have factorized code between functions generated_files_get_from_fls and generated_files_get_from_log, what you did is call one of this functions inside generated_files_set and place the

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Answers below... Le 09/09/2015 02:14, Gavin Smith a écrit : [...] > > Vincent mentioned the problem of the efficiency of running the test > for --recorder every time. I don't think it's a problem: if it led to > a noticeable slowdown (maybe tenth of a second or so) that would be a > problem.

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 16/09/2015 00:25, Gavin Smith a écrit : [...] > > Because the *.fls (sorted fl index file) is clobbered by the *.fls > recorder file, so it is no more. I had to change the order to get this > to work, so that the *.fls (sorted fl index file) will be created > again, after the recorder file

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 16/09/2015 00:25, Gavin Smith a écrit : > On 15 September 2015 at 22:49, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> There is another optimization that could be done: at the end of the loop >> run_bibtex and run_index are launched one more time e

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 15/09/2015 23:53, Karl Berry a écrit : > are the TeXLive engine MSys application ? > > There is no explicit support for msys in TeX Live, as far as I can > recall. There is support for cygwin and native Windows. > > How do you handle texi2xxx > tools for MSW in TeXLive ? > > I'm

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 14/09/2015 12:21, Gavin Smith a écrit : >> On 9 September 2015 at 06:52, Vincent Belaïche >> <vincent.belai...@gmail.com> wrote: >>> Well, I agree with you that tweaking just for performance when it is not >>> worth it is just another source of p

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 15/09/2015 23:29, Gavin Smith a écrit : > On 15 September 2015 at 18:15, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> No, these lines are bogous because >> >> $EGREP -iv 'cygwin|mingw|djgpp' >> >> will always fail. As a result

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Just one plain question following my previous email (conclusion part): are the TeXLive engine MSys application ? How do you handle texi2xxx tools for MSW in TeXLive ? VBR, Vincent --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 16/09/2015 12:40, Gavin Smith a écrit : >> Now here is the funny story, I have made a correction of texi2dvi >> (attached to this email), and it converts all pathes from MSys to MSW >> for both input file and TeX envvar, everything seemed ok but compilation >> of dummy.texi was still failed.

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Hello Eli, Answers below... Le 17/09/2015 12:58, Eli Zaretskii a écrit : >> From: vincent.belai...@gmail.com (Vincent Belaïche) >> Date: Thu, 17 Sep 2015 12:41:12 +0200 >> Cc: Karl Berry <k...@freefriends.org>, Texinfo <bug-texinfo@gnu.org>, >> Vincent

[bug #45912] texindex 5.9.93 does not support -o argument

URL: Summary: texindex 5.9.93 does not support -o argument Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: jeu. 10 sept. 2015 06:34:18 GMT Category:

[bug #45913] MSYS gawk does not like \(CR) due to texindex SVN not keeping Linux EOL

URL: Summary: MSYS gawk does not like \(CR) due to texindex SVN not keeping Linux EOL Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: jeu. 10 sept. 2015 06:45:10 GMT

[bug #46018] texi2any makes inconsistent EOL style

Follow-up Comment #2, bug #46018 (project texinfo): It is true that MSYS programs open text files without doing the CRLF conversion to LF, which is not surprising as they just do like programs on systems which natively uses LF as an EOL. Anyway all the non-MS programs internally (be it AWK,

[bug #46018] texi2any makes inconsistent EOL style

Follow-up Comment #3, bug #46018 (project texinfo): I just realized that we have already discussed this sort of EOL conversion in relation with [bug #38795]. In [bug #38795] my problem was that the BBDB manual was made of several files, some of them had svn:eol-style set to LF and others to

[bug #46007] texi2dvi Msys support

Additional Item Attachment, bug #46007 (project texinfo): File name: texi2dvi.diff Size:1 KB ___ Reply to this item at: ___ Message

[bug #46007] texi2dvi Msys support

Follow-up Comment #2, bug #46007 (project texinfo): Le 20/09/2015 17:31, Eli Zaretskii a écrit : > Follow-up Comment #1, bug #46007 (project texinfo): > >> if test -n "$COMSPEC$ComSpec" && uname | $EGREP -iv 'cygwin >>>/dev/null; then path_sep=";" > > Shouldn't that ' before "cygwin" be

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Answers inserted below... Le 16/09/2015 11:09, Gavin Smith a écrit : >> Since the nearly beginning of this whole tale of woe, I am thinking that >> it would be better to solve the .fls case in texinfo.tex also rather >> than just texi2dvi, my first idea was some fl<->_0 translation, and my >>

[bug #46007] texi2dvi Msys support

Additional Item Attachment, bug #46007 (project texinfo): File name: texi2dvi.diff Size:4 KB ___ Reply to this item at: ___ Message

Re: [bug #46007] texi2dvi Msys support

Le 24/09/2015 12:33, Gavin Smith a écrit : > On 23 September 2015 at 22:03, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> Anyway, with the simple patch >> https://savannah.gnu.org/bugs/download.php?file_id=34939 , texi2dvi >> works with MikTeX for the b

Re: [bug #46007] texi2dvi Msys support

Le 24/09/2015 17:27, Eli Zaretskii a écrit : >> > From: vincent.belai...@gmail.com (Vincent Belaïche) >> > Cc: Vincent Belaïche <vincent.belai...@gmail.com> , >> > Gavin Smith <gavinsmith0...@gmail.com>, >> > Texinfo <bug-texinfo@

Re: texi2dvi changes

[...] > > They you can't know what the next step if (bibtex, makeglossaries, > biber, makeindex, texindex, ...)... > [...] I meant "The*n* you can't know what the next step i*s*" Sorry for the typoes, Vincent. --- L'absence de virus dans ce courrier électronique a été vérifiée par le

texi2dvi changes

Hello Gavin, Le 22/09/2015 19:53, Gavin Smith a écrit : > Hello Vincent and everyone else, > > Information about the changes to texi2dvi that I've made: > > No longer use a trick of renaming the recorder file to *.flz. In fact, > no special tricks at all in texi2dvi to handle this case. So the >

Re: [bug #46007] texi2dvi Msys support

Le 24/09/2015 18:14, Eli Zaretskii a écrit : >> Date: Thu, 24 Sep 2015 18:09:32 +0200 >> From: Patrice Dumas <pertu...@free.fr> >> Cc: Vincent Belaïche <vincent.belai...@gmail.com>, >> bug-texinfo@gnu.org >> >>> MSYS is not bastard, i

[bug #46018] texi2any makes inconsistent EOL style

URL: Summary: texi2any makes inconsistent EOL style Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: mar. 22 sept. 2015 04:41:17 GMT Category: None

[bug #46007] texi2dvi Msys support

taken so long to reply, but since it was not clear at all to me what was really going on when using MSYS+MikTeX I had first to do some action on the MikTeX side (go on the forum, post bugs...) Le 17/09/2015 21:20, Eli Zaretskii a écrit : >> From: vincent.belai...@gmail.com (Vincent Belaïche)

Re: [bug #46007] texi2dvi Msys support

Le 23/09/2015 18:02, Eli Zaretskii a écrit : >> Date: Wed, 23 Sep 2015 15:30:19 +0100 >> From: Gavin Smith <gavinsmith0...@gmail.com> >> Cc: Eli Zaretskii <e...@gnu.org>, Vincent Belaïche >> <vincen...@users.sourceforge.net>, >> Texinfo <

Re: [bug #43122] texi2dvi does not compile enough times to get toc

Le 18/09/2015 10:56, Gavin Smith a écrit : > On 18 September 2015 at 08:09, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> It could not be so big, because we should make texi2dvi/texindex >> backward compatible with the older extensions and make the update in &

Re: texi2dvi changes

Le 25/09/2015 10:42, Gavin Smith a écrit : > On 24 September 2015 at 21:54, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >>> I pointed out that the log files were being grep'd a lot to get the >>> list of generated files. This won't happen as muc

Re: Fwd: REVIEW REQUEST - user manual generation

;8<8<8<-- end -->8>8>8>8>8 but I prefer the one with "$newline" to keep the sed command on the same line. VBR, Vincent Le 04/06/2016 à 06:59, Vincent Belaïche a écrit : > Answering to myself... > >> Hello

Re: Fwd: REVIEW REQUEST - user manual generation

Hello Gavin, Le 01/06/2016 à 22:40, Gavin Smith a écrit : > On 10 May 2016 at 10:13, Vincent Belaïche <vincent.belai...@gmail.com> wrote: >> Hello Gavin, >> >> Answering to myself: I had been a bit too hasty, patch #7 sent >> preivously was working pro

Re: Fwd: REVIEW REQUEST - user manual generation

Answering to myself... >Hello, > >Le 03/06/2016 à 18:15, Gavin Smith a écrit : >>> The problem is that my MSYS sed was version 3.02, and it did not >>> recognise \n in the replacement string when you want to make each funny >>> character on one line. I made some test with my git bash --- which

Re: problem with texi2dvi from texinfo 6.1

\catcode126=12\def\temp{' './test1.tex' '}\expandafter\endgroup\expandafter\input\expandafter{\temp}' Vincent. Le 23/02/2016 08:14, Kurt Hornik a écrit : >>>>>> Vincent Belaïche writes: > >> Dear Kurt, >> Is the issue that texi2dvi does not make enough runs?

Re: problem with texi2dvi from texinfo 6.1

OK, I got it. The problem is in function filter_files. Unfortunately when we made the changes to solve the missing \openout in log problem, we did not make any tests with not any new xref files after the first run. When this happens (ie variable xref_files_new empty) the function filter_files

Re: problem with texi2dvi from texinfo 6.1

p;&, || or if/ while. VBR, Vincent. Le 24/02/2016 08:54, Gavin Smith a écrit : > On 23 February 2016 at 23:15, Vincent Belaïche > <vincent.belai...@gmail.com> wrote: >> >> OK, I got it. The problem is in function filter_files. Unfortunately >> when we

Re: problem with texi2dvi from texinfo 6.1

dftex/con fig/pdftex.map}] [2] (test1.aux) ) Output written on test1.pdf (2 pages, 23305 bytes). Transcript written on test1.log. /bin/texi2dvi: Original xref files = /bin/texi2dvi: New xref files = /bin/texi2dvi: Removing /tmp/efrench/test1.t2d /bin/texi2dvi: done. /bin

Re: problem with texi2dvi from texinfo 6.1

Ooops... it proved out that I made the trial with a quite old texi2dvi version. Now I have used a more recent one (not yet checked whether this is the latest one) and I could reproduce the problem. I let you know when I understand why there is one single run. Vincent. >Hello Kurt, > >I think

Re: [bug #46007] texi2dvi Msys support

(Not Texinfo related: please ignore if you're not interested.) Hello Gavin, In reply of: http://lists.gnu.org/archive/html/bug-texinfo/2015-09/msg00115.html I has been a long time since I should have answered about what evolution I was thinking of concerning interacting with external

Re: problem with texi2dvi from texinfo 6.1

Le 25/02/2016 19:00, Kurt Hornik a écrit : >>>>>> Vincent Belaïche writes: > > Vincent, > > Thanks millions again for looking into this. > > You are welcome, anyway I was probably the one to blame for the bug :-$ . It was good to learn about `set -e', and a

[bug #47284] openout test clashes with --batch option

URL: Summary: openout test clashes with --batch option Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: sam. 27 févr. 2016 16:29:43 GMT Category:

[bug #47276] \typeout to log in LaTeX way index file access

URL: Summary: \typeout to log in LaTeX way index file access Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: ven. 26 févr. 2016 17:06:36 GMT

Re: problem with texi2dvi from texinfo 6.1

Dear Kurt, Is the issue that texi2dvi does not make enough runs? Could you send also a minimal example of Rd2.tex, I could then make a trial on my machine to see if I can reproduce the issue Vincent. Le 22/02/2016 22:19, Gavin Smith a écrit : > The log files you sent help a bit. They

[bug #47566] Loosing LocalData with texi2any

URL: Summary: Loosing LocalData with texi2any Project: texinfo - GNU documentation system Submitted by: vincentb1 Submitted on: mar. 29 mars 2016 18:33:01 GMT Category: makeinfo

Re: [bug #47566] Loosing LocalData with texi2any

Answers embeded below... Le 29/03/2016 22:27, Gavin Smith a écrit : > (Replying by email.) > > On 29 March 2016 at 19:33, Vincent Belaïche <invalid.nore...@gnu.org> wrote: > >> Now the problem I have is that using this non-installed version lacks >>

  1   2   >