Am 23.09.2013 00:44, schrieb Janek Warchoł:
Hi,
2013/9/22 Amreg :
Hi,
Just to introduce myself: I used to write software for some time (several
decades- but never used Scheme nor Lisp), [...]
I discovered LilyPind a few months ago. I use it not only to have
"professionally-looking" scores, but
Hi,
2013/9/22 Amreg :
> Hi,
>
> Just to introduce myself: I used to write software for some time (several
> decades- but never used Scheme nor Lisp), [...]
> I discovered LilyPind a few months ago. I use it not only to have
> "professionally-looking" scores, but also (and moreover) to use its MIDI
On Sun, Sep 22, 2013 at 8:31 PM, David Kastrup wrote:
> Vik Reykja writes:
>
> > On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup wrote:
> >
> >> David Kastrup writes:
> >>
> >> Thanks for the report.
> >>
> >
> > And thank you for your quick response. This does indeed fix my minimal
> > exampl
Werner LEMBERG wrote
>> my preferred variants are
>>
>> myFile.ly~.1 or myFile.ly.1~
>
> Since man pages on Unix traditionally end with a digit
> (e.g. `lilypond.1'), I prefer
>
> myFile.ly.1~
>
> or something similar.
I'm happy with this - it also avoids confusions resulting from adding a
> my preferred variants are
>
> myFile.ly~.1 or myFile.ly.1~
Since man pages on Unix traditionally end with a digit
(e.g. `lilypond.1'), I prefer
myFile.ly.1~
or something similar.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
ht
Federico Bruni-5 wrote
> in Linux it's myFile.ly~ (where the trailing ~ makes it invisible to the
> file manager)
> so a better name would be myFile-1.ly~ myFile-2.ly~ etc.
you're absolutely right -I must have been confused when I wrote the other
way round
my preferred variants are
myFile.ly~.
Vik Reykja writes:
> On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup wrote:
>
>> David Kastrup writes:
>>
>> > Vik Reykja writes:
>> >
>> >> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to
>> try
>> >> something, I noticed my music was broken. Here is a minimal example
>
On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup wrote:
> David Kastrup writes:
>
> > Vik Reykja writes:
> >
> >> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to
> try
> >> something, I noticed my music was broken. Here is a minimal example
> >> illustrating the problem:
>
2013/9/22 Eluze
> it would nice to have a backup in convert-ly which deserves the name.
>
> actually convert-ly does backup the file being converted - but always to
> the
> same file (filename.~ly), and so the original gets quickly lost if you
> press
> the convert button twice.
>
>
probably most
David Kastrup writes:
> Vik Reykja writes:
>
>> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to try
>> something, I noticed my music was broken. Here is a minimal example
>> illustrating the problem:
>>
>> \new Lyrics \lyricmode { \skip 1.*3 }
>
> The lexer apparently thi
Vik Reykja writes:
> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to try
> something, I noticed my music was broken. Here is a minimal example
> illustrating the problem:
>
> \new Lyrics \lyricmode { \skip 1.*3 }
>
> which now gives
>
> /home/vik/minimal.ly:1:34: error: no
Amreg wrote
> Hi,
>
> (Sorry, this mail is long because I try to explain as clearly as
> possible an issue that shows up in several ways, but still keeping the
> examples minimal - the length of the mail is simply related to the
> explanations. This volume is because solving this issue could br
Amreg writes:
> 1) Consider the (very common) situation of a contemporary song,
> starting with some intro measures followed by the first verse (and as
> such, this verse is included in a global repeat that encompasses both
> the verses and the chorus, but does *not* encompass the intro).
> Usual
Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to try
something, I noticed my music was broken. Here is a minimal example
illustrating the problem:
\new Lyrics \lyricmode { \skip 1.*3 }
which now gives
/home/vik/minimal.ly:1:34: error: not a duration: 3
\new Lyrics \lyricmo
Hi,
I should have posted this mail first, but an unexpected click made me
sent my first bug report beforehand... sorry.
Just to introduce myself: I used to write software for some time
(several decades- but never used Scheme nor Lisp), so I understand what
a "minimal example" means... and th
Hi,
(Sorry, this mail is long because I try to explain as clearly as
possible an issue that shows up in several ways, but still keeping the
examples minimal - the length of the mail is simply related to the
explanations. This volume is because solving this issue could bring
noticeable changes
it would nice to have a backup in convert-ly which deserves the name.
actually convert-ly does backup the file being converted - but always to the
same file (filename.~ly), and so the original gets quickly lost if you press
the convert button twice.
I fancy a simple rule for this: add an increasi
Joachim Mairböck writes:
> The syntax of a ranged tempo specification changed from \tempo =
> ~ to \tempo = - from version 2.16 to current
> unstable, i.e. it uses a '-' instead of a '~'.
>
> This is a good change. However, a source file containing a statement
> like this and \version "2.16
2013/9/22 Joachim Mairböck
> The syntax of a ranged tempo specification changed from \tempo =
>
> ~ to \tempo = - from version 2.16 to current
> unstable, i.e. it uses a '-' instead of a '~'.
>
> This is a good change. However, a source file containing a statement like
> this and \version "
The syntax of a ranged tempo specification changed from \tempo =
~ to \tempo = - from version 2.16 to current
unstable, i.e. it uses a '-' instead of a '~'.
This is a good change. However, a source file containing a statement like
this and \version "2.16.0" doesn't compile using the current
20 matches
Mail list logo
