Hi Gavin,
> Le 11 févr. 2020 à 10:51, Gavin Smith a écrit :
>
> Hello Akim, I believe I have fixed the issue in commit 2df5ef95a (also
> uploaded to ftp.gnu.org, so should be updated in gnulib soon). I
> turned off the "active" characters in node names when retrieving the
> section names.
I
> Le 10 févr. 2020 à 19:47, Akim Demaille a écrit :
>
> Hi!
>
> The following file is fine in non TeX output, but dies on the single-argument
> @ref in PDF, because of the +.
Sorry. That was with the latest texinfo.tex from gnulib (2019-09-24.13).
Hi!
The following file is fine in non TeX output, but dies on the single-argument
@ref in PDF, because of the +.
Cheers!
\input texinfo @c -*-texinfo-*-
@setfilename bison.info
@settitle Bison
@xrefautomaticsectiontitle on
@node Top
@top Bison
@node Chapter
@chapter Chapter
@node C++ Vari
Hi!
Structured indexes are great, thanks a lot for this! However they don't work
well for Bison for three different reasons (two "bugs", and one "missing
feature"), presented in the attachement.
> @syncodeindex fn cp
> @syncodeindex vr cp
> @syncodeindex tp cp
>
> @cindex %define @subentry a
> Le 18 juil. 2019 à 15:51, Gavin Smith a écrit :
>
> On Thu, Jul 18, 2019 at 8:04 AM Akim Demaille wrote:
>> Thanks for the suggestion. I have removed all the trailing @tab, and space
>> between rows is now consistent. It looks like a workaround to me, but it'
Hi guys!
The version of Texinfo I have (and the current source according to
http://git.savannah.gnu.org/cgit/texinfo.git/tree/doc/texinfo.texi) are
confusing about @url:
> 6.10.1 '@url' Examples
> --
>
> First, here is an example of the simplest form of '@url', with just o
Hi Gavin,
Happy new year!
> Le 1 janv. 2019 à 00:49, Gavin Smith a écrit :
>
> On Sun, Nov 11, 2018 at 06:41:02PM +0100, Akim Demaille wrote:
>> The HTML reads:
>>
>> Understanding (Bison 3.2.1)
>>
>> Is there a means to use the section name rather
Hi!
I must be doing something wrong, but I get failures when using
@setcontentsaftertitlepage in TeX (other backends are happy with it). This is
Texinfo 6.0. I tried with the current texinfo.tex.
$ cat foo.texi
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename foo.info
@setc
Hi Karl!
> Le 11 mars 2015 à 19:03, Karl Berry a écrit :
>
>Back to square one: it should be clearer, somewhere rather
>easily reachable, that compressed files are supported :)
>
> Hi Akim - I'm afraid I don't even really agree with that. My experience
> is that most users are happy if
> Le 11 mars 2015 à 18:59, Eli Zaretskii a écrit :
>
>> From: Akim Demaille
>> Date: Wed, 11 Mar 2015 18:29:38 +0100
>> Cc: Texinfo Bugs
>>
>> Back to square one: it should be clearer, somewhere rather
>> easily reachable, that compressed files are s
Hi Karl!
> Le 10 mars 2015 à 22:33, Karl Berry a écrit :
>
>is not the documentation of the info reader, and immediately
>point to it?
>
> How about avoiding flame bait, Akim :)?
Sorry about that, I was really naive here and had no idea
I was.
> 1) The standalone Info reader is not "t
Hi Gavin!
> Le 9 mars 2015 à 19:10, Gavin Smith a écrit :
>
> I expect the cross-reference to info-stnd.info is easily missed. Some
> of this could be slimmed down, for example, there are two "summary
> paragraphs" (beginning "The GNU Project distributes..." and "This file
> describes..."). Sayi
> Le 5 mars 2015 à 10:38, Gavin Smith a écrit :
>
> On 5 March 2015 at 08:42, Akim Demaille wrote:
>> I kinda discovered that info can read compressed files.
>> This is excellent news, but it seems poorly documented.
>> I can find information about install-info being
Hi all,
I kinda discovered that info can read compressed files.
This is excellent news, but it seems poorly documented.
I can find information about install-info being able to
read compressed files and compressed dir files, but that's
it!
Shouldn't install-info also support a means to compress
wh
Hi all,
The following bit of code is extracted from Bison's documentation:
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename foo.info
@settitle Sample Manual 1.0
@c %**end of header
@deftypemethod {symbol_type} {} make_@var{token} ()
@deftypemethodx {symbol_type} {} {make_@
hi Karl!
Le 5 juil. 2014 à 01:35, Karl Berry a écrit :
> Does anyone want to argue for preservation of --recode and/or
> --recode-from? Akim, Sergey? Since you two were the ones who
> originally sent me the patches. I'll give you-all a couple of days
> before I remove it :).
No, please, fine
Le 31 oct. 2012 à 22:39, Karl Berry a écrit :
>> Here is my proposal. It works for Bison.
>Ping!
>
> Sorry, my reply from a few days ago accidentally/erroneously went only
> to the list and not to you. Here it is:
> http://lists.gnu.org/archive/html/bug-texinfo/2012-10/msg00014.html
>
> I
Hi all,
Le 26 oct. 2012 à 09:39, Akim Demaille a écrit :
> Here is my proposal. It works for Bison.
Ping!
Hi Karl,
Le 25 oct. 2012 à 23:49, Karl Berry a écrit :
>Actually, why would we rename it instead of simply passing to -o the
>wanted directory, instead of creating this directory?
>
> No, this has nothing to do with -o. gendocs runs makeinfo to generate
> the split HTML, which is create
Hi all,
I don't understand too well some bits of gendocs:
opt="--html -o $PACKAGE.html $commonarg $htmlarg"
cmd="$SETLANG $MAKEINFO $opt \"$srcfile\""
echo "Generating html by node... ($cmd)"
eval "$cmd"
split_html_dir=$PACKAGE.html
(
cd ${split_html_dir} || exit 1
tar -czf "$ab
Hi Karl!
Le 24 oct. 2012 à 01:45, Karl Berry a écrit :
> Hi Akim,
>
>I propose the attached patch which provides a -I option.
>
> Sounds good. Installed (blindly), thanks.
Thanks!
>FWIW, I don't know if it's considered an error, but @centering
>@image will not center in text mode
Le 19 oct. 2012 à 23:54, Karl Berry a écrit :
> Hi Akim,
Hi Karl!
>A few images have been added to the Bison documentation
>
> Sorry to hear it. I doubt you can reasonably use gendocs in such
> circumstances, for all the reasons you have discovered. Anyway, I have
> no good answers and c
Hi all!
A few images have been added to the Bison documentation
recently, and "make web-manual" faces a couple of issues.
First of all, I'd like to point out that tex is not called
in batch mode, I think it would be nice to pass --batch
to texi2dvi to avoid hanging on stdin.
The images come in s
Hi all,
I know the issue has already been reported before, for instance
http://lists.gnu.org/archive/html/bug-texinfo/2006-05/msg00018.html
but makeinfo --html happily merges files with names that differ
only by the case.
Eli reported somewhere in the previous thread that makeinfo should
warn abo
Hi all,
texi2dvi has code that looks like this:
# we'd like to handle arbitrary input file names, especially
# foo~bar/a~b.tex, since Debian likes ~ characters.
if $catcode_special; then
# $normaltilde is just to reduce line length in this source file.
# The idea is to define \norm
Index: ChangeLog
from Akim Demaille
texi2dvi: use texindy if available.
* bin/texi2dvi (run_index): Use texindy if available.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retrieving
This is still not nice, and fragile, this is why it is not integrated
in the --help, yet. Yet, I would very much appreciate some feedback.
I use it, and it works.
Index: ChangeLog
from Akim Demaille
texi2dvi: initial support for tex4ht.
* bin/texi2dvi ($latex2html, --tex4ht
Index: ChangeLog
from Akim Demaille
texi2dvi: make $expand a regular Boolean variable.
* bin/texi2dvi ($expand): Use true/false instead of t/''.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/te
Index: ChangeLog
from Akim Demaille
texi2dvi: fix comments.
* bin/texi2dvi: here.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retrieving revision 1.147
diff -u -u -r1.147 texi2dvi
Index: ChangeLog
from Akim Demaille
texi2dvi: simplify move_to_dest.
* bin/texi2dvi (move_to_dest): Exit immediately if there is
nothing to do.
This allows to simplify the body of the loop, as we no longer have
to check whether something has to be done
Index: ChangeLog
from Akim Demaille
texi2dvi: avoid creating invisible temporary files.
* bin/texi2dvi ($t2ddir): Strip leading `./'.
Call sed once.
Index: util/texi2dvi
===
RCS file: /cvsroot/te
Index: ChangeLog
from Akim Demaille
texi2dvi: complete --help.
* bin/texi2dvi (usage): Document --html.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retrieving revision 1.145
diff
Index: ChangeLog
from Akim Demaille
texi2dvi: fix error invocations.
* bin/texi2dvi: error already reports $0, don't do it again.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2
2009-04-15 Akim Demaille
texi2dvi: simplify the handling of --no-line-error.
* bin/texi2dvi (no_line_error): Remove, rather use
line_error=false.
(run_tex): Adjust.
By the way, don't call tex --help if !$line_error.
Index: util/tex
Index: ChangeLog
from Akim Demaille
texi2dvi: be robust to a failing latex --help.
* bin/texi2dvi (run_tex): here.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retrieving revision
Index: ChangeLog
from Akim Demaille
* bin/texi2dvi (out_lang_set): New.
Use it.
(usage): Document --html, --info, --text, --ps, DVIPS and DVIPDF.
(run_tex_suite): Honor DVIPS.
(main): Support -O/--output-format.
Undocumented for now.
Index
Index: ChangeLog
from Akim Demaille
* bin/texi2dvi (ensure_dir): Die only if we could not create the
directory at all.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retrieving
ve left it, because there might happen something I don't
understand, but IMO, since we are in $tidy mode, what lies there is
only what we create with ln, so the test -f should always fire because
there is nothing (not because there is something which is not a file).
Alternative, no test, but a
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (usage): More comments.
(version): exit 0.
Reported by Karl Berry.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinf
Actually, I installed the following, sorry.
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (version): New function, to replace...
($version): this.
(usage): Document --dvipdf.
Index: util/te
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (version): New function, to replace...
($version): this.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
texi2dvi: avoid "\n" in echos to please Bash 3.2.
It is virtually impossible to find a safe means to use
echo with \n in it. So use cat and here docs.
* bin/texi2dvi ($usage): Rem
I have installed the following patch.
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Support -I dir1:dir2, as per the documentation.
Reported by Vincent Ordy.
* bin/texi2dvi: (list_concat_dirs): New.
Currently mostly a copy of absolute_filename
This was needed to be able to use -Ifoo// with foo being a directory
where fonts were installed (deeply).
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Let texi2dvi keep the trailing //.
* bin/texi2dvi ($space, $tab): New.
($IFS): Use them to be rob
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi: Don't use "local foo=`cmd`", because in that case
failures of cmd, including with set -e, will go unnoticed. So
always first declare with local, then run the assignment.
run it
from the top-level, but I don't have such a tool.
> I saw you committed your changes -- anything else left outstanding
> at this point?
I applied the following changes, so I think I'm done for now :)
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
I can't bootstrap CVS texinfo :( I think local.test is correct, but I
can't run it :(
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi: Update DVIPSHEADERS so that dvips finds its
special headers.
Don't rely on non-IFS split
I hope this can still make it in the future texi2dvi!
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Use hevea more like we use tex itself, no longer as a tool
that does everything magically.
* util/texi2dvi (run_hevea): Remove trailing spaces
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/defs.in ($latex_paragraph): New.
* util/latex2html.test (input.tex): Make it big enough to trigger
the info file splitting.
* util/texi2dvi (move_to_dest): Accept several arg
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Fix the clean invocations to hevea.
Note that this breaks document using images (to be fixed).
* util/latex2html.test (run_hevea_check): Extend to support
various build modes.
Tes
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (generated_files_get): Call uniq.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retrieving revision 1.85
diff
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> * lib/Makefile.am (DEFS): Remove, included in...
> I thought it was traditional to include -DPATHDIR=\"$(somepath)\" in
> DEFS instead of AM_CPPFLAGS. It doesn't seem like it should hurt
> anything. Is it going to be dis-recommende
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (fatal): Rename as...
(error): this.
If the exit status is 0, don't exit.
(run): New.
Use it where appropriate.
(run_dvipdf): New.
Use it.
Index: ut
Hum... Now I think about it, it would be safer to put the builds
before the srcs so that if by accident a file is present in both dirs,
the built one is kept.
That shouldn't happen though.
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/Makefile.am, info/
Le 19 juin 06 à 21:01, Karl Berry a écrit :
Support dvips and dvipdf for sake of pstricks, and to
dvipdf is a tiny wrapper that calls dvips | gs. That's fine, but the
user should have the option of specifying other dvi-to-pdf
translators.
In particular, dvipdfmx is the native t
pstricks is alive and kicking.
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Support dvips and dvipdf for sake of pstricks, and to
spare the use tweaking TEXINPUTS.
* util/defs.in (optionset_get, assert_and_remove_files): New.
* util/te
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (aux_file_p): Rename the second occurrence as...
(bibaux_file_p): this.
(run_bibtex): Use it.
(options processing, $usage): Support --dvi for symmetry and to
ease systematic
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi: Add support for latex to text and info using
hevea.
Don't document it yet, as it's preliminary and on some regards
incomplete. It is usable though.
(IFS): U
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Be robust to spaces in directory names.
* util/texi2dvi (absolute): Be robust to non directories.
(run_tex): Quote in_input properly.
(compile): Quote args of eval properly.
Index: util/te
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Unfortunately, all I can do for now is add them to the savannah bug
> list.
No problem with me :) But I had not realized you used a bug tracker.
Would you prefer bugs to be reported there instead of the list?
___
I don't know whether the following should be considered correct, but
it is accepted by makeinfo and was definitely an error: the @item was
missing.
unopened-item.texi
Description: TeXInfo document
___
Texinfo home page: http://www.gnu.org/software/tex
Sectioning commands are accepted at weird places in info and TeX modes
(below, in a @table). I have not tested the HTML output, but the XML
output is broken.
unclosed-item.texi
Description: TeXInfo document
___
Texinfo home page: http://www.gnu.org/s
The following file triggers an assertion with CVS Makeinfo with
--no-headers.
% makeinfo --no-header accents-in-menu.texi
Menu
makeinfo: ../../makeinfo/lang.c:806: cm_accent_generic_no_headers: Assertion
`end > 0' failed.
zsh: abort makeinfo --no-header accents-in-menu.texi
accent
Thanks for the report, I could reproduce and solve this issue.
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Sometimes the temporary directory remains.
Reported by Wybo Dekker.
* util/defs.in (assert_files): New.
* util/texi2dvi.test:
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (generated_files_get): Skip nonexistent files
earlier.
Index: util/texi2dvi
===
RCS file: /cvsroot/texinfo/texinfo/util/texi2dvi,v
retr
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Tar will be available only if the user takes care to download and
> install it.
> And if they are smart enough to download and install texinfo *and* bash
> *and* tex, they will 99.9% surely have done so, long ago. And even if
>
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> compile with -Werror -Wall
> I do not see -e as at all analogous to -Werror -Wall, or to errno,
> for the reason I wrote before: not all nonzero exit codes are
> errors.
That's my point: not all warnings are errors. Nevertheless,
>>> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes:
> On a more general note, most GNU packages are written in C, so
> personal preferences aside, C is the main programming language of the
> GNU Project.
That's right. It's wrong, it slows down the GNU project, but it's the
law, you are rig
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Can you please describe the situation where texi2dvi is run on a
> directory tree like the comment above suggests? I didn't think this
> could happen.
> I believe a LaTeX document might be set up that way. However, perhaps
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
> Choose Perl, Python, Ruby and I'm your man.
On a second thought, I have no idea what what I wrote means in English :)
It's a French idiom that means "I'd be ready
>>> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes:
> It strikes me that we should reimplement texi2dvi as a C program.
> Beyond certain level of complexity (which IMHO texi2dvi passed way
> back), there's no reasons to continue to stick to a shell script.
I disagree, C is about the worse l
>>> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> From: Akim Demaille <[EMAIL PROTECTED]>
>> Date: Mon, 09 Jan 2006 10:51:14 +0100
> Thanks.
>> Stop using the idiom "test && action" in favor of "if test; t
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> I'm most concerned by the set -e, myself.
Really, you shouldn't be. Sure, there may remain places where
failures are not properly controlled, but I can tell you be experience
that it is a effort that is worth. It's like deciding that you
c
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Hi Akim,
> * util/texi2dvi: set -e.
> I have had nothing but problems with -e. Whenever I have used it, I
> always end up taking it again, because a nonzero exit status simply does
> not always mean failure. Are you really
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi: set -e.
Stop using the idiom "test && action" in favor of "if test; then
action; fi".
(xref_files_save): Use tar instead of cp.
(run_makeinf
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
> Akim, would you agree with this change to the comment?
Sure.
___
Texinfo home page: http://www.gnu.org/software/texinfo/
bug-texinfo@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-texinfo
the common cases, and if there remain bugs, that
the best means to have them reported...
It doesn't work for HTML (yet).
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
Implement --mostly-clean, improve the detection of aux files.
* util/texi2dvi ($action): N
Minor details. The most interesting thing is that I realized that the
log contains the list of the auxiliary files! That's valuable information!
2005-12-19 Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (run_conversion): Rename as...
(run_core_conver
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi.test: Make sure --build=clean passes.
* util/texi2dvi: Fix the handling of --build.
Index: util/texi2dvi
===
RCS file: /cvsroot/t
Bummer! This one was really really stupid!
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi: Be sure to return to the current directory even
after obeying --clean.
Index: util/te
>>> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> However, I had the impression the patch would not cause non-symlink
>> platforms to always fail now, so they'd be no worse off than before.
>> Was that wrong? If so, the symlink stuff should probably be made
>> conditional to when the
Le 31 août 05 à 18:57, Eli Zaretskii a écrit :
Date: Wed, 31 Aug 2005 15:36:03 +0200
From: [EMAIL PROTECTED] (Karl Berry)
Cc: bug-texinfo@gnu.org
I have experienced a few failure when compiling in a directory
containing white spaces. I work around this using symbolic
links...
I in
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
This part of the patch is wrong:
> + # Get the name of the current directory.
> + filename_dir=`func_dirname "$command_line_filename"`
> + # In a clean build, we `cd', so get an abs
I have experienced a few failure when compiling in a directory
containing white spaces. I work around this using symbolic links...
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* utils/texi2dvi: Fix white space issues.
Quote uses of directory and file
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> But leaving the 8-bits there works...[in @node]
> But does it actually produce accented e's in the output?
I'm focusing on TeX issues only. Do @node names appear somewhere?
> See @xref{Été}.
> That is a new one on me. I tho
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> the section title :(
> Commands in @node names do not work with texinfo.tex.
Damn it! But leaving the 8-bits there works... But then it's @ref
that does not recognize it, even using @'. No way to have something
like the following wor
The following file does not compile properly, because of the accent in
the section title :(
src/texinfo/test-cases % texi2dvi --pdf accents-in-chapters.texinostromo
12:24
This is pdfeTeX, Version 3.14159-1.10b-2.1 (Web2C 7.4.5)
entering extended mode
(/home/akim/src/texinfo/test-cases/accent
rsevering with all this.
My pleasure :)
There's a bug in this version: -o is not respected.
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* util/texi2dvi (run_tex): Updating the output is also needed when
-o is used, not just when $tidy.
Index: util/texi2dv
EADME
- --mostlyclean
- *.t2d should probably be named (located?) after OUTPUT.dvi instead
of INPUT.tex
- ?
2005-06-09 Akim Demaille <[EMAIL PROTECTED]>
Let all the compilations happen in a local directory. This is
similar to using --clean, but the files are preserved. The
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
Akim> is there really any point?
> It's simple to implement and it's cleaner to use. It also shows a
> good example of an interface we would both like to see in many
> other tools.
Of course you're right. Thanks for keeping me a
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
>>> So the new work is merely to add *.t2d in .cvsignore (or whatever), and
>>> CLEANFILES = *.t2d in Makefile.am, until Automake is updated?
> Can we work on an interface that wi
reason to run TeX again.
# But we won't know that if the index files are out of date or
# nonexistent.
index_files=`get_index_files $orig_xref_files`
if test -n "$texindex" && test -n "$index_files"; then
verbose "Running $texindex $index_fil
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Overall, I think I'm becoming convinced that the patch is a good
> idea and should even be the new default -- provided that Automake
> will know to rm -rf *.t2d in the next release, so maintainers won't
> have to do anything once they get
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
> OTOH, if you adopt my approach--build in a subdir, but copy the xref files
> after a successful compilation, you get all the advantages from Akim's
> initial patch decription [foot-2] and you are still backward compatible.
But you lose
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
>> Don't forget people using texi2dvi with LaTeX, where there can be many
>> more runs.
> In theory yes, but I think that in the vast majority of cases two runs
> suffice.
That's not my experience, that precisely prompted for the chang
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
> So the fact that you rpeserve the dir is only an optimization (you don't
> have to run TeX twice). So the golden rule "don't optimize" applies here.
You must be kidding! How big is the biggest file you ever worked on?
Your sentence, s
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
[The thread starts in
http://lists.gnu.org/archive/html/bug-texinfo/2005-05/msg00019.html]
> finding the xref files is much easier,
> That's a good point. Finding all those aux files has always been a drag.
> Still wanna keep the
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Yeah. I'm not sure I really want to force every maintainer to play with
> their admin files. I rather suspect most of them don't need the
> advantages and never noticed a problem.
Except those would had to insert CLEANFILES by hand becau
>>> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes:
> Let all the compilations happen in a local directory.
> I've tried it out on the texinfo/doc files and didn't have any
> problems. Cool.
> One question, though -- do we really want to create the (sort of) temp
> working dir in a s
>>> "Eli" == Eli Zaretskii <[EMAIL PROTECTED]> writes:
Hi Eli!
>> The following patch transforms TeX into the program I would have liked
>> it to be :)
> You mean texi2dvi, not TeX, right?
Well, I did meant TeX, but since I won't even try to change TeX,
improving the wrapper meets my needs :
1 - 100 of 151 matches
Mail list logo
