Re: Include path syntax on Mac

[David Wright]

On Wed 15 Aug 2018 at 22:40:57 (+0200), Hans Åberg wrote:
> 
> > On 15 Aug 2018, at 21:49, David Wright  wrote:
> > 
> > On Wed 15 Aug 2018 at 10:07:11 (+0200), Hans Åberg wrote:
> >> 
> >> Also, it seems it adds the directory before the current in the call 
> >> argument. Normally in compilers, one would expect -I to only affect input 
> >> directives occurring in files, I think.
> > 
> > I'm not quite sure what you're saying here. Do you mean that
> > 
> >lilypond -I ~/LilyLib source.ly
> > 
> > is interpreted as meaning
> > 
> >lilypond -I ~/LilyLib ~/LilyLib/source.ly
> > 
> > in MacOS?
> 
> Yes. So a file ./source.ly in the current directory won't be compiled, only 
> if the file ~/LilyLib/source.ly does not exist. 
> 
> I would have expected that -I only affects \include within the file 
> ./source.ly and others, and not the command line itself, like in GCC.

Yes, that's what I would expect too, though the way the manuals are
written, their defence could be that it says "input files", not
"include files".

So long as your source directory is relatively clean, a trivial
workaround would be seem to be to start each invocation with:

$ lilypond -I.

but even that has a limited effect because there is another, hidden,
-I that comes even earlier: LP's own files, as reported in
http://lists.gnu.org/archive/html/lilypond-user/2016-12/msg00717.html

