On Thu, Jan 9, 2014 at 9:53 PM, Sergey Poznyakoff wrote:
> Hi Gavin,
>
> 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.
>
> Regards,
> Sergey
>
I am having some problem
> Namely (for the record), the potential stretchiness around the special
> characters in the url still had effect.
>
> I made the diff below, which seemed to fix this case.
I don't need to test that to know that it's the right fix :-)
Thanks!
Werner
Hi Werner,
+@raggedright
POSIX specification:@*
@url{http://www.opengroup.org/onlinepubs/9699919799/functions/posix_spawn_file_actions_addclose.html}
...
and `make gnulib.pdf' produced a result as shown in the attached
image...
Namely (for the record), the potential stretchin
On Thu, Feb 06, 2014 at 07:11:08PM +, Karl Berry wrote:
> Hi Arnold,
>
> @cindex main topic, secondary point, tertiary point
> ...
> main topicsecondary
> pointtertiary
> point
>
> Anyway, as a workaround for your immediate needs, maybe Patrice can
> point you to a hoo
On Thu, Feb 06, 2014 at 06:32:05PM +, Karl Berry wrote:
> But there is no reason why @r{} would only be used like that,
>
> Sure, agreed. (I don't believe I said there was; I was merely
> explaining why it had been done, incorrect thinking as it may have
> been.)
>
> If we really wa
On Thu, Feb 6, 2014 at 6:44 PM, Karl Berry 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.
>
> Right. So wha
Hi Arnold,
@cindex main topic, secondary point, tertiary point
...
main topicsecondary
pointtertiary
point
Well, as you know, support for the usual index features has been on the
todo list forever. I can't imagine having the time and energy to deal
with them in the fore
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.
Right. So what do you mean by "the default file encoding is set to
UTF-8"? What d
But there is no reason why @r{} would only be used like that,
Sure, agreed. (I don't believe I said there was; I was merely
explaining why it had been done, incorrect thinking as it may have
been.)
If we really want something like [lineannotation]
As far as I'm concerned, we don't, bar
I've tried to apply this patch to gnulib's git repository:
diff --git a/doc/posix-functions/posix_spawn_file_actions_addclose.texi
b/doc/posix-functions/posix_spawn_file_actions_addclose.texi
index 772093a..a0e583b 100644
--- a/doc/posix-functions/posix_spawn_file_actions_addclose.texi
+++ b/do
please find attached a patch that corrects
two spelling mistakes in txirefcard.tex.
Thanks! Will install for the next release.
Best,
Karl
On Thu, Feb 06, 2014 at 05:37:27PM +, Karl Berry wrote:
> Hi Glenn,
>
> PS Maybe consider adding a --strict flag or somesuch, which will warn
> about "things that are invalid but which are normally silently
> accepted for historical reasons"...
>
> I'm not a fan of generic options
Hi Glenn,
http://lists.gnu.org/archive/html/bug-texinfo/2013-08/msg9.html
-all-over-againly,
Basically :(.
(For example, I have just discovered that about 1% of index entries in
the Emacs manuals are useless because of this reason.)
They don't work as they should in Info,
13 matches
Mail list logo
