On Sat, Aug 01, 2015 at 12:03:27AM +0100, Gavin Smith wrote:
> On 31 July 2015 at 12:16, Patrice Dumas wrote:
> > On Fri, Jul 31, 2015 at 11:32:26AM +0100, Gavin Smith wrote:
> >>
> >> There is probably something you can do with an init file, maybe by
> >> replacing/wrapping _convert_heading_comma
On 31 July 2015 at 12:16, Patrice Dumas wrote:
> On Fri, Jul 31, 2015 at 11:32:26AM +0100, Gavin Smith wrote:
>>
>> There is probably something you can do with an init file, maybe by
>> replacing/wrapping _convert_heading_command as the handler for @node.
>> >From looking at HTML.pm I didn't see a
On 31 July 2015 at 23:32, Kevin Barry wrote:
> Do you think it would be difficult to implement? We already do this in
> our build process, so there should be no problem sending some code
> (I'm not a Perl guru, but I assume it's not too hard).
No, but the difficulty of it isn't what's important.
I think it's an aesthetic choice.
Hmm. That doesn't seem like a good enough reason to break (or at best,
complicate) every cross reference mechanism that has been devised since
day one of Texinfo. If we provided the feature, we'd be implicitly
recommending, or at least not denying it, and co
On Fri, Jul 31, 2015 at 11:19 PM, Karl Berry wrote:
> use only lowercase file names in --html output
>
> Why do you need to do this? -k
I think it's an aesthetic choice. Most webpages use lower case letters
so it was decided some time ago that LilyPond's web manuals would
follow this convent
use only lowercase file names in --html output
Why do you need to do this? -k
Hi Gavin, Patrice,
Thank you both for responding.
On Fri, Jul 31, 2015 at 11:32 AM, Gavin Smith wrote:
> If you want to use the output in that way, I'm not going to discourage
> you, although you should be aware that any cross-references from other
> HTML files generated by Texinfo won't work. I
On Fri, Jul 31, 2015 at 2:12 PM, Eli Zaretskii wrote:
> > From: Michael Convey
> > Date: Fri, 31 Jul 2015 11:59:43 -0700
> > Cc: "help-texinfo@gnu.org"
> >
> > $ info -- apropos
> > \'\-\-\'
> > info: No available info files have ''--'' in their indices.
>
> Why in the world would you want
> From: Michael Convey
> Date: Fri, 31 Jul 2015 11:59:43 -0700
> Cc: "help-texinfo@gnu.org"
>
> $ info -- apropos
> \'\-\-\'
> info: No available info files have ''--'' in their indices.
Why in the world would you want to look for that? What stuff did you
_really_ want to find?
On 31 July 2015 at 19:42, Eli Zaretskii wrote:
>> From: Michael Convey
>> Date: Fri, 31 Jul 2015 10:11:10 -0700
>> Cc: "help-texinfo@gnu.org"
>>
>> For experienced users, who likely know where to look, such a tool is less
>> useful. However, for the less-experienced user, it is invaluable.
>
> Y
On Fri, Jul 31, 2015 at 1:43 AM, Gavin Smith
wrote:
> On 31 July 2015 at 02:03, Michael Convey wrote:
> > On Tue, Jul 28, 2015 at 3:26 PM, Karl Berry
> wrote:
> >>
> >>
> >> BTW, even simpler:
> >> zgrep /usr/share/info/* foo
> >
> >
> > $ zgrep /usr/share/info/*
>
> \'\-\-\'
> > gzip: '--'.
> From: Michael Convey
> Date: Fri, 31 Jul 2015 10:11:10 -0700
> Cc: "help-texinfo@gnu.org"
>
> For experienced users, who likely know where to look, such a tool is less
> useful. However, for the less-experienced user, it is invaluable.
You should use "info --apropos" instead. That searches
On Fri, Jul 31, 2015 at 4:00 AM, Gavin Smith
wrote:
> On 31 July 2015 at 01:56, Michael Convey wrote:
> > This is very helpful and I'm using it frequently.
>
> Full-text search for all Info files has been in the to-do list for a
> long time. I have some idea how it could be implemented, for exam
On 30 July 2015 at 15:19, David Oostdyk wrote:
> I made an example project, but it occurs to me that I'm not sure what
> the rules regarding file attachment to the mailing list are, so I will
> email it separately if you are willing to give it a try.
Karl sent me the example project, but it works
On Fri, Jul 31, 2015 at 11:32:26AM +0100, Gavin Smith wrote:
>
> There is probably something you can do with an init file, maybe by
> replacing/wrapping _convert_heading_command as the handler for @node.
> >From looking at HTML.pm I didn't see any way to customize the
> filenames when the output w
On 31 July 2015 at 01:56, Michael Convey wrote:
> This is very helpful and I'm using it frequently.
Full-text search for all Info files has been in the to-do list for a
long time. I have some idea how it could be implemented, for example
by going down a node's menu entries recursively, starting a
On 31 July 2015 at 00:49, Kevin Barry wrote:
> Dear All,
>
> I am working on LilyPond issue nr. 1000:
> https://code.google.com/p/lilypond/issues/detail?id=1000
> and would like some help with generating html file names.
>
> Currently we post process the output of makeinfo to make all of our
> htm
On 31 July 2015 at 02:03, Michael Convey wrote:
> On Tue, Jul 28, 2015 at 3:26 PM, Karl Berry wrote:
>>
>>
>> BTW, even simpler:
>> zgrep /usr/share/info/* foo
>
>
> $ zgrep /usr/share/info/* \'\-\-\'
> gzip: '--'.gz: No such file or directory
>
It should be "zgrep foo /usr/share/info/*", I think
18 matches
Mail list logo
