success with lilypond-book

To David, Knute and Carl, I am happy to report success with running lilypond-book on Windows 10.  For users' info, these are the steps I took, as guided by David, Knute and Carl.  It is hard to tell at this point whether it would have worked if one or the other of these steps had been om

Success

Today both machines are working so fingers crossed I have seen the last of -1073741819. Downloads from http://lilypond.org/downloads/binaries/mingw/lilypond-2.19.81-1.mingw.exe> worked. My suspicion still remains something to do with file permissions/ownership but cannot pin it down.

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

On 15 January 2018 at 07:58, Urs Liska wrote: > > > Am 11. Januar 2018 05:38:29 MEZ schrieb Vaughan McAlley < > vaug...@mcalley.net.au>: > >On 8 Jan 2018 12:35 p.m., "Andrew Bernard" > >wrote: > > > >Hi Urs and All, > > > >A totally successful install on a new Ubuntu 17.10 pristine image. All >

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Am 11. Januar 2018 05:38:29 MEZ schrieb Vaughan McAlley : >On 8 Jan 2018 12:35 p.m., "Andrew Bernard" >wrote: > >Hi Urs and All, > >A totally successful install on a new Ubuntu 17.10 pristine image. All >works fine as per the source installations now updated. > >A large vote of thanks to all wh

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Am 11.01.2018 07:40, schrieb Urs Liska: Am 11.01.2018 um 05:38 schrieb Vaughan McAlley: On 8 Jan 2018 12:35 p.m., "Andrew Bernard" wrote: Hi Urs and All, A totally successful install on a new Ubuntu 17.10 pristine image. All works fine as per the source installations now updated. A large vo

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Am 11.01.2018 um 05:38 schrieb Vaughan McAlley: On 8 Jan 2018 12:35 p.m., "Andrew Bernard" > wrote: Hi Urs and All, A totally successful install on a new Ubuntu 17.10 pristine image. All works fine as per the source installations now updated.

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

On 8 Jan 2018 12:35 p.m., "Andrew Bernard" wrote: Hi Urs and All, A totally successful install on a new Ubuntu 17.10 pristine image. All works fine as per the source installations now updated. A large vote of thanks to all who untangled this ball of wool. Despite a lifetime of software developm

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Hi Urs and All, A totally successful install on a new Ubuntu 17.10 pristine image. All works fine as per the source installations now updated. A large vote of thanks to all who untangled this ball of wool. Despite a lifetime of software development experience, I kept going round in circles and ne

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

I've done a new iteration on the Wiki page. I've also added a concise walkthrough at the end that leaves out all the explanations and considerations, so it's easier to get an impression what has actually to be done. Best Urs Am 07.01.2018 um 09:18 schrieb Urs Liska: Am 07.01.2018 um 07:4

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Am 07.01.2018 um 07:43 schrieb Blöchl Bernhard: I planned to try the installation following the new description Satureday evening https://github.com/wbsoft/frescobaldi/wiki/Installing-Frescobaldi-3-on-Linux-(Package-or-Source) but had some drinks with friends in the evening ... I just read

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

