headers
Mats Bengtsson | 1 Nov 2007 10:11
Picon
Picon
Favicon

Re: Cross-staff arpeggios

Cross-staff arpeggios already work in StaffGroups and GrandStaffs, without
adding any extra engraver:

    \score {
      \new StaffGroup {
        \set StaffGroup.connectArpeggios = ##t
        <<
          \new Staff \relative c' {
            <e g>4\arpeggio
          }
          \new Staff  \relative c {
            \clef bass
            <c e>4\arpeggio
          }
        >>
      }
    }

    /Mats

Eyolf Østrem wrote:
> In the section about arpeggios in the documentation, there is an
> example of cross-staff arpeggios in a PianoStaff context:
>
>      <at> lilypond[quote,ragged-right,fragment,relative=1,verbatim]
>     \new PianoStaff <<
>       \set PianoStaff.connectArpeggios = ##t
>       \new Staff { <c' e g c>\arpeggio }
>       \new Staff { \clef bass <c,, e g>\arpeggio }
>     >>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eyolf Østrem | 1 Nov 2007 11:22
Favicon

Re: Cross-staff arpeggios

On 01.11.2007 (10:11), Mats Bengtsson wrote:
> Cross-staff arpeggios already work in StaffGroups and GrandStaffs, without
> adding any extra engraver:

Ah, great! Thanks. Why didn't I think of that...?

e

--

-- 
   "To make a bad day worse, spend it wishing for the impossible." -Calvin
Permalink | Reply | 0 comments |
headers
Mats Bengtsson | 1 Nov 2007 11:38
Picon
Picon
Favicon

Proposed patch to modify #'style of line objects

Hi,

The current mechanism to get solid versus dashed lines in LilyPond has
been irritating me for several years. We do have the option to set
both #'style = #'line and #'style = #dashed-line but currently both
give the same result and you instead have to set #'dash-fraction = #'()
to get a solid line.

Below, you can find a patch that gives a much more intuitive behavior,
namely that #'style=#'line gives a solid line whereas #'style=#'dashed-line
gives ... guess what. This will fix 
http://code.google.com/p/lilypond/issues/detail?id=505

I realize that this might break some existing code and have tried to fix it
in the regression test files I could find (the example line-arrows.ly in LSR
has to be updated correspondingly). Also, the current behavior is mentioned
at one place in the manual, which should be updated in GDP.

Does anybody have any objections or can I submit?
Maybe I should also add a rule in convert-ly that warns everybody who 
has set
the dash-fraction property.

    /Mats

diff --git a/input/regression/line-arrows.ly 
b/input/regression/line-arrows.ly
index 7512711..10b9ae9 100644
--- a/input/regression/line-arrows.ly
+++ b/input/regression/line-arrows.ly
(Continue reading)

Permalink | Reply | 8 comments |
headers
Trevor Bača | 1 Nov 2007 14:02
Picon

Re: Proposed patch to modify #'style of line objects

On 11/1/07, Mats Bengtsson <mats.bengtsson <at> ee.kth.se> wrote:
> Hi,
>
> The current mechanism to get solid versus dashed lines in LilyPond has
> been irritating me for several years. We do have the option to set
> both #'style = #'line and #'style = #dashed-line but currently both
> give the same result and you instead have to set #'dash-fraction = #'()
> to get a solid line.
>
> Below, you can find a patch that gives a much more intuitive behavior,
> namely that #'style=#'line gives a solid line whereas #'style=#'dashed-line
> gives ... guess what. This will fix
> http://code.google.com/p/lilypond/issues/detail?id=505
>
> I realize that this might break some existing code and have tried to fix it
> in the regression test files I could find (the example line-arrows.ly in LSR
> has to be updated correspondingly). Also, the current behavior is mentioned
> at one place in the manual, which should be updated in GDP.
>
> Does anybody have any objections or can I submit?
> Maybe I should also add a rule in convert-ly that warns everybody who
> has set
> the dash-fraction property.

FWIW, I find this interface to the dashing syntax *much* preferrable.
Thank you, Mats; I really hope this makes it into the standard
distros.

--

-- 
Trevor Bača
(Continue reading)

Permalink | Reply | 0 comments |
headers
Graham Percival | 1 Nov 2007 14:10
Picon

Re: Proposed patch to modify #'style of line objects

Mats Bengtsson wrote:
> I realize that this might break some existing code and have tried to fix it
> in the regression test files I could find (the example line-arrows.ly in 
> LSR
> has to be updated correspondingly).

LSR is still on 2.10.12, so this can't be fixed until it upgrades.  (and 
that won't be until a 2.12 beta version, at the earliest)

> Also, the current behavior is mentioned
> at one place in the manual, which should be updated in GDP.

Easily done, once 2.11.35 (or .36) is out.

Cheers,
- Graham
Permalink | Reply | 5 comments |
headers
michał poręba | 1 Nov 2007 15:39
Picon

web page translation - make new LANG malfunction?

Hi

I began my translation as recomended in README file

gmake new LANG=pl

It should copy all orginal files from site/ to pl/, shouldn't it?
I miss these:
announce*.html
contact.ihtml
menu-entries.py
news.ihtml
old-news.html
search-noscript.html
search.html
template.ihtml

shell I just copy those files manually?

cheers
michał



_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Permalink | Reply | 1 comment |
headers
Valentin Villenave | 1 Nov 2007 18:56
Picon

Re: Request: Beta-testers

2007/10/31, Rune Zedeler <rz <at> daimi.au.dk>:
> On the 29th of october I posted a beta-fix for nested contexts.
> Before we polish it and include it in lily we need to ensure that it works.

Hi Rune,

I'm currently on vacation at my grandparents' (yeah I know, my life is
quite exciting) and I'm  running linux so I'm able to test your
contexts, as well as the pitches thingy.

I'll do so within this weekend. (I can't wait)

