Re: Solaris 11 info test suite problems

On 5 June 2015 at 23:43, Karl Berry wrote: > The best option, I think, is to run "stty sane" at the end. > > Sorry to make things more complicated, but ... if we are running under > that shell on that system, I think ... changing terminal settings when > it's unnecessary does not sound good.

Re: Solaris 11 info test suite problems

On 6 June 2015 at 00:22, Karl Berry wrote: > Better to upset whatever terminal settings the user had beforehand > > Clearly, doing the stty on this system is desirable. > > Doing the stty on all systems is what I'm worried about, i.e., > upsetting things that were fine before. > > I don't

Re: Bug#779885: info: Does not display a info-file from the start, if it contains (some) multibyte characters

On 6 June 2015 at 08:24, Norbert Preining wrote: > We are updating the dir file by looping over all info files and call > install-info "$file" "$INFODIR/dir" > > I attach the gzipped version of the dir file on my system. Please have a look at coreutils.info (or coreutils.info-1) and look

Re: Solaris 11 info test suite problems

On 6 June 2015 at 00:45, Gavin Smith wrote: > On 6 June 2015 at 00:22, Karl Berry wrote: >> Better to upset whatever terminal settings the user had beforehand >> >> Clearly, doing the stty on this system is desirable. >> >> Doing the stty on all syste

Re: Bug#779885: info: Does not display a info-file from the start, if it contains (some) multibyte characters

On 6 June 2015 at 23:25, Karl Berry wrote: > Not that that particular case has anything to do with the general > problem, of course. I've been bothered with such cases off and on, but > I don't think there is any general solution. It is a fact that manuals > often have the same name as their pri

Re: info segfaults when the file being viewed is replaced

On 7 June 2015 at 11:20, Benno Schulenberg wrote: > In texinfo-5.9.93, do for example 'info/ginfo doc/info.info'. > Then in a different terminal do 'touch doc/info.texi; make' > and wait for it to complete. Now type '/what' in the > first terminal and see it segfault, leaving the terminal in > a

texinfo-5.9.95 pretest available

The next pretest for the upcoming Texinfo release is available, shortly after the last one. This incorporates only a few changes since last time, including a couple that we only just missed, unfortunately. This is what we hope to release as 6.0 next week. http://alpha.gnu.org/gnu/texinfo/texinfo

Re: texinfo-5.9.95 pretest available

> Somehow, the changes I committed in revision 6348 are not in this > tarball, although the corresponding ChangeLog entry, committed > together with those changes, is. How can that happen? I don't know. I was sure I had run "svn update", but when I ran it just now I got your changes. Updating '.

texinfo-5.9.96 pretest available

The texinfo-5.9.96 pretest is now uploaded at http://alpha.gnu.org/gnu/texinfo/texinfo-5.9.96.tar.xz ftp://alpha.gnu.org/gnu/texinfo/texinfo-5.9.96.tar.xz This is the same as the previous pretest, except that some changes that were accidentally left out the last time are now included. I apo

Some indices don't show up (was Re: backslashes, macros, indexes, texinfo)

On 2 June 2015 at 01:15, Karl Berry wrote: > Werner, David, > > Coming back to: > > http://lists.gnu.org/archive/html/bug-texinfo/2011-08/msg2.html > > where the crux of the test document is > > @macro funindex {TEXT} > @findex \TEXT\ > @kindex \TEXT\ > @c > @end macro > @funindex \relativ

Re: backslashes, macros, indexes, texinfo