I planned to try the installation following the new description Satureday evening https://github.com/wbsoft/frescobaldi/wiki/Installing-Frescobaldi-3-on-Linux-(Package-or-Source) but had some drinks with friends in the evening ... I just read the description and found: Note: As the desktop file

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Am 7. Januar 2018 00:56:53 MEZ schrieb Simon Albrecht : >Hi Urs, >I did now test the instructions on an Ubuntu 16.04 Live system, and it >seems to work (Frescobaldi is up and running; I didn't test any of the >features). There's one typo: popller->poppler. My first question would >be: what soluti

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Hi Urs, I did now test the instructions on an Ubuntu 16.04 Live system, and it seems to work (Frescobaldi is up and running; I didn't test any of the features). There's one typo: popller->poppler. My first question would be: what solution to using a .desktop file and still use the correct pyt

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Hi Urs, thanks a lot, this sounds good. I'll try it when I'll have fixed my Ubuntu 16.04 Best, Simon Am 06-Jan-2018 11:40:55 +0100 schrieb li...@openlilylib.org: Hi all, after all the discussion about getting Frescobaldi to run on distributions based on Ubuntu < 17.xx I decided to give

Re: New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

I have now finished a run-through of installation instructions. As I have once more renamed it the link is now https://github.com/wbsoft/frescobaldi/wiki/Installing-Frescobaldi-3-on-Linux-(Package-or-Source) I'd be glad about feedback: * confirmation * questions * reports about mistakes * repor

New information (success report) for Frescobaldi 3 and the Ubuntu 16.04 repositories

Hi all, after all the discussion about getting Frescobaldi to run on distributions based on Ubuntu < 17.xx I decided to give it a shot myself. TL;DR Frescobaldi *can* be installed on Ubuntu 16.04/Mint 18.3 from its own Git repositories and the Ubuntu package repositories without issues. Contex

Re: Lyrics - align first wowel of a syllable under the notehead -- SUCCESS

s? > -- View this message in context: http://www.nabble.com/Re%3A-Lyrics---align-first-wowel-of-a-syllable-under-the-noteheadSUCCESS-tp21720060p21971229.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Lyrics - align first wowel of a syllable under the notehead -- SUCCESS

s. -- View this message in context: http://www.nabble.com/Re%3A-Lyrics---align-first-wowel-of-a-syllable-under-the-noteheadSUCCESS-tp21720060p21809924.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user

Re: Lyrics - align first wowel of a syllable under the notehead -- SUCCESS

End f( e) | c \melisma d \melismaEnd c( e) a16 [ \melisma g f e ] \melismaEnd fis8 a | g1 } theLyrics = \lyricmode { Each ssyl -- lla -- ble's vowel is unnn -- der the note. } \score { << \new Voice = "melody" \theNotes \new Lyrics \lyricsto "melody" \the

Re: Lyrics - align first wowel of a syllable under the notehead -- SUCCESS

ote." (vowel-center music)) theNotes = \relative c'' { g8( c) b( a) b \melisma g \melismaEnd f( e) | c \melisma d \melismaEnd c( e) a16 [ \melisma g f e ] \melismaEnd fis8 a | g1 } theLyrics = \lyricmode { Each ssyl -- lla -- ble's vowel is unnn -- der the note. } \

Re: Lyrics - align first wowel of a syllable under the notehead -- SUCCESS

Success! It's not perfect, because it doesn't recognize that we're using a proportional font, but it looks pretty good to me. It uses vowels (characters that are always vowels) and secondary vowels (characters that are vowels only if there isn't a regular vowel, like y in eng

Re: Has anyone had success including lilypond generated EPS files into groff?

On Nov 10, 2008, at 10:31 AM, Kim Shrier wrote: On Nov 10, 2008, at 10:04 AM, Werner LEMBERG wrote: As an experiment, I wanted to create a simple troff document that would include the EPS output from lilypond. [...] I use the following command to make the test.eps file: lilypond -dback

Re: Has anyone had success including lilypond generated EPS files into groff?

On Nov 10, 2008, at 10:04 AM, Werner LEMBERG wrote: As an experiment, I wanted to create a simple troff document that would include the EPS output from lilypond. [...] I use the following command to make the test.eps file: lilypond -dbackend=eps \ -dno-gs-load-fonts \

Re: Has anyone had success including lilypond generated EPS files into groff?

> As an experiment, I wanted to create a simple troff document that > would include the EPS output from lilypond. [...] > > I use the following command to make the test.eps file: > > lilypond -dbackend=eps \ > -dno-gs-load-fonts \ > -dinclude-eps-fonts >

Has anyone had success including lilypond generated EPS files into groff?

I am using lilypond 2.11.59 on a FreeBSD 6.3 system. As an experiment, I wanted to create a simple troff document that would include the EPS output from lilypond. The lilypond source file is: \version "2.11.59" \paper{ indent=0\mm oddFooterMarkup=##f oddHeaderMarkup=##

Re: OpenBSD port - half success

Matthias Kilian wrote: Could you publish your ports somewhere on a web or ftp server or send them to me? I'm short of time, but a Lilypond port is on my long-term TODO list, too. I don't promise anything, but when I get some spare time, I'd love to assist your porting work. http://crescentisland.co

Re: OpenBSD port - half success

On Mon, Feb 14, 2005 at 01:24:32PM -0700, Matt Jibson wrote: > I have started a port for lilypond onto OpenBSD. Currently everything > builds and installs. The output is only half working, though. As an example: [...] > In addition to lilypond, I also had to create ports to autotrace, > ec-fonts-

OpenBSD port - half success

I have started a port for lilypond onto OpenBSD. Currently everything builds and installs. The output is only half working, though. As an example: http://crescentisland.com/lily/lily-240886117.pdf (this is example 3.3.2: http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond/Piano-temp

ps2pdf success!

Version 7.04 to the rescue! apt-get install gs-aladdin/unstable woody wouldn't. :-) And this worked, too. Thanks. \paper { \translator { \RhythmicStaffContext \consists Instrument_name_engraver } .