Is the nested contexts patch applied on your git branch, or do I have
to apply it on a local master branch ?

Regards,
Valentin
Permalink | Reply | 1 comment |
headers
Valentin Villenave | 1 Nov 2007 18:58
Picon

Re: Request: Beta-testers

2007/11/1, Valentin Villenave <v.villenave <at> gmail.com>:

> Is the nested contexts patch applied on your git branch, or do I have
> to apply it on a local master branch ?

Oops, I've just seen the _other_ thread.

Never mind :)
Permalink | Reply | 0 comments |
headers
Jean-Charles Malahieude | 1 Nov 2007 19:54
Picon

Re: web page translation - make new LANG malfunction?

Le 01.11.2007 15:39, michał poręba disait :
> Hi
> 
> I began my translation as recomended in README file
> 
> gmake new LANG=pl
> 
> It should copy all original files from site/ to pl/, shouldn't it?
> I miss these: [...]
> 
> shall I just copy those files manually?
> 
> cheers
> michał
> 
> 

If you have a look at the other localized directories (de, es or fr), 
you will get the list of the files you should find in your pl directory.

Jean-Charles
Permalink | Reply | 0 comments |
headers
Reinhold Kainhofer | 2 Nov 2007 21:44
Favicon
Gravatar

Re: Problem pushing the dev/kainhofer branch to git

I'm still having these problems pushing to the dev/kainhofer branch on 
git.sv.gnu.org... Does anyone know the reason and what I can do to solve it?

I even tried deleting the remote dev/kainhofer branch, but that does not work 
either with the same error message.

Currently, I can't push to dev/kainhofer, so I push everything into master 
instead (which is all but ideal).

Thanks,
Reinhold

Am Samstag, 27. Oktober 2007 schrieb Reinhold Kainhofer:
> Hi,
> I'm having a problem when I try to push my local development commits to the
> dev/kainhofer branch on the git server:
>
> updating 'refs/heads/dev/kainhofer' using 'refs/heads/kainhofer'
>   from 1cfb12c2762d614ebf09980f31de14a007be6c3d
>   to   a945d6d23581c973e6029d1db691afd147546603
> Generating pack...
> Done counting 0 objects.
> Writing 0 objects...
> Total 0 (delta 0), reused 0 (delta 0)
> fatal: unable to create 'refs/heads/dev/kainhofer.lock': File exists
> fatal: The remote end hung up unexpectedly
> error: failed to push to 'ssh://kainhofer <at> git.sv.gnu.org/srv/git/lilypond'
>
>
> Pushing to the master branch works just fine, just dev/kainhofer does not
> work. Does anyone have any idea what I can do about this?
>
> Cheers,
> Reinhold

--

-- 
------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold <at> kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
Permalink | Reply | 1 comment |

Gmane