On 2 June 2015 at 10:12, David Kastrup wrote: > Karl Berry writes: > >> 6) I recognize that you want me to just omit the \catcode`\\=0. That >> may solve your problem, but it creates problems for other people doing >> other things with @macro. For instance, you're invoking the macro with >> a w

Re: backslashes, macros, indexes, texinfo

On 22 June 2015 at 00:37, Gavin Smith wrote: > However, you would still want to interpret backslashes, so that "\\", > "\{" and "\}" (and maybe "\,") would be interpreted as "\", "{", "}" > and "," respecti

Re: texinfo-5.9.96 pretest available

On 20 June 2015 at 20:01, Eli Zaretskii wrote: > This builds OK with MinGW, but the Gnulib change in wchar.in.h was not > imported yet. I needed to apply it by hand. It still works fine now with your changes, right, even without the Gnulib change?

Re: backslashes, macros, indexes, texinfo

On 2 June 2015 at 10:12, David Kastrup wrote: > So I suspect that TeX may currently be the only backend that actually > tries, however imperfectly, matching the documentation, thus diverging > from the other backends. One more email on this. (Sorry if it's getting boring.) One point that may hav

Re: bug in @sub output in docbook [was: texinfo-5.9.96 pretest available]

On 24 June 2015 at 01:43, Per Bothner wrote: > A buglet in the @sub handling, at least in docbook output: > Notice the elements in the body, but they're missing in the > . > Which means inconsistent-looking output. Thanks for the report, I've fixed it. For some reason only some XML elements are

Re: backslashes, macros, indexes, texinfo

On 23 June 2015 at 18:46, David Kastrup wrote: > It seems like a reasonable idea to quote { } inside of braces in order > to allow for unmatched braces. If one quotes those, one needs to quote > \ for obvious reasons. I would guess that this had been the original > motivation for the quoting bus

Re: backslashes, macros, indexes, texinfo

On 24 June 2015 at 13:28, Gavin Smith wrote: > This makes sense because we'd need to invoke @findex like "@findex > \with@}macro" but it's being invoked like "@findex \with}macro". With > texinfo.tex, the \} is converted into a command to display an actual

Re: bug in @sub output in docbook [was: texinfo-5.9.96 pretest available]

On 24 June 2015 at 14:43, Patrice Dumas wrote: > The reason why some elements only are allowed is to generate valid > DocBook, as in not everything is accepted. I do not remember > if is allowed or not, I may have forgotten to add it. If it > is not allowed, however, I think that inconsistent-

Re: bug in @sub output in docbook [was: texinfo-5.9.96 pretest available]

On 24 June 2015 at 15:03, Gavin Smith wrote: > On 24 June 2015 at 14:43, Patrice Dumas wrote: >> The reason why some elements only are allowed is to generate valid >> DocBook, as in not everything is accepted. I do not remember >> if is allowed or not, I may have forgot

Texinfo 6.0 released

We have released version 6.0 of Texinfo, the GNU documentation format. It is available at http://ftpmirror.gnu.org/texinfo/texinfo-6.0.tar.xz http://ftpmirror.gnu.org/texinfo/texinfo-6.0.tar.gz if automatic redirection fails, the list of mirrors is at: http://www.gnu.org/prep/ftp.html Fai

Newlines in @w and sentence ends

Hi Patrice and Karl, I've working on the paragraph formatter in C and I have a question: should a newline after an end sentence character within a @w be recognized as an end of sentence and be doubled to two spaces? With the following input: @w{a. b. c. d. e.} I get the following output: a. b

Re: Newlines in @w and sentence ends

On 28 June 2015 at 19:09, Patrice Dumas wrote: >> I think that a single space character could well appear after the "c." >> or "C." in both cases. > > Unless I am missing something the fact that C. doesn't lead to an end of > sentence is unrelated to whether it is in @w or not. An upper case > le

Preparation for use of XS paragraph formatting module

ishes, Gavin Index: ChangeLog ======= --- ChangeLog (revision 6365) +++ ChangeLog (working copy) @@ -1,3 +1,46 @@ +2015-??-?? Gavin Smith + + * tp/Texinfo/Convert/Line.pm, tp/Texinfo/Convert/Paragraph.pm, + tp/Texinfo/Convert/UnFilled.pm: (

Re: Preparation for use of XS paragraph formatting module

On 29 June 2015 at 20:24, Patrice Dumas wrote: >> I didn't want to write the C code to process underlying text >> along with the main text, and also there may be performance >> implications in doing things twice. So I've changed the code to use a >> different approach. This is to insert a marker c

Re: Make output of texinfo index deterministic

On 29 June 2015 at 21:08, Chris Lamb wrote: > (Replying quickly, apologies for terseness..) > >> Do you have a list of manuals that exhibit this issue, and an >> explanation on how this can be triggered? > > https://reproducible.debian.net/dbd/unstable/amd64/mmm-mode_0.5.2-2.debbindiff.html > > or

Re: Preparation for use of XS paragraph formatting module

On 30 June 2015 at 11:48, Patrice Dumas wrote: > It seems to me to break the idea that user of an API should not care > about implementation details. This should still be the case, just that the API is different. It is true that the API has changed as a result of implementation details. It could b

Integration of a Perl XS module with an Automake build system

Hello all, I wonder if anyone could give pointers to advice on how to integrate a Perl XS module with an Automake build system? Over at the Texinfo project we're starting to replace parts of makeinfo with loadable native-code modules, for speed. The problem is that the Makefiles produced by ExtUt

Re: Preparation for use of XS paragraph formatting module

On 30 June 2015 at 18:33, Karl Berry wrote: > Beyond that, I wonder if it's desirable to have sentence spacing in > @sc{a. b} in the first place. Text set in small caps is going to be > titles or something else special where anything but frenchspacing is > going to look weird. It seems that texi

Re: Integration of a Perl XS module with an Automake build system

On 30 June 2015 at 14:25, Bob Friesenhahn wrote: > In addition to behavior issues, a major problem is that the re-link > capabilities offered by libtool are not available. If one links from the > Perl module to a shared library in the build tree, then there is the risk of > continued reference to

Re: Integration of a Perl XS module with an Automake build system

On 30 June 2015 at 22:41, Bob Friesenhahn wrote: >> as well as a heap of other variable definitions copied from the >> MakeMaker Makefile. Now I have to see how ExtUtils:MakeMaker knew what >> flags to use to see if I can replicate it. > > > These definitely come from how Perl was originally compi

Re: Integration of a Perl XS module with an Automake build system

On 30 June 2015 at 23:06, Bob Friesenhahn wrote: > On Tue, 30 Jun 2015, Gavin Smith wrote: >> >> >> What you say about using a different compiler is worrying, though, and >> I hadn't thought about it before. So basically when compiling an XS >> module, you

Re: Problem with texinfo.tex 6.0

On 1 July 2015 at 17:39, David Kastrup wrote: > There is no @relative in the source file: the requisite source reads > > @warning{Motifs to be inverted should be expressed in absolute form > or be first converted to absolute form by enclosing them in a > @code{\relative} block.} > > The definition

Re: Problem with texinfo.tex 6.0

On 1 July 2015 at 18:25, David Kastrup wrote: > Ugh. So inside of the @warning argument, ",", "{", "}" need quoting > with \ unless they are part of a macro argument themselves. >From what I understand, when getting the brace-delimited argument to @warning, braces in the argument shouldn't be qu

Re: texi2dvi is a bash script, not a Bourne shell script

On 1 July 2015 at 21:43, Gavin Smith wrote: > > I seem to remember there was something wrong about the "local" > function, but I can't remember what it was. This test for "local" is flawed: ( foo=bar test_local () { local foo=foo } test_local

Re: texi2dvi is a bash script, not a Bourne shell script

On 1 July 2015 at 08:49, Prof Brian Ripley wrote: > On Solaris 10, installed from the sources: > > swift-9% texi2dvi --version > texi2dvi (GNU Texinfo 6.0) 6363 > > and any invocation gives > > /usr/local/bin/texi2dvi: BSTINPUTS: not found Many thanks for the report; I managed to replicate this m

Re: texi2dvi is a bash script, not a Bourne shell script

On 1 July 2015 at 21:43, Gavin Smith wrote: > But we may as well rip out > the uses of local anyway Here's a patch to do this. Because of the size of this patch, and the corresponding likelihood of something being wrong, it is worth explaining my method for creating this patch. This

Re: Integration of a Perl XS module with an Automake build system

On 30 June 2015 at 23:06, Bob Friesenhahn wrote: > If you use a system which supports several completely different compilers > targeting the same ABI, you immediately find dismay unless you compile > Perl using the same compiler you plan to use. > > This is quite evident on Solaris systems which

Text decoration in node names and index entries

I'd like to propose that when @-commands that produce decoration around text are used in node names or index entries, the decoration is suppressed. For example: @node @samp{@@chapter} @chapter @samp{@@chapter} @findex @samp{@@chapter} @samp{@@chapter} @printindex fn This gives the output: Fi

Info output of @dots{} in UTF-8

At present makeinfo outputs @dots{} as the Unicode ellipsis character when "@documentencoding UTF-8" is used. I think this looks ugly in a monospaced font; see the attached picture. I'd propose that three full stops in a row be used instead: "..." to give the ellipsis more space to breathe. Any tho

Re: texi2dvi is a bash script, not a Bourne shell script

On 1 July 2015 at 08:49, Prof Brian Ripley wrote: > On Solaris 10, installed from the sources: > > swift-9% texi2dvi --version > texi2dvi (GNU Texinfo 6.0) 6363 > > and any invocation gives > > /usr/local/bin/texi2dvi: BSTINPUTS: not found > > The head of the script is > > #! /bin/sh > # texi2dvi

Menus should be optional in Texinfo source

Here's a patch to make menus optional in Texinfo source files. I based this on the code for the existing option "-c TREE_TRANSFORMATIONS=complete_tree_nodes_menus". makeinfo will now add a menu to nodes that don't have one already and output it for Info output. This simplifies the creation of Te

Re: Text decoration in node names and index entries

On 3 July 2015 at 20:51, Eli Zaretskii wrote: >> I'd like to propose that when @-commands that produce decoration >> around text are used in node names or index entries, the decoration is >> suppressed. > > I think you will take away a feature if you do that: some @-commands > change the output in

Re: find XSParagraph in t/test_utils.pl

On 5 July 2015 at 22:40, Patrice Dumas wrote: > Hello, > > I don't know if it is still relevant, but I like to run specific tests > in t/*.t like > > perl -w t/80include.t > > or, for a single test: > > perl -w t/80include.t cpp_lines > > Now XSParagraph is not found. I think that it should b

Re: Text decoration in node names and index entries

On 5 July 2015 at 22:52, Karl Berry wrote: > Which @-commands did you have in mind? > > I didn't have a list in mind. > Do you know for which commands your patch removed the decorations? > I agree about the ones you kept. Quite a few. @key - I'm not sure about this one. (Decorates like .) @c

Re: Argument of \\ has an extra } ??

On 6 July 2015 at 01:42, Norbert Preining wrote: > I had to change two occurrences of > @SOMECMD{"\X"} > to > @SOMECMD{"\\X"} > Is this expected? Yes. See this thread from a few days ago: https://lists.gnu.org/archive/html/bug-texinfo/2015-07/msg2.html

Re: Text decoration in node names and index entries

On 7 July 2015 at 16:39, Eli Zaretskii wrote: > There was this discussion in 2003: > > http://lists.gnu.org/archive/html/bug-texinfo/2003-05/msg00055.html > > (it continued in June). It mentions @value and macros as potentially > useful commands in node names. > > Also this one, which provides

Re: Integration of a Perl XS module with an Automake build system

On 3 July 2015 at 20:31, Russ Allbery wrote: > You can see the approach that I took in various of my packages, such as: > > http://git.eyrie.org/?p=kerberos/webauth.git;a=blob;f=Makefile.am;h=2cc0aba845f450afcd60a6c01e02a33cb9bdc803;hb=9d3555c7f9047f5ac1c67237379072df5b864b82 > > Search for BINDIN

Re: Build failure for texinfo revision 6402 from SVN

On 10 July 2015 at 22:12, Stefan Husmann wrote: > I get segfaults when compiling under Arch Linux for x86_64. > Thanks for reporting this. It's very useful for improving reliability. The problem appears to be here: > /bin/sh: line 15: 4053 Aborted (core dumped) ( /usr/bin/perl

Re: Build failure for texinfo revision 6402 from SVN

On 10 July 2015 at 23:30, Gavin Smith wrote: > I see there is a test > > checking whether wcwidth works reasonably in UTF-8 locales... yes > > so maybe there is some other way to set a UTF-8 locale that we should use. > > Could you try running "locale -a" and see

Re: Build failure for texinfo revision 6402 from SVN

On 11 July 2015 at 09:17, Stefan Husmann wrote: >> As you can see it's hit a snag because it tried to set the locale to >> en_US.UTF-8 but failed for some reason. >> >> We do plan on making it possible to recover from this (using >> alternative functions to process UTF-8 data), but I do find it st

Re: Build failure for texinfo revision 6402 from SVN

On 11 July 2015 at 13:13, Gavin Smith wrote: >> Hello, >> I only have de_DE.utf8. >> >> [haawda@frege texinfo]$ locale -a >> C >> POSIX >> de_DE >> de_DE.iso88591 >> de_DE.iso885915@euro >> de_DE.utf8 >> de_DE@euro >> deuts

Re: Build failure for texinfo revision 6402 from SVN

On 11 July 2015 at 17:41, Stefan Husmann wrote: > the activation of the locale for en_US.utf8 did the trick in revision 6411. > Without that activation, there were segfaults also in 6411. What's the output of "locale" for you? If your locale is "de_DE" or "de_DE.utf8", a segfault without en_US.

Re: Build failure for texinfo revision 6402 from SVN

On 11 July 2015 at 19:22, Stefan Husmann wrote: > Am 11.07.2015 um 19:24 schrieb Gavin Smith: >> On 11 July 2015 at 17:41, Stefan Husmann wrote: >> >>> the activation of the locale for en_US.utf8 did the trick in revision 6411. >>> Without that activation, ther

Re: Info reader fails to follow xrefs to anchors

On 13 July 2015 at 15:24, Ludovic Courtès wrote: > The standalone Info reader in Texinfo 6.0 fails to follow > cross-references to anchors: Following such a link leads to an unrelated > place in the document. This is a regression compared to Texinfo 5.2 > (guix.texi is one example that illustrate

Re: Info reader fails to follow xrefs to anchors

>> On 13 July 2015 at 15:24, Ludovic Courtès wrote: >>> The standalone Info reader in Texinfo 6.0 fails to follow >>> cross-references to anchors: Following such a link leads to an unrelated >>> place in the document. This is a regression compared to Texinfo 5.2 >>> (guix.texi is one example that

Re: Info reader fails to follow xrefs to anchors

On 13 July 2015 at 21:21, Ludovic Courtès wrote: > File attached. As an example: Go to “Substitutes” and try to follow the > anchors ‘daemon-substitute-urls’ and ‘client-substitute-urls’ (see > .) Here's the fix. I expect it cou

Re: (fwd) Bug#792328: info: can no longer find the Emacs manual

On 15 July 2015 at 00:23, Norbert Preining wrote: > Hi everyone, > > down here at Debian a certain inconvenience has arrived: Namely that > info cannot follow links to info files in sub-directories it seems: > In our case this is the emacs manual in the emacs-24 subdirectory: > /usr/share/

Re: Bug#792328: info: can no longer find the Emacs manual

On 15 July 2015 at 15:06, Norbert Preining wrote: > I was a bit surprised to see this, it is rather new, but several > packages are taking this approach. > >> "info emacs-24/emacs" is now interpreting "emacs-24/emacs" as a path >> relative to the current directory, because it has a slash in it. Gi

Re: (fwd) Bug#792328: info: can no longer find the Emacs manual

On 15 July 2015 at 00:23, Norbert Preining wrote: > down here at Debian a certain inconvenience has arrived: Namely that > info cannot follow links to info files in sub-directories it seems: > In our case this is the emacs manual in the emacs-24 subdirectory: > /usr/share/info/emacs-24/ema

Re: (fwd) Bug#792328: info: can no longer find the Emacs manual

On 15 July 2015 at 19:50, Gavin Smith wrote: > Here's my attempt at making this work Attached this time. Index: ChangeLog === --- ChangeLog (revision 6432) +++ ChangeLog (working copy) @@ -1,5 +1,21 @@ 2015-07-15 Gav

Re: Bug#792328: info: can no longer find the Emacs manual

On 16 July 2015 at 00:39, Norbert Preining wrote: > What works is selecting the > emacs-24/emacs > node in the dir file (start plain info without args, then select > emacs-24/emacs). > > What not works is doing > info emacs-24/emacs > on the command line That was intentional.

Re: (fwd) Bug#792328: info: can no longer find the Emacs manual

On 15 July 2015 at 16:02, Eli Zaretskii wrote: > How about a new option to the Info reader, whose meaning would be "use > the argument as a menu entry even if it looks like a file name"? None of the menu entry labels have a slash in them here. A dir entry like >> > * Emacs: (emacs-24/em

Re: It's time for a change

On 18 July 2015 at 15:28, Arthur Schwarz wrote: > The Texinfo declaration of intent is to support a wide range of monitors and > operating systems, and to have a single source document to feed many other > type documents. These goals have been achieved, and have been remarkably > done. Also print

Re: It's time for a change

On 18 July 2015 at 20:02, Per Bothner wrote: > When the texinfo tool chain fails IMO is the use of the generated info > format, > the one you see in Emacs info mode or the standalone 'info' application. > This format should be replaced by HTML - but now we're talking about HTML > as a generated fo

Re: (fwd) Bug#792328: info: can no longer find the Emacs manual

On 19 July 2015 at 22:36, Karl Berry wrote: > /usr/share/info/emacs-24/emacs.info.gz > > FWIW, to the best of my knowledge, $(infodir) has always been a flat > directory, and dir files a flat namespace. The problem of multiple > versions, similar to multiple languages, has never been

Re: Bug#792328: info: can no longer find the Emacs manual

Link to discussion for reference: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1339655.html On 21 July 2015 at 13:23, Norbert Preining wrote: >> Moreover there are many >> Info files under the "emacs-24" subdirectory that describe various >> Emacs modes, etc.? > > Right. >>

Inconsistent size of ASCII graphics as index initials

Nonalphanumeric ASCII graphic characters, like "@" and "^", can appear as initials to categorize entries in an index, but I noticed that they don't seem to have a consistent size. Looking at the "Command and Variable Index" for the Texinfo index, first I thought that the { and } were too small, but

Re: [bug #45612] Add flex entry to util/htmlxref.cnf

On 24 July 2015 at 04:20, Carlos O'Donell wrote: > When glibc generates online manuals, these manuals may contain cross > references to flex. The flex cross references don't work becuase the project > documentation is not on the gnu servers. > > Patch tested on ferdora f21 with texinfo 5.2 and wor

Re: Inconsistent size of ASCII graphics as index initials

On 23 July 2015 at 19:24, Karl Berry wrote: > Is this just a consequence of the fonts being used or is something > else going on? > > It's not the fonts as such, but the TeX constructs being used. Getting > the ASCII characters to be typeset as ASCII characters at all is enough > of a pai

Re: Inconsistent size of ASCII graphics as index initials

On 24 July 2015 at 09:55, Gavin Smith wrote: > On 23 July 2015 at 19:24, Karl Berry wrote: >> It's not the fonts as such, but the TeX constructs being used. Getting >> the ASCII characters to be typeset as ASCII characters at all is enough >> of a pain that I'

Re: Build failure for texinfo revision 6402 from SVN

On 25 July 2015 at 10:30, Stefan Husmann wrote: > Am 23.07.2015 um 13:20 schrieb Gavin Smith: >> On 11 July 2015 at 23:45, Gavin Smith wrote: >>> On 11 July 2015 at 19:22, Stefan Husmann wrote: > I use these functions to prepare and build. > > prepare() {

Re: hat accent bug

On 1 August 2015 at 22:43, Karl Berry wrote: > Thanks Ralph. I installed that change (with different names). > @math{\hat o} works for me now in the main text. > > I see that something like > @chapter @math{\hat o} > still fails, because the catcode of \ is fixed as other when the > argument is r

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 2 August 2015 at 00:18, Rob Browning wrote: >> As far as I can see, Debian is creating the "problem" by distributing >> two different versions of Emacs at the same time. So it seems to me the >> answer should come at the same level: Debian could have two different >> directories with the Emacs

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 3 August 2015 at 01:40, Rob Browning wrote: > - There's an easy way to ask specifically for the "foo X" pages. I > suppose X might be program specific, but all of the values I can > think of right now are of the form N or N.M. (i.e. GCC 5.0, Python > 2.7, Python 3.4, Emacs 24.4 (

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 3 August 2015 at 14:22, Gavin Smith wrote: > I'm wondering if we can kill two birds with one stone here and get > install-info to actually install the Info file as part of the > solution. So here's an idea. Add a --suffix option to install-info and at the same time allow u

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 3 August 2015 at 16:21, Eli Zaretskii wrote: > > I don't see how this would solve the issue at hand. Installation of a > manual is a system-wide action, whereas Rob wanted a way for a _user_ > to specify her preferred version(s) of the manual(s) to use at any > given moment. How the user acce

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 3 August 2015 at 22:55, Karl Berry wrote: > Perhaps it's naive, but I feel like I might just want a dir like this so > that I can find what I want and don't have to change global state and/or > restart the viewer just to read different versions: > > I agree. You can have that now.

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 4 August 2015 at 14:34, Eli Zaretskii wrote: >> It would still be better than what we have at the moment, though. > > In what way would it be better? I don't see any significant > improvement, just the added complexity. You could easily install and access multiple versions of manuals side-by-

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 4 August 2015 at 14:35, Eli Zaretskii wrote: >> Then there would only be one "foo.info" manual reachable for >> each element in PATH (those other than the first can be accessed with >> "info --all foo"). This means that "info foo" can only give the manual >> for a particular version of foo if t

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 4 August 2015 at 16:39, Eli Zaretskii wrote: >> You could easily install and access multiple versions of manuals >> side-by-side, by configuring with --program-suffix. Taking the example >> of Texinfo, you could access different versions of the Texinfo manual >> with "info texinfo-5.0", "info t

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 4 August 2015 at 16:44, Eli Zaretskii wrote: >> Date: Tue, 4 Aug 2015 15:27:51 +0100 >> From: Gavin Smith >> Cc: Karl Berry , 793...@bugs.debian.org, >> Texinfo , Rob Browning >> >> Suppose there are two emacs installations, one as /usr/bin/emacs,

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 4 August 2015 at 20:10, Eli Zaretskii wrote: >> Can you elaborate on what would constitute a complete solution? > > A solution that supports inter-manual links, both in Info and in HTML > formats. To do this on a per-user basis, we would need some > environment variable or/and user init file t

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 5 August 2015 at 16:06, Eli Zaretskii wrote: >> Date: Tue, 4 Aug 2015 21:20:47 +0100 >> From: Gavin Smith >> Cc: Rob Browning , 793...@bugs.debian.org, >> Texinfo >> >> > A solution that supports inter-manual links, both in Info and in HTML >&g

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 5 August 2015 at 20:05, Eli Zaretskii wrote: > If the file is created as "-o foo-1.2.3.info", there should be no need > to rewrite anything, is there? That's assuming the person installing the Info file is also creating it. Distributions of software products frequently distribute pre-built Inf

Re: a sentence ending in uppercase suppresses double space

On 6 August 2015 at 09:06, Benno Schulenberg wrote: > When a sentence in a texi document ends with an uppercase letter, > the normal second space after the period is suppressed. > > For example, when a texi doc contains "Press ^X. Then press N. > And it's gone...", the Info document that makeinf

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 4 August 2015 at 00:10, Norbert Preining wrote: > ANyway, I wan to return to the proposal I wrote some time ago and > that was discarded as not working (or unclear): > > Change info reader node search method as follows: > * if a node is going to be followed, first search *in*the*current*directo

Re: a sentence ending in uppercase suppresses double space

On 6 August 2015 at 11:18, Benno Schulenberg wrote: > An unrelated question. How can I get or formatting > in the HTML output, but not have any quotes added in the Info doc? > > I have a string, including the double quotes, that I wish to have set > in a fixed-wdith font in the HTML document, b

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 6 August 2015 at 10:43, Norbert Preining wrote: > But we also have an entry > * Eshell: (emacs-24/eshell). ... > > Then I have removed all references but the main to emacs from the > dir file, and retested, but still eshell info was found and loaded. > > So yes, it seemed to work ;-)

Re: a sentence ending in uppercase suppresses double space

On 7 August 2015 at 09:31, Benno Schulenberg wrote: > The double quotes have to be shown because the user has to type them. > It won't work without them, and other quotes won't work. Do you think the user will know that they have to type them? Single-quotes are a standard way to indicate sample

Re: scrolling behaviour of newer info has changed

On 7 August 2015 at 10:28, Benno Schulenberg wrote: > When with the current (6.0) stand-alone info I just run 'info', > am shown the top node, and type PageUp, it does not beep or > say anything. An older info (4.13) will beep and say there is > no Prev or Up node here. Also when reaching the en

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

I implemented an option in the standalone Info browser to search the subdirectory containing the current Info file when following a cross-reference to another manual, before searching through the Info file search path. Emacs Info could have a similar option. The variable is called "follow-strategy

Re: scrolling behaviour of newer info has changed

On 7 August 2015 at 23:12, Karl Berry wrote: > FWIW: > > 1) Personally, I find it convenient sometimes to just hold down the > PageUp (or Down) key and autorepeat and get to the top/bottom of the > first/final node. It seems intuitive that, if you're not at the "top", > PageUp will go up as far a

Texinfo Perl module versions (was: info: can no longer find the Emacs manual)

On 3 August 2015 at 14:22, Gavin Smith wrote: > Suppose you configure with "./configure --program-suffix=-5.2" and > there is an installable Info file "texinfo.info": ideally, the file > would be installed as "texinfo-5.2.info", and be accessible with "

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 6 August 2015 at 03:39, Eli Zaretskii wrote: >> Date: Wed, 5 Aug 2015 21:16:36 +0100 >> From: Gavin Smith >> Cc: Rob Browning , 793...@bugs.debian.org, >> Texinfo >> >> > Symlinks are less portable than init files. >> >> What o

Re: Bug#793067: Bug#792328: info: can no longer find the Emacs manual

On 8 August 2015 at 09:32, Eli Zaretskii wrote: >> problems I foresee are >> that indirect sub-file tables have hitherto never contained absolute >> paths > > Why would it need to, since this is only about renaming the basename > of the Info file, isn't it? Assuming you were asking about the abso

Re: scrolling behaviour of newer info has changed

On 7 August 2015 at 10:28, Benno Schulenberg wrote: > When with the current (6.0) stand-alone info I just run 'info', > am shown the top node, and type PageUp, it does not beep or > say anything. An older info (4.13) will beep and say there is > no Prev or Up node here. Also when reaching the en

Re: scrolling behaviour of newer info has changed

On 8 August 2015 at 13:10, Benno Schulenberg wrote: > However, this is still not the old behaviour. In the old info, > after a PageUp I could tab to the crossreferences listed on the > page. In the current info, with the cursor sitting at the bottom > of the page (when we're not at the top of th

Re: backslashes, macros, indexes, texinfo

g use of a @macro and a @rmacro for braced and whole-line arguments. Please have a play around and post if anything breaks. Index: ChangeLog ======= --- ChangeLog (revision 6513) +++ ChangeLog (working copy) @@ -1,5 +1,21 @@ 2015-08-08 Gavin Smith + * doc/texinfo.tex (\m

Re: hat accent bug

On 2 August 2015 at 22:16, Karl Berry wrote: > It could be done somehow, I'm sure. But I don't want to spend the time > to do it unless someone has a real document that really needs math in > section titles. The bug has been there since @math was created and no > one has ever complained about it

Re: info command segmentation fault

On 8 August 2015 at 16:17, Sergey Poznyakoff wrote: > That happens due to a malformed dir entry, e.g.: > >* gdbm_dump: gdbm_dump(gdbm). > > The resulting reference entry contails filename=NULL, which causes > coredump. The fix for this particular problem is attached. I don't think that is th

<    4   5   6   7   8   9   10   11   12   13   >