Compounded with the problems caused by -o, there's probably every
reason to use an absolute path for the LP input file, particularly
in scripts. Perhaps the file handling could be revamped when the
major change in relative-includes is made (from #f to #t).

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-ottava Scheme script problems

[David Bellows]

Sorry everyone, it's been too long since I've used the list and forgot
to reply to all. Below is a message sent earlier indicating that
Torsten's fix solved my problem.

Thanks everyone,
Dave Bellows

Torsten, thank you very much! That seems to fix my test cases. I have
absolutely no idea what's going on in that script so I am very
grateful that you took the time to figure this out.

Sincerely,
Dave Bellows
On Wed, Aug 15, 2018 at 2:54 PM David Bellows  wrote:
>
> Elaine Alt:
>
> > But it does make me wonder whether it would work if you structured your 
> > score a bit differently?
>
> > For example,
>
> > <>\f 
> > <>\f 4
>
> Carl Sorensen:
>
> > Have you tried
>
> >  -\f or
> >  4-\f
>
> Neither of those two approaches worked.
>
> The spacer method would work but it adds a lot of complexity to how my
> program generates Lilypond files. The process is already really
> complicated.
>
> Fortunately Torsten's solution seems to do the trick, at least based
> on my tests.
>
> Dave
> On Wed, Aug 15, 2018 at 2:27 PM Flaming Hakama by Elaine
>  wrote:
> >
> >
> >>
> >> -- Forwarded message --
> >> From: David Bellows 
> >> Date: Wed, 15 Aug 2018 10:23:41 -0700
> >> Subject: Auto-ottava Scheme script problems
> >> Hello all,
> >> ...
> >>
> >> So I've been using that function daily for years and it works
> >> wonderfully. Just recently, however, I started working on adding
> >> chords to my music generating program (before you could have many
> >> different voices but just not chords) and that's when I noticed a
> >> problem.
> >>
> >> The following works as intended:
> >>
> >>  or
> >> 4
> >>
> >> but these produce errors:
> >> \f or
> >> 4\f
> >>
> >> ...
> >>
> >> The problem seems to be when there are dynamics involved with chords.
> >> Note, this does *not* happen with single notes and dynamics, only with
> >> chords and dynamics.
> >>
> >> ...
> >>
> >> Thanks,
> >> Dave Bellows
> >
> >
> >
> > Sorry I can't help directly.  But it does make me wonder whether it would 
> > work if you structured your score a bit differently?
> >
> > For example,
> >
> > <>\f 
> > <>\f 4
> >
> > Or like this:
> >
> > <<
> > {
> > % We'll need to give this first chord a definite duration for this 
> > approach to have a chance
> > 2.
> > 4
> > }
> > {
> > s2.\f
> > s4\f
> > }
> > >>
> >
> >
> > HTH,
> >
> > Elaine Alt
> > 415 . 341 .4954   "Confusion is 
> > highly underrated"
> > ela...@flaminghakama.com
> > Producer ~ Composer ~ Instrumentalist
> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-ottava Scheme script problems

[David Bellows]

Elaine Alt:

> But it does make me wonder whether it would work if you structured your score 
> a bit differently?

> For example,

> <>\f 
> <>\f 4

Carl Sorensen:

> Have you tried

>  -\f or
>  4-\f

Neither of those two approaches worked.

The spacer method would work but it adds a lot of complexity to how my
program generates Lilypond files. The process is already really
complicated.

Fortunately Torsten's solution seems to do the trick, at least based
on my tests.

Dave
On Wed, Aug 15, 2018 at 2:27 PM Flaming Hakama by Elaine
 wrote:
>
>
>>
>> -- Forwarded message --
>> From: David Bellows 
>> Date: Wed, 15 Aug 2018 10:23:41 -0700
>> Subject: Auto-ottava Scheme script problems
>> Hello all,
>> ...
>>
>> So I've been using that function daily for years and it works
>> wonderfully. Just recently, however, I started working on adding
>> chords to my music generating program (before you could have many
>> different voices but just not chords) and that's when I noticed a
>> problem.
>>
>> The following works as intended:
>>
>>  or
>> 4
>>
>> but these produce errors:
>> \f or
>> 4\f
>>
>> ...
>>
>> The problem seems to be when there are dynamics involved with chords.
>> Note, this does *not* happen with single notes and dynamics, only with
>> chords and dynamics.
>>
>> ...
>>
>> Thanks,
>> Dave Bellows
>
>
>
> Sorry I can't help directly.  But it does make me wonder whether it would 
> work if you structured your score a bit differently?
>
> For example,
>
> <>\f 
> <>\f 4
>
> Or like this:
>
> <<
> {
> % We'll need to give this first chord a definite duration for this 
> approach to have a chance
> 2.
> 4
> }
> {
> s2.\f
> s4\f
> }
> >>
>
>
> HTH,
>
> Elaine Alt
> 415 . 341 .4954   "Confusion is 
> highly underrated"
> ela...@flaminghakama.com
> Producer ~ Composer ~ Instrumentalist
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-ottava Scheme script problems

[Carl Sorensen]

On 8/15/18, 11:23 AM, "David Bellows"  wrote:



The following works as intended:

 or
4

but these produce errors:
\f or
4\f

Have you tried 

   -\f or
   4-\f

HTH,

Carl


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re:Auto-ottava Scheme script problems

[Flaming Hakama by Elaine]

>
> -- Forwarded message --
> From: David Bellows 
> Date: Wed, 15 Aug 2018 10:23:41 -0700
> Subject: Auto-ottava Scheme script problems
> Hello all,
> ...
>
> So I've been using that function daily for years and it works
> wonderfully. Just recently, however, I started working on adding
> chords to my music generating program (before you could have many
> different voices but just not chords) and that's when I noticed a
> problem.
>
> The following works as intended:
>
>  or
> 4
>
> but these produce errors:
> \f or
> 4\f
>
> ...
>
> The problem seems to be when there are dynamics involved with chords.
> Note, this does *not* happen with single notes and dynamics, only with
> chords and dynamics.
>
> ...
>
> Thanks,
> Dave Bellows
>


Sorry I can't help directly.  But it does make me wonder whether it would
work if you structured your score a bit differently?

For example,

<>\f 
<>\f 4

Or like this:

<<
{
% We'll need to give this first chord a definite duration for this
approach to have a chance
2.
4
}
{
s2.\f
s4\f
}
>>


HTH,

Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Include path syntax on Mac

[Hans Åberg]

> On 15 Aug 2018, at 21:49, David Wright  wrote:
> 
> On Wed 15 Aug 2018 at 10:07:11 (+0200), Hans Åberg wrote:
>> 
>> Also, it seems it adds the directory before the current in the call 
>> argument. Normally in compilers, one would expect -I to only affect input 
>> directives occurring in files, I think.
> 
> I'm not quite sure what you're saying here. Do you mean that
> 
>lilypond -I ~/LilyLib source.ly
> 
> is interpreted as meaning
> 
>lilypond -I ~/LilyLib ~/LilyLib/source.ly
> 
> in MacOS?

Yes. So a file ./source.ly in the current directory won't be compiled, only if 
the file ~/LilyLib/source.ly does not exist. 

I would have expected that -I only affects \include within the file ./source.ly 
and others, and not the command line itself, like in GCC.

https://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Preprocessor-Options.html#Preprocessor-Options
https://gcc.gnu.org/onlinedocs/gcc-8.2.0/gcc/Directory-Options.html#Directory-Options



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-ottava Scheme script problems

[Torsten Hämmerle]

Sorry, certainly more straight-forward way would be just to use (filter
(music-type-predicate 'note-event) to filter out the note-events only:

 (let* ((elts (filter (music-type-predicate 'note-event)
  (ly:music-property mus-expr 'elements)))
   […]


auto-ottava2.ly
  


All the best,
Torsten



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-ottava Scheme script problems

[Torsten Hämmerle]

David Bellows wrote
> The following works as intended:
> 
>  or
> 
> 4
> 
> but these produce errors:
> 
> \f or
> 
> 4\f
> 
> The error message:
> 
> GNU LilyPond 2.19.82
> Processing `auto-ottava.ly'
> Parsing...auto-ottava.ly:24:15: In procedure ly:pitch-steps in
> expression (ly:pitch-steps p):
> auto-ottava.ly:24:15: Wrong type argument in position 1 (expecting Pitch):
> ()
> 
> The problem seems to be when there are dynamics involved with chords.
> Note, this does *not* happen with single notes and dynamics, only with
> chords and dynamics.


Hi David,

In chords, all the elements have to be looped, and, as it happens, dynamics,
but also scripts like staccato etc. will be among these elements and calling
ledger-line-no passing anything other than a pitch will lead to the "Wrong
type argument" error.

Here's a quick fix (see file attached below):
Filter out pitches from the elements and use the filtered list "pitches"
instead of "elts". This way, only pitches will be passed to ledger-line-no,
and everything will work as desired.
There might be more elegant ways, but I wanted to keep the coding as
original as possible.

auto-ottava2.ly
  

HTH,
Torsten





--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Include path syntax on Mac

[David Wright]

On Wed 15 Aug 2018 at 10:07:11 (+0200), Hans Åberg wrote:
> 
> > On 15 Aug 2018, at 00:59, Urs Liska  wrote:
> > 
> > Am 15.08.2018 um 00:34 schrieb Hans Åberg:
> >>> On 14 Aug 2018, at 21:31, Urs Liska  wrote:
> >>> 
> >>> Could someone please test (or tell me directly) whether it makes a 
> >>> difference if a path passed to -I has a trailing slash or not on Mac?
> >> It seems to not matter, tried on MacOS 10.13.6.
> > 
> > That was what I expected. Thank you for testing
> 
> You are welcome.
> 
> Also, it seems it adds the directory before the current in the call argument. 
> Normally in compilers, one would expect -I to only affect input directives 
> occurring in files, I think.

I'm not quite sure what you're saying here. Do you mean that

lilypond -I ~/LilyLib source.ly

is interpreted as meaning

lilypond -I ~/LilyLib ~/LilyLib/source.ly

in MacOS?

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-ottava Scheme script problems

[Karlin High]

On 8/15/2018 12:23 PM, David Bellows wrote:

I emailed David several days ago but haven't heard from him. I'm not
sure if it was a good email address or if he's just not available
these days. In any case, I'm hoping someone on the list can spot the
problem and offer up a solution. I've attached a copy of the Scheme
script.


David Nalesnik posted a message about 5 days ago. This is vacation 
season for many people, though. A quick scroll through that script 
leaves me thinking that not very many other people here will have the 
Scheme skills needed for helping with this.

--
Karlin High
Missouri, USA

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Auto-ottava Scheme script problems

[David Bellows]

Hello all,

Several years ago David Nalesnik very kindly and generously created a
Scheme script that would automatically apply ottava markings to a
score when needed (according to my own instrument definitions). I
needed this function because my Lilypond scores are all generated
automatically by my software and there is no human intervention
allowed in that process.

So I've been using that function daily for years and it works
wonderfully. Just recently, however, I started working on adding
chords to my music generating program (before you could have many
different voices but just not chords) and that's when I noticed a
problem.

The following works as intended:

 or
4

but these produce errors:
\f or
4\f

The error message:

GNU LilyPond 2.19.82
Processing `auto-ottava.ly'
Parsing...auto-ottava.ly:24:15: In procedure ly:pitch-steps in
expression (ly:pitch-steps p):
auto-ottava.ly:24:15: Wrong type argument in position 1 (expecting Pitch): ()

The problem seems to be when there are dynamics involved with chords.
Note, this does *not* happen with single notes and dynamics, only with
chords and dynamics.

I emailed David several days ago but haven't heard from him. I'm not
sure if it was a good email address or if he's just not available
these days. In any case, I'm hoping someone on the list can spot the
problem and offer up a solution. I've attached a copy of the Scheme
script.

Thanks,
Dave Bellows
%%This program, auto-ottava.ly. creates automatic ottavation of GNU Lilypond input.

%%Copyright (C) 2014-2015  David Nalesnik

%%This program is free software: you can redistribute it and/or modify
%%it under the terms of the GNU General Public License as published by
%%the Free Software Foundation, either version 3 of the License, or
%%(at your option) any later version.

%%This program is distributed in the hope that it will be useful,
%%but WITHOUT ANY WARRANTY; without even the implied warranty of
%%MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
%%GNU General Public License for more details.

%%You should have received a copy of the GNU General Public License
%%along with this program.  If not, see .

\version "2.19.82"

#(define (ledger-line-no middle-C-pos p)
   "Returns the number of ledger-lines a pitch @var{p} will have with
middle C position @var{middle-C-pos} expressed as staff-steps from the
middle staff line."
   (let* ((ps (ly:pitch-steps p))
  (mid-staff-steps (- middle-C-pos))
  (top-line (+ mid-staff-steps 4))
  (bottom-line (- mid-staff-steps 4))
  (above? (> ps top-line))
  (below? (< ps bottom-line))
  (steps-outside-staff
   (cond
(below? (- ps bottom-line))
(above? (- ps top-line))
(else 0
 (truncate (/ steps-outside-staff 2

#(define (find-clefMiddleCPosition mus)
   (let ((clef-pos -6)) ; treble is default
 (for-some-music
  (lambda (x)
(let ((n (ly:music-property x 'symbol)))
  (and (eq? n 'middleCClefPosition)
   (set! clef-pos (ly:music-property x 'value)
  mus)
 clef-pos))

#(define clefs
   ; An alist of (clef . position of middle C) pairs.  Center line of staff = 0.
   ; For use when \ottavate is called on a music expression which begins with a
   ; clef other than treble, which has been set before that expression.
   '((treble . -6)
 (treble_8 . 1)
 (bass . 6)
 (bass_8 . 13)
 (alto . 0)
 (tenor . 2)))

#(define (make-ottava-music arg)
   (list (make-music
  'OttavaMusic
  'ottava-number arg)))

#(define (select-ottava-music str)
   (let ((options
  '(("up-an-octave" . 1)
("down-an-octave" . -1)
("up-two-octaves" . 2)
("down-two-octaves" . -2)
("loco" . 0
 (make-ottava-music (assoc-get str options

#(define naming-options
   '((short . (("up-an-octave" . "8")
   ("down-an-octave" . "8")
   ("up-two-octaves" . "15")
   ("down-two-octaves" . "15")
   ("loco" . #f)))
 (long . (("up-an-octave" . "8va")
  ("down-an-octave" . "8va bassa")
  ("up-two-octaves" . "15ma")
  ("down-two-octaves" . "15ma")
  ("loco" , #f)))
 (default . #f)))

#(define (make-alternate-name name)
   (let* ((ps (make-music
   'PropertySet
   'symbol 'ottavation
   'value name))
  (csm (make-music
'ContextSpeccedMusic
'element ps
'context-type 'Staff)))
 (list csm)))

#(define (select-name displacement name-style)
   (let* ((style (assoc-get name-style naming-options))
  (name (if style
(assoc-get displacement style)
#f)))
 (if name
 (make-alternate-name name)
 '(


ottavate =
#(define-music-function 

Re: Include path syntax on Mac

[Hans Åberg]

> On 15 Aug 2018, at 18:44, David Kastrup  wrote:
> 
> Hans Åberg  writes:
> 
>>> On 15 Aug 2018, at 17:05, David Kastrup  wrote:
>>> 
>>> C++11 would give us  I think?  Which should be
>>> good for most path manipulations.  At least I think so.
>> 
>> It was added in C++17 [1]. GCC 7 or later have -std=c++17. GCC 6 or
>> later have C++14 as default, without the -std option.
>> 
>> 1. https://en.cppreference.com/w/cpp/filesystem
> 
> I was talking about  , not  .

That is not part of the standard, so it depends on the compiler [1]. Apple 
inhouse clang has that for optional even though accepting -std=c++17, so I 
switched to clang6, where it is properly implemented.

1. https://en.cppreference.com/w/cpp/experimental



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Include path syntax on Mac

[David Kastrup]

Hans Åberg  writes:

>> On 15 Aug 2018, at 17:05, David Kastrup  wrote:
>> 
>> C++11 would give us  I think?  Which should be
>> good for most path manipulations.  At least I think so.
>
> It was added in C++17 [1]. GCC 7 or later have -std=c++17. GCC 6 or
> later have C++14 as default, without the -std option.
>
> 1. https://en.cppreference.com/w/cpp/filesystem

I was talking about  , not  .

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Include path syntax on Mac

[Hans Åberg]

> On 15 Aug 2018, at 17:05, David Kastrup  wrote:
> 
> C++11 would give us  I think?  Which should be
> good for most path manipulations.  At least I think so.

It was added in C++17 [1]. GCC 7 or later have -std=c++17. GCC 6 or later have 
C++14 as default, without the -std option.

1. https://en.cppreference.com/w/cpp/filesystem



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Include path syntax on Mac

[David Kastrup]

David Wright  writes:

> On Tue 14 Aug 2018 at 21:31:18 (+0200), Urs Liska wrote:
>> Hi all,
>> 
>> it seems LilyPond on Windows requires paths passed to the -I command
>> line option to have a trailing slash while LilyPond on Linux doesn't
>> seem to care whether there is or not (see
>> https://github.com/wbsoft/frescobaldi/issues/1094). It seems a fix
>> to the issue in Frescobaldi is to ensure there's a trailing slash to
>> the paths, which makes it work on Windows and Linux.
>> 
>> Before merging this code I'd need to know whether Mac also doesn't
>> care about the trailing slash. Obviously it accepts paths without
>> slashes, but if it should not accept them *with* slashes I'd need to
>> make the changed code aware of the OS.
>> 
>> Could someone please test (or tell me directly) whether it makes a
>> difference if a path passed to -I has a trailing slash or not on
>> Mac?
>
> It's worth bearing in mind that AFAICT -I can take a relative path.
> In windows, D: and D:\ can be different directories depending on
> circumstances. No idea about the Mac, though.
>
> Is LP constructing filenames merely by concatenating part1, delimiter
> and part2? This usually works but isn't the Right Way, hence functions
> like Python's os.path.join().

C++11 would give us  I think?  Which should be
good for most path manipulations.  At least I think so.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Changing Staffs

[Amir Teymuri]

To clarify what i mean, i was wondering if there is a command to set the
staff type back to the last one just at any point, or do i have to set a
\new PreviousStaff each time i want to cancel the current staff out and
continue with the last one?

Thank you,

Amir Teymuri writes:

> Thank you for your reply!
>
> Is there a command like \startStaff to set the staff type back to the
> previouse one, if i am in a nested staff type construction?
>
> Some thing which would have the effect of the following example for
> example:
>
>
> \version "2.19.80"
>
> \new Staff \with { \accepts RhythmicStaff \accepts DrumStaff \accepts 
> MensuralStaff }
> {
>   c'4 g'
>   \stopStaff
>   \new RhythmicStaff
>   {\omit Staff.TimeSignature c d f
>\stopStaff
>\new DrumStaff
>{\omit Staff.TimeSignature d f8 c d4
> \stopStaff
> \new MensuralStaff
> {\omit Staff.TimeSignature f e g8}
> \new DrumStaff 
> {\omit Staff.TimeSignature f c4 }
>   }
>\new RhythmicStaff 
>{\omit Staff.TimeSignature \time 3/8  g4. f d}
>  }
>   \startStaff
>
>   c''1 \bar "|."
> }
>
>
>
> David Kastrup writes:
>
>> Amir Teymuri  writes:
>>
>>> Hello,
>>>
>>> How can i change a Staff for instance from a noraml one to a
>>> RhythmicStaff and then set back to the noraml Staff?
>>>
>>> Greetings,
>>> Amir
>>
>> \version "2.19.80"
>>
>> \new Staff \with { \accepts RhythmicStaff }
>> {
>>   c'1 g'
>>   \stopStaff
>>   \new RhythmicStaff
>>   { \omit Staff.TimeSignature 8. 16 8 8 8. 16 8 8 }
>>   \startStaff
>>   c''1 \bar "|."
>> }


-- 
ateymur...@gmail.com

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Changing Staffs

[Amir Teymuri]

Thank you for your reply!

Is there a command like \startStaff to set the staff type back to the
previouse one, if i am in a nested staff type construction?

Some thing which would have the effect of the following example for
example:


\version "2.19.80"

\new Staff \with { \accepts RhythmicStaff \accepts DrumStaff \accepts 
MensuralStaff }
{
  c'4 g'
  \stopStaff
  \new RhythmicStaff
  {\omit Staff.TimeSignature c d f
   \stopStaff
   \new DrumStaff
   {\omit Staff.TimeSignature d f8 c d4
\stopStaff
\new MensuralStaff
{\omit Staff.TimeSignature f e g8}
\new DrumStaff 
{\omit Staff.TimeSignature f c4 }
  }
   \new RhythmicStaff 
   {\omit Staff.TimeSignature \time 3/8  g4. f d}
 }
  \startStaff

  c''1 \bar "|."
}



David Kastrup writes:

> Amir Teymuri  writes:
>
>> Hello,
>>
>> How can i change a Staff for instance from a noraml one to a
>> RhythmicStaff and then set back to the noraml Staff?
>>
>> Greetings,
>> Amir
>
> \version "2.19.80"
>
> \new Staff \with { \accepts RhythmicStaff }
> {
>   c'1 g'
>   \stopStaff
>   \new RhythmicStaff
>   { \omit Staff.TimeSignature 8. 16 8 8 8. 16 8 8 }
>   \startStaff
>   c''1 \bar "|."
> }


-- 
ateymur...@gmail.com

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Include path syntax on Mac

[Hans Åberg]

> On 15 Aug 2018, at 00:59, Urs Liska  wrote:
> 
> Am 15.08.2018 um 00:34 schrieb Hans Åberg:
>>> On 14 Aug 2018, at 21:31, Urs Liska  wrote:
>>> 
>>> Could someone please test (or tell me directly) whether it makes a 
>>> difference if a path passed to -I has a trailing slash or not on Mac?
>> It seems to not matter, tried on MacOS 10.13.6.
> 
> That was what I expected. Thank you for testing

You are welcome.

Also, it seems it adds the directory before the current in the call argument. 
Normally in compilers, one would expect -I to only affect input directives 
occurring in files, I think.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Question about GUB and source code update

[Phil Holmes]

make LILYPOND_BRANCH=somebranch lilypond does pull from the git branch 
specified.  I believe a simple make lilypond will pull from master, but I'm 
not absolutely certain.


--
Phil Holmes


- Original Message - 
From: "Engraver" 

To: "Phil Holmes" ; 
Sent: Wednesday, August 15, 2018 7:56 AM
Subject: Re: Question about GUB and source code update





Op 14 augustus 2018 23:06:54 schreef "Phil Holmes" :

Please look at:

http://lilypond.org/doc/v2.19/Documentation/contributor/minor-release-checklist

which I follow for "standard" development builds.

I also aim to follow "Subsequent builds" in
http://lilypond.org/doc/v2.19/Documentation/contributor/notes-on-builds-with-gub

Please let me know if this doesn't help.

--
Phil Holmes


That seems pretty complicated. Also, I'm not building 'official' releases, 
just a windows-version of Lilypond for my own use. Ideally that build is 
based on the most recent master branch. So I guess my question is: does 
GUB's command "make lilypond"  automatically perform a 'pull' of origin 
master? Or do I have to perform that step manually myself before issuing 
'make lilypond'?


Auke





- Original Message -
From: "Partitura Organum" 
To: "lilypond-user" 
Sent: Tuesday, August 14, 2018 5:07 PM
Subject: Question about GUB and source code update


Hello,

About a month ago I succeeded in getting GUB running and compiling in
VirtualBox on my Windows 10 machine. So I have now a working Windows
version of Lilypond 2.21 from the source code as it was a month ago. What
I'd like to know is: what happens if I run GUB again? Do I then build the
same Lilypond version again? Or does GUB automatically refresh the source
code and is the result a 'newer' Lilypond? I did run it again, but the
version is number is the same, so that's a bit inconclusive.

Regards,
Auke

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user







___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition Engraver and staff changes

[Engraver]

Hallo Jan-Peter,

Thanks for the clarification. I had hoped it would be possible in some 
other way. Hopefully it will be possible in a future version of the EE. 
Until then I'll do it the old-fashioned way (manually).


Auke


Op 15 augustus 2018 07:50:57 schreef Jan-Peter Voigt :

Hello Auke,

yes you are right, \change Staff cannot be used with the EE. Some time
ago I tried to make it possible, but it results in a fatal crash of
lilypond if the EE sends such an event. I add this to the issues.

Jan-Peter




Am 14.08.2018 um 21:51 schrieb Partitura Organum:
Hello all,

In organ music it is quite common that one of the hands plays a part
that is either to high or to low for the  'common' clefs, but that can
be perfectly rendered with the alto clef. Not many organists are still
able to read the alto clef, so I usually make to versions, one with the
alto clef, and one with the part distributed over two staves (see images
for an example).








Since the notes do not change, only the way they are rendered, I thought
it would be a good use case for the edition engraver.  Problem however
is that the Edition Engraver references contexts and I cannot tell one
context to become another. The command 'change Staff' cannot be used
with the Edition Engraver. Below is my (not so minimal) not-working
example. Is there a way to tell the Edition Engraver that a part should
switch Staff? Or is the Edition Engraver not suitable for my use case
(which means that I should continue to do it manually)?


%==
\include "/oll-core/package.ily"
\loadPackage edition-engraver
%\addEdition alto
\addEdition nonalto
\consistToContexts #edition-engraver Score.Staff.Voice

righthand = \relative c''{
a2 a |
b1 |
c4 b a2\trill
}

lefthand = \relative c'{
f8 e d c d c b a |
gis8 a b c d e fis gis |
a8 a, b cis d d, e fis |
}

pedal = \relative c {
b2 d  |
e1  |
a,2 c
}

lefthandnonalto=\relative c'{
\clef bass
\change Staff="right" \voiceTwo f8 e d c d c \change Staff="left"
\oneVoice b a |
gis a b c \change Staff="right" \voiceTwo d e fis gis |
a \change Staff="left" \oneVoice a, b cis d d, e fis |
}


\editionMod alto 1 0/4 left.Voice.A \clef alto

\editionMod nonalto 1 0/4 right.Voice.A \voiceOne
\editionMod nonalto 1 0/4 left.Voice.A \change Staff="right"
\editionMod nonalto 1 0/4 left.Voice.A \voiceTwo

\score {
<<
\new Staff = "right" \with {
\editionID right
}
\new Voice {  \righthand }

\new Staff = "left" \with {
\editionID left
}
%\new Voice { \lefthand}
\new Voice { \lefthandnonalto}

\new Staff {
\clef bass \pedal
}

>

}
%===

Regards,
Auke



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Question about GUB and source code update

[Engraver]

Op 14 augustus 2018 23:06:54 schreef "Phil Holmes" :

Please look at:

http://lilypond.org/doc/v2.19/Documentation/contributor/minor-release-checklist

which I follow for "standard" development builds.

I also aim to follow "Subsequent builds" in
http://lilypond.org/doc/v2.19/Documentation/contributor/notes-on-builds-with-gub

Please let me know if this doesn't help.

--
Phil Holmes


That seems pretty complicated. Also, I'm not building 'official' releases, 
just a windows-version of Lilypond for my own use. Ideally that build is 
based on the most recent master branch. So I guess my question is: does 
GUB's command "make lilypond"  automatically perform a 'pull' of origin 
master? Or do I have to perform that step manually myself before issuing 
'make lilypond'?


Auke





- Original Message -
From: "Partitura Organum" 
To: "lilypond-user" 
Sent: Tuesday, August 14, 2018 5:07 PM
Subject: Question about GUB and source code update


Hello,

About a month ago I succeeded in getting GUB running and compiling in
VirtualBox on my Windows 10 machine. So I have now a working Windows
version of Lilypond 2.21 from the source code as it was a month ago. What
I'd like to know is: what happens if I run GUB again? Do I then build the
same Lilypond version again? Or does GUB automatically refresh the source
code and is the result a 'newer' Lilypond? I did run it again, but the
version is number is the same, so that's a bit inconclusive.

Regards,
Auke

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user