the
message [`ESC p' is invalid].
* Skip the current screen when moving between results with } and
{. This is like the -a option to the less pager.
Are these possible, or if not, could this functionality be added?
Gavin Smith
Hello,
On Sat, Jun 8, 2013 at 8:38 PM, Sergey Poznyakoff g...@gnu.org.ua wrote:
I have implemented the proposed skip current screen behavior
for the repeated searches in the SVN trunk. The new behavior is enabled
when the search-skip-screen variable is set to On (e.g. using M-x
set-variable
In the info browser in the search.c file, the regexp_search function
takes a parameter of SEARCH_BINDING *binding, which contains a
pointer to the text to be searched with a regular expression, and
offsets into the text specifying the range to be searched.
It works by replacing a character in
On Tue, Jan 7, 2014 at 10:44 PM, Karl Berry k...@freefriends.org wrote:
Hi,
the way the code is places the null character too
early if binding-start is not 0.
Thanks for the report and patch. Can you give a way (info file,
specific search to run) to observe the failure, whatever it
On Thu, Jan 9, 2014 at 9:53 PM, Sergey Poznyakoff g...@gnu.org.ua wrote:
Thanks a lot for the report and the testcase. I have fixed the bug
in the repository. For your convenience, the patch is attached.
Please let me know if it works for you.
Good work, it seems to be working now.
The attached patch implements some support for changing from a UTF-8
encoded file to an ASCII one. This is against SVN version 5400.
set_file_lc_type() checks if the file contains a Local Variables
section with a coding line. Then the convert_characters() function can
substitute characters in the
On Tue, Jan 21, 2014 at 8:46 PM, Gavin Smith gavinsmith0...@gmail.com wrote:
The attached patch implements some support for changing from a UTF-8
encoded file to an ASCII one.
Anything that replaces strings of characters in a file with strings of
unequal length potentially invalidates the tags
On Thu, Jan 30, 2014 at 11:27 PM, Karl Berry k...@freefriends.org wrote:
Hi Gavin.
I can certainly appreciate all the work you have put in, and I am happy
to hear from others on the subject. But for myself, I'm afraid I simply
do not like the results. (I don't like them in Emacs either, not
On Fri, Jan 31, 2014 at 8:01 AM, Eli Zaretskii e...@gnu.org wrote:
It is true that characters which cannot be encoded in the terminal's
encoding should be replaced with something that still leaves the text
legible. However, many characters _can_ be encoded, and Info should
use libiconv for
On Sat, Feb 1, 2014 at 8:11 AM, Eli Zaretskii e...@gnu.org wrote:
First, I think a configure time test for libiconv availability should
be added, and the code that uses libiconv should be conditioned on
HAVE_LIBICONV or some such, computed by that test.
I've managed to add the iconv module
On Sat, Feb 1, 2014 at 3:50 PM, Eli Zaretskii e...@gnu.org wrote:
This depends on what files are out there with no encoding specified.
Do you know how long makeinfo has output an encoding section? Is it
still possible today that makeinfo could output a UTF-8 file with no
encoding specified?
On Sat, Feb 1, 2014 at 5:00 PM, Eli Zaretskii e...@gnu.org wrote:
What if a file is not in UTF-8 and doesn't specify its encoding? Is it
likely, for example, that there are many files in ISO-8859-1 which
don't specify their encoding?
That could happen, yes. But I don't see any bad outcome
On Thu, Feb 6, 2014 at 6:44 PM, Karl Berry k...@freefriends.org wrote:
Hi Gavin,
that is, not output encoding -
Good.
I would think that we should leave files as they are if we don't
know their encoding - that way we don't risk breaking something that
works already.
There appears to be a typo in the Info Format Tag Table node in the
texinfo manual:
--- doc/texinfo.texi.old2014-03-21 18:51:48.0 +
+++ doc/texinfo.texi2014-03-21 18:53:09.0 +
@@ -23812,8 +23812,8 @@ Here is an example:
@example
^_
Tag Table:
-Node: Top^_89
Moving the cursor around causes some screen flickering. This patch stops this.
display.c (find_diff): Return values other than 0.
--- a/display.c
+++ b/display.c
@@ -102,7 +102,7 @@ find_diff (const char *a, size_t alen, const char
*b, size_t blen, int *ppos)
for (i = 0, mbi_init (itra, a,
On Sat, Mar 22, 2014 at 11:06 PM, Karl Berry k...@freefriends.org wrote:
Would you like to set up a (long-overdue) test framework for info? I'm
guessing that with --dribble, --strict-node-location, and other options,
it should be possible to run tests in batch.
I will look into it. Automatic
On Sat, Mar 29, 2014 at 2:34 PM, Karl Berry k...@freefriends.org wrote:
(1) It's helpful to write the ChangeLog entry too.
Should I add diffs for ChangeLog entries on proposed patches as well?
Because the date that they are actually committed to the repository
will be different. Or does this
On Thu, Apr 3, 2014 at 11:11 PM, Karl Berry k...@freefriends.org wrote:
Because this behavior has been around so long, I fear that people
setting INFOPATH now are likely to expect the merging with system
directories, despite the documentation. In other words, let's treat it
as a doc bug and
On Fri, Apr 4, 2014 at 11:10 PM, Karl Berry k...@freefriends.org wrote:
Here's another idea: a command-line option (for convenience in the
tests) and .infokey variable (for convenience for users), e.g.,
--infopath-no-default
infopath-no-default
I've implemented this. It is accessible from the
On Sun, Apr 13, 2014 at 6:51 AM, Richard PALO invalid.nore...@gnu.org wrote:
Just to communicate where the real problem lies as reported by pkgsrc users
(Mr Clausen and Mr Zingelman), the following snippet is not supported by
certain shells, namely pdksh and older bash (prior to 2.04) and older
On Tue, Apr 15, 2014 at 10:03 AM, Mohammad Akhlaghi
akhla...@astr.tohoku.ac.jp wrote:
I am reading the Texinfo manual in the emacs info mode and trying to apply
it in my own manual. It has been fantastic so far. Only when I press space
to go from section 12.1.3: '@listoffloats': Tables of
Hello,
I have seen in the mailing list archives that there has been
discussion of allowing characters like colons in node names and
indices over the years. It would be useful for languages like C++ or
anywhere else.
The idea that was floated was to have some kind of quoting in Info
format. See,
On Sat, Apr 19, 2014 at 5:47 PM, Eli Zaretskii e...@gnu.org wrote:
That's better, IMO. I think we already use ^? for different purposes
(in the Tag Table), though. Not sure if that matters, but see below.
^? characters would only be inter
I.e., no quoting of file names at all, and quoting
On Tue, Apr 22, 2014 at 9:49 AM, Patrice Dumas pertu...@free.fr wrote:
On Fri, Apr 18, 2014 at 09:28:02PM +0100, Gavin Smith wrote:
Hello,
Node specifications:
Use the same method as Next etc. in node lines. E.g. *see
label:nodename, would become *see label:q3nodenameq4 if
nodename
On Tue, May 6, 2014 at 9:04 PM, Benno Schulenberg
bensb...@justemail.net wrote:
Hi,
Trying to build texinfo from SVN (wanting to see how things
stand with the h-H issue), I run into some difficulties.
Hi, you seem to have a few issues. I will comment on the info browser
issues because I've
On Tue, May 6, 2014 at 11:09 PM, Gavin Smith gavinsmith0...@gmail.com wrote:
$ info/ginfo doc/info.info
Welcome to Info version 5.2. Type h for help, m for menu item.Segmentation
fault
Wow.
The doc/info.info seems to be fine, though, I can read it okay with the
system's own info command
On Wed, May 7, 2014 at 2:03 PM, Benno Schulenberg
bensb...@justemail.net wrote:
Hi Gavin,
On Wed, May 7, 2014, at 0:09, Gavin Smith wrote:
On Tue, May 6, 2014 at 9:04 PM, Benno Schulenberg bensb...@justemail.net
wrote:
$ info/ginfo doc/info.info
Welcome to Info version 5.2. Type h
On Thu, May 8, 2014 at 4:35 PM, Benno Schulenberg
bensb...@justemail.net wrote:
With current SVN, doing 'info/ginfo doc/info.info' seems to work.
Seems, because when I add some words to that doc/info.info file,
they don't show. Those words do show when I add the --file option.
So the bare
On Wed, May 7, 2014 at 10:06 PM, Benno Schulenberg
bensb...@justemail.net wrote:
On Wed, May 7, 2014, at 16:30, Karl Berry wrote:
Since you bring it up again, I just changed it. As we previously discussed:
h = tutorial (like Emacs Info)
H = terse cmd list
Nice, the addition of h for
I've implemented closing the info browser help window with the same
key used to open it (H now). (This was in the TODO file.) If this
looks all right the help window could be changed from saying to use
x to close it. Also, it only closes the window if the window is
currently selected - I think
On Sun, May 18, 2014 at 1:22 PM, Patrice Dumas pertu...@free.fr wrote:
Hello,
When doing an out of source check, I get the following error with
make check, in info/:
./infokey --output t/Info-config ../../../texinfo/info/t/Infokey-config
infokey: cannot create output file `t/Info-config' -
On Sun, May 18, 2014 at 12:47 PM, Patrice Dumas pertu...@free.fr wrote:
Hello,
With info tests, when doing parallel tests, with
make -j8 check
for example, there may be some failures that do not happen for
sequantial tests. It is not that much reproducible. There is something
in the log
On Sun, May 18, 2014 at 6:13 PM, Gavin Smith gavinsmith0...@gmail.com wrote:
On Sun, May 18, 2014 at 12:47 PM, Patrice Dumas pertu...@free.fr wrote:
Hello,
With info tests, when doing parallel tests, with
make -j8 check
for example, there may be some failures that do not happen
On Mon, May 19, 2014 at 10:23 PM, Karl Berry k...@freefriends.org wrote:
Is there some crazy way to avoid pty's completely? I suspect they are
inherently random trouble. I mean, tests presumably can't use a real
terminal, pseudo or otherwise, it all has to be batch anyway.
(Sorry for not
In standalone Info, there is a command M-x kill-node which is
supposed to be used to forget about nodes that are being viewed or
have been viewed. However, it doesn't work, and isn't useful anyway.
It can only be used to kill nodes that are currently being displayed,
and not in the history of a
On Sun, Jul 6, 2014 at 5:26 PM, Samuel Marshall m...@samdmarshall.com wrote:
Hello, I’ve found a number of bugs in info that are triggered as the result
of resizing the terminal window in some specific ways. I was originally going
to write up a proper ticket with a patch for this but after
(re-adding list)
On Mon, Jul 7, 2014 at 1:25 AM, Samuel Marshall m...@samdmarshall.com wrote:
From what I saw, the data isn’t being updated in sync with the window sizes.
This leads me to believe this is an issue with how quickly the window
properties are being updated vs how quickly the
On Sun, Jul 6, 2014 at 5:26 PM, Samuel Marshall m...@samdmarshall.com wrote:
I ultimately could not track down the exact cause of the negative window
height despite patching out almost every case where it could become negative.
I was able to track down a number of versions of the source code
On Fri, Aug 1, 2014 at 8:43 AM, Vincent Belaïche
invalid.nore...@gnu.org wrote:
I attached some exemple temp.texi, and the corresponding output temp.info.
The problem in temp.texi is at line 58:
* À propos de ce document:About this document. reporter les bogues, etc.
There is a missing
Like this:
C-u C-h i /path/to/arbitrary-info-file RET
Thanks, I managed to open a file.
On Sat, Aug 2, 2014 at 7:44 PM, Vincent Belaïche
invalid.nore...@gnu.org wrote:
Follow-up Comment #2, bug #42897 (project texinfo):
The EMACS info viewer is not consistent in the way as it handles the
On Sun, Aug 3, 2014 at 11:07 PM, Vincent Belaïche
vincen...@users.sourceforge.net wrote:
I do not know the info format details --- BTW is it documented somewhere
See Appendix F Info Format Specification in the texinfo manual.
From your answer I see that such kind of escaping mechanism does not
On Mon, Aug 11, 2014 at 6:59 AM, Volker Siegel invalid.nore...@gnu.org wrote:
We have opened related info pages 'cut' and 'column',
then navigated the info pages, to reach the same page, 'ls'.
For that reason, we can expect to end up on the same page.
A possible solution is to map links to
On Tue, Aug 19, 2014 at 7:28 AM, Mahlon Smith ( 马伦 )
esl.tutor@gmail.com wrote:
The largest of these is that v:5.1 ignores the '--fill-column' option.
This means that 50+ pages of documentation, carefully-formatted for
'--fill-column=78' now look really bad.
A smaller matter:
a) There
On Thu, Aug 21, 2014 at 6:22 PM, Vincent Belaïche
invalid.nore...@gnu.org wrote:
= References =
See bug report on EMACS info viewer
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18308#11.
= Position of problem =
In texinfo manual info node `(texinfo) Node Line Requirements', one can read
On Thu, Aug 21, 2014 at 11:05 PM, Vincent Belaïche
vincent.belai...@gmail.com wrote:
*References to the node* should all use that name, with no leading or
trailing spaces a single internal space.
I understand the term References to the node as anything that can be a
node reference that
(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 you first do docstring,
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 in the main file, while the
On Mon, Sep 1, 2014 at 8:40 PM, Vincent Belaïche vincent@hotmail.fr wrote:
Having translated node names isn't as important because there would be
translated headers in the contents of files/nodes saying what section
we're in. The main use would be the status bar in a browser giving the
On Sun, Sep 28, 2014 at 1:01 AM, 積丹尼 Dan Jacobson jida...@jidanni.org wrote:
On the info man page, after
Note that the man page is automatically generated from the output of
info --help.
info emacs buffers
start at buffers node within emacs manual
Please add
On Thu, Oct 2, 2014 at 5:46 PM, Ken Brown kbr...@cornell.edu wrote:
I just took over as the Cygwin maintainer of Texinfo, and I bumped into a
few (easily fixed) build problems. The first two exist in texinfo-5.2, and
the rest only in the trunk.
Thanks for the report. Comments below:
1. The
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 source code, and that it is one of the
following:
* a @ref,
--- info/termdep.h (revision 5852)
+++ info/termdep.h (working copy)
@@ -49,7 +49,7 @@
# endif /* !HAVE_TERMIO_H */
#endif /* !HAVE_TERMIOS_H */
-#ifdef GWINSZ_IN_SYS_IOCTL
+#ifndef __MINGW32__
# include sys/ioctl.h
#endif
I see the same thing
Hello Werner, I believe I have fixed the problem. Please try the
latest revision.
On Wed, Oct 29, 2014 at 8:43 AM, Werner LEMBERG w...@gnu.org wrote:
[rev. 5897, compiled on a GNU/Linux box]
The functionality of `Ctrl-s' seems to be severely broken:
Say
bash --noprofile
info texinfo
On Mon, Nov 17, 2014 at 3:42 AM, Mahlon sam_texi...@softwaresam.us wrote:
According to the documentation, the @raggedright command does not apply to
info and HTML output, obviously because the command applies only to output
formats that can produce 'justified' text. The 'info' output correctly
On Thu, Nov 20, 2014 at 5:20 AM, Mahlon sam_texi...@softwaresam.us wrote:
Without the application of CSS style, the HTML output for both @table and
@multitable could be considered unacceptable for two reasons:
1) the formatting of the HTML output is rather embarrassing, and
2) it doesn't
On Fri, Nov 28, 2014 at 6:54 AM, Per Bothner p...@bothner.com wrote:
Supposed I want to write a formula like e=mc^2 in TexInfo.
In TeX I'd like it to be typeset $e = mc^2$.
In HTML I'd like it to be typeset span class=mathe =
mcsup2/sup/span
or similar - i.e. I want to use sup2/sup. Likewise
In the Texinfo manual, under Macro Details, there is this example:
@macro linemac
@cindex whatever @c
@end macro
...
foo
@linemac
bar
It states:
Without the '@c', there will be a unwanted blank line between the
If makeinfo produces a cross-reference in a table in the Info output
and the text for the cross-reference is split across lines, then it is
not possible to follow the cross-reference. For example:
Chunk nameFirst definition point
On Thu, Dec 11, 2014 at 8:48 AM, David Kastrup d...@gnu.org wrote:
The command is supposed to be a _single_ command per document without
any printed output in the Info. Its purpose is so that the Info reader
is able to propose a corresponding web link (containing the same
content) for the
On Thu, Dec 11, 2014 at 3:45 AM, Eli Zaretskii e...@gnu.org wrote:
Perhaps the performance should be higher on the agenda than it
evidently is.
Did someone try compiling the Perl code into C?
Not me, does anyone know how to do that?
There is a chance for speedups with the current project to
On Fri, Dec 12, 2014 at 4:54 AM, Per Bothner p...@bothner.com wrote:
May I suggest some tweaks for how @quotation and @indentedblock are
translated?
Currently, in HTML, @quotation becomes a blockquote, while @indentedblock
becomes plain div class=indentedblock - and then we use CSS to indent.
On Wed, Dec 17, 2014 at 10:42 PM, Karl Berry k...@freefriends.org wrote:
I am aware that W3C wants everyone to use CSS for everything, but my
experience with what works best is different, and I don't think it's a
good idea to just do things because W3C says so.
Using basic HTML tags like
On Thu, Dec 18, 2014 at 3:57 PM, Ineiev ine...@gnu.org wrote:
On Thu, Dec 18, 2014 at 03:41:40PM +, Gavin Smith wrote:
On Wed, Dec 17, 2014 at 10:42 PM, Karl Berry k...@freefriends.org wrote:
(BTW, does lynx/etc. render CSS?)
I just tried the HTML output for @indentedblock in Lynx
On Thu, Dec 18, 2014 at 4:35 PM, Ineiev ine...@gnu.org wrote:
I attach what lynx prints for me (what I see on the screen is colored,
but the indents are the same). The first paragraph, Here is
an indented block:, has the same indent as the subsequent one,
US and Cuba are to start talks to
On Thu, Dec 18, 2014 at 11:58 PM, Karl Berry k...@freefriends.org wrote:
for example using semantic
output could allow better accessibility
No question. But that's not what's going on here.
Neither blockquote nor css indent is especially semantic.
If anything, blockquote is more so.
Thanks for your welcome, everybody, and thanks to Karl for your
support and work maintaining Texinfo.
On Tue, Dec 23, 2014 at 4:49 PM, Patrice Dumas pertu...@free.fr wrote:
First of all it is a bit unclear where this html comes from. In
general, both texi2html and texi2any/makeinfo, especially for makeinfo
starting at version 5 render properly nested html tags.
Could it be coming from some
The problem is that for a couple of months now, the most recent
HTML version is HTML5, and it does /not/ specify these elements.
Granted, there’re browsers which still support these, but I
could easily imagine a new browser project being started that
On Mon, Dec 22, 2014 at 10:59 PM, Mahlon sam_texi...@softwaresam.us wrote:
Yes, that's an interesting idea. @quotation, @indentedblock, @example,
@display and their @small. . . counterparts could receive class
designations.
I believe they already have class designations that you could use to
On Wed, Dec 24, 2014 at 5:53 PM, Eli Zaretskii e...@gnu.org wrote:
Looking through the code in display_update_window_1, I don't see any
attempt to handle this situation. Does the code assume that writing a
character at the last column of the last display line doesn't cause
such a scroll? If
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
I wonder if there's a way to avoid such severe breakage during
development. Is there perhaps some CI-type buildbot somewhere that
the project uses? If so, is it possible to set it up to try the MinGW
(cross-)build as well?
On Wed, Dec 24, 2014 at 5:53 PM, Eli Zaretskii e...@gnu.org wrote:
While working on the MinGW port of Info, I noticed an annoying
problem: the welcome message displayed in the echo area when the
reader starts up causes the entire display to scroll up one line,
which messes up the display until
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
. memrchr and asprintf are being used, but the corresponding Gnulib
modules were not imported, and so the build on any platform that
lacks these is broken.
I've tried to add these gnulib modules.
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii e...@gnu.org wrote:
In addition, there are non-fatal warnings: libiconv routines are
called with 'char **' arguments where the functions expect to get a
'const char **' argument, and there's one case of conflicting
prototypes in pcterm.c. Patch
On Thu, Dec 25, 2014 at 3:51 PM, Eli Zaretskii e...@gnu.org wrote:
Today I discovered that the Info reader built from the current trunk
cannot display any Info file that was produced natively on Windows (as
opposed to Info files that come from distribution tarballs, which were
produced on
On Thu, Dec 25, 2014 at 3:55 PM, Eli Zaretskii e...@gnu.org wrote:
Date: Fri, 07 Nov 2014 17:55:36 +1000
From: Jason Hood jad...@yahoo.com.au
* enhances the gnulib stat replacement to provide meaningful values for
st_ino st_dev, thus enabling detection of duplicate directories;
This was
On Fri, Dec 26, 2014 at 9:52 PM, Eli Zaretskii e...@gnu.org wrote:
It's a broken file. I have no idea how they produced it, but it
wasn't by stock makeinfo 4.8 on Windows, because that version already
did both count byte offsets in makeinfo disregarding the CR
characters, and had the EOL
On Thu, Dec 25, 2014 at 5:58 PM, Eli Zaretskii e...@gnu.org wrote:
All the documentation I have looked at for iconv doesn't show
const for any of the arguments.
I have in my include/iconv.h:
#ifndef LIBICONV_PLUG
#define iconv libiconv
#endif
extern size_t iconv (iconv_t cd, const
On Fri, Jan 2, 2015 at 11:26 AM, Eli Zaretskii e...@gnu.org wrote:
However, I see an annoying delay when going to a different node. For
example, in the Emacs Lisp manual, go to the Index node, move to the
end of the index, type RET on one of the last entries, then type 'l'
to go back. Bot
On Sat, Jan 3, 2015 at 3:29 PM, Eli Zaretskii e...@gnu.org wrote:
The bottle-neck is clearly process_node_text, it takes more than 1 sec
when the node is Index in the ELisp manual.
I timed the loop in process_node_text, and it takes about 0.22 msec
per line on the average, and there are 5700
On Fri, Feb 6, 2015 at 11:54 PM, Karl Berry k...@freefriends.org wrote:
I notice that @w can block newlines.
I'm not sure what you mean.
The purpose of @w{...} is to have absolutely no line breaks in the
argument. The bug I see in your sample output is that @w{@ref{...}}
does still
On Sat, Feb 7, 2015 at 6:29 AM, Werner LEMBERG w...@gnu.org wrote:
While running
info texinfo
(info compiled from r6104), entering
C-s \ \
results in
Failing Regexp I-search: \\
while info 4.13 correctly finds
* Special Characters:: Inserting @ {} , \ #
Thanks
A few times I have struggled to find the documentation of some Texinfo
commands (like @w, or @c) because there isn't an index entry which is
the command name exactly. (Pressing icret in the info browser takes
you to the node Printing Indices and Menus.) I think it would be
best to have an index
On Fri, Feb 6, 2015 at 4:50 PM, Eli Zaretskii e...@gnu.org wrote:
How about if the 'i' command puts first in the list of candidates the
entry whose beginning matches what the user typed exactly?
That would be a good idea - for 'I' as well.
On Fri, Feb 6, 2015 at 4:52 PM, Andreas Schwab sch...@linux-m68k.org wrote:
(texinfo) Command and Variable Index already lists all commands, but @c
is listed as 'c (comment)' and @w as 'w (prevent line break)'.
I understand that - I think they should be listed as 'c' and 'w' as well.
I just noticed for the Info output of the following,
@example
y@c
x
aaa
bb
@end example,
there is no indent for the line with x at all. The output looks like
==
This is text.info, produced by makeinfo version 5.2dev from text.texi.
y
x
On Fri, Feb 6, 2015 at 4:33 PM, Gavin Smith gavinsmith0...@gmail.com wrote:
On Wed, Dec 3, 2014 at 8:22 PM, Gavin Smith gavinsmith0...@gmail.com wrote:
If makeinfo produces a cross-reference in a table in the Info output
and the text for the cross-reference is split across lines
On Wed, Dec 3, 2014 at 8:22 PM, Gavin Smith gavinsmith0...@gmail.com wrote:
If makeinfo produces a cross-reference in a table in the Info output
and the text for the cross-reference is split across lines, then it is
not possible to follow the cross-reference.
I should note
On Wed, Jan 14, 2015 at 5:57 PM, Eli Zaretskii e...@gnu.org wrote:
Date: Wed, 14 Jan 2015 10:42:08 +
From: Gavin Smith gavinsmith0...@gmail.com
Cc: Texinfo bug-texinfo@gnu.org
int
wcwidth (wchar_t wc)
#undef wcwidth
{
/* In UTF-8 locales, use a Unicode aware width function
On Tue, Jan 27, 2015 at 6:14 PM, Werner LEMBERG w...@gnu.org wrote:
Doing
./autogen.sh
./configure
make
I get
...
/bin/sh .../texinfo.compiled/build-aux/missing \
help2man --name=translate Texinfo documents \
-I ./makeinfo.h2m ..//tp/makeinfo -o makeinfo.1
On Wed, Jan 28, 2015 at 10:34 AM, Werner LEMBERG w...@gnu.org wrote:
Still happening with rev 6069.
I suspect your man/Makefile is out of date for it still be trying to
build texindex under util/. I tried running make distclean,
followed by ./autogen.sh, ./configure and make and it got
On Tue, Jan 27, 2015 at 6:14 PM, Werner LEMBERG w...@gnu.org wrote:
Doing
./autogen.sh
./configure
make
I get
...
/bin/sh .../texinfo.compiled/build-aux/missing \
help2man --name=translate Texinfo documents \
-I ./makeinfo.h2m ..//tp/makeinfo -o makeinfo.1
On Thu, Jan 29, 2015 at 10:23 AM, Vitezslav Crhonek
invalid.nore...@gnu.org wrote:
There's just minor issue - when compiling with -Werror=format-security, the
build fails:
info.c: In function 'main':
info.c:908:9: error: format not a string literal and no format arguments
In file included from ./stdlib.h:42:0,
from exitfail.c:22:
./stddef.h:93:3: error: conflicting types for 'max_align_t'
} max_align_t;
^
In file included from ./stddef.h:55:0,
from ./stdlib.h:42,
from exitfail.c:22:
On Thu, Jan 29, 2015 at 3:01 AM, Nathan Royce naro...@hotmail.com wrote:
Testsuite summary for GNU Texinfo 5.2dev
# TOTAL: 68
# PASS: 31
On Sat, Jan 24, 2015 at 6:07 PM, Werner LEMBERG w...@gnu.org wrote:
Walter has written a `txi-ca.tex' file for Catalan
Walter has written about support of the middle dot in Catalan.
(Wikipedia link http://en.wikipedia.org/wiki/Interpunct#Catalan).
So · should be admitted to produce l·l , L·L,
On Sat, Jan 10, 2015 at 1:43 PM, Andreas Schwab sch...@linux-m68k.org wrote:
Gavin Smith gavinsmith0...@gmail.com writes:
We should probably follow what TeX does in such circumstances. Does anyone
know?
Plain TeX sets \sfcode`\)=0 \sfcode`\'=0 \sfcode`\]=0, which makes these
three
Thanks for the report. The error message is No rule to build
texindex, right? Karl is in the process of integrating the new
texindex implementation into the package so maybe he is aware of this
error already.
It looks like it is trying to build the C texindex in the util
directory, and failing.
I think the rules to build texindex.1 in man/Makefile.am have to be
removed or updated.
On Sun, Jan 11, 2015 at 11:35 AM, Gavin Smith gavinsmith0...@gmail.com wrote:
Thanks for the report. The error message is No rule to build
texindex, right? Karl is in the process of integrating the new
On Sat, Jan 10, 2015 at 3:31 PM, Eli Zaretskii e...@gnu.org wrote:
Date: Thu, 8 Jan 2015 11:00:40 +
From: Gavin Smith gavinsmith0...@gmail.com
Cc: Texinfo bug-texinfo@gnu.org
On Sat, Jan 3, 2015 at 3:29 PM, Eli Zaretskii e...@gnu.org wrote:
As you see, wcwidth and locale_charset, both
1 - 100 of 2304 matches
Mail list logo
