Il giorno mar 26 lug 2016 alle 19:36, Dan Eble ha
scritto:
I should have made it clear that I asked because my build is failing.
I’ve got makeinfo version 4.13.
Are you sure that you are using LilyDev 3? It is based on Debian stable
(Jessie) and texinfo is version 5.2:
https://packages.debia
>> I should have made it clear that I asked because my build is
>> failing. I’ve got makeinfo version 4.13.
>
> That's because Werner pushed changes requiring newer Texinfo syntax.
> Werner, can you fix this until systems like Gub and LilyDev 3 can
> support it? It is not realistic to expect pe
Dan Eble writes:
>> On Jul 26, 2016, at 07:57 , David Kastrup wrote:
>>
>> Dan Eble writes:
>>
>>> In LilyDev 3, I’ve tried “sudo apt-get install texinfo” and it tells
>>> me “texinfo is already the newest version.” Is there any easier path
>>> forward than switching to a new VM? Would the
2016-07-26 17:05 GMT+02:00 Thomas Morley :
> Hi,
>
> I had a look at
> https://sourceforge.net/p/testlilyissues/issues/4931/
>
> Any reason not to do the most simple code below?
[...]
> xNote = {
> \once \override TabNoteHead.style = #'cross
> \once \override NoteHead.style = #'cross
> \once
> On Jul 26, 2016, at 07:57 , David Kastrup wrote:
>
> Dan Eble writes:
>
>> In LilyDev 3, I’ve tried “sudo apt-get install texinfo” and it tells
>> me “texinfo is already the newest version.” Is there any easier path
>> forward than switching to a new VM? Would the latest LilyDev be
>> suff
On Tue, Jul 26, 2016 at 9:06 AM, Thomas Morley-2 [via Lilypond] <
ml-node+s1069038n193110...@n5.nabble.com> wrote:
> I had a look at
> https://sourceforge.net/p/testlilyissues/issues/4931/
> ...
>
Just for the record (and maybe this is the wrong place to record it), I
thought I'd clarify some con
> I've accepted the pull requests on GitHub and updated my system as
> above. I'm now getting a failure rebuilding Guile. I've attached the
> end of the logfile to avoid problems with line wrapping making the
> error messages unintelligible.
I've created pull request for fixing guile compilation.
> Extracting page mode and named destinations as PDFmark from the font
> less PDF. Both the PDF and the PDFmark are mixed by Ghostscript.
Aaah! Very nice idea.
If I understand the issue correctly, your solution overcomes the last
obstacle with ghostscript, so we could actually start with an
im
> Unfortunately, Ghostscript (ps2pdf) discards PDF destination names.
> So remote PDF links do not work fine.
>
> http://bugs.ghostscript.com/show_bug.cgi?id=696943
> http://bugs.ghostscript.com/show_bug.cgi?id=695760
This is much more depressing :-(
Isn't it possible to modify `texinfo.tex'
Hi,
I had a look at
https://sourceforge.net/p/testlilyissues/issues/4931/
Any reason not to do the most simple code below?
\version "2.19.45"
defaultNoteHeads = {
\revert NoteHead.style
\revert TabNoteHead.style
\revert NoteHead.font-name
\revert TabNoteHead.font-name
}
xNotesOn = {
- Original Message -
From: "Masamichi Hosoda"
To: ; ; ;
Sent: Monday, July 25, 2016 3:41 PM
Subject: Re: Gub failure
Please use 5.x – 4.x is no longer supported.
Or even better 6.x.
I've created pull request for updating texinfo to 6.1.
https://github.com/gperciva/gub/pull/25
I
Dan Eble writes:
> On Jul 24, 2016, at 13:32 , David Kastrup wrote:
>>
>> Note that even "make" builds a basic non-image version of the Info
>> files, and of course with a non-image version, the difference is quite
>> noticeable.
>>
>> At any rate, if we were to update Texinfo, it would likely
On Jul 24, 2016, at 13:32 , David Kastrup wrote:
>
> Note that even "make" builds a basic non-image version of the Info
> files, and of course with a non-image version, the difference is quite
> noticeable.
>
> At any rate, if we were to update Texinfo, it would likely make sense to
> take the n
13 matches
Mail list logo
