Johannes Schindelin skrev:
For shared repositories (such as on git.sv.gnu.org), non-fast-forwarding
pushes are not allowed.
Ok.
It would be nice with a better error message.
If I understand it correctly, what you just said is that the "--force"
option cannot be used on shared repositories.
Max
This function works rather well to make a slashed
and beamed acciaccatura with the following
parameters:
slashBeam =
{ \MakeSlash #40 #0.7 #1.7 #0.08 #0.7 #'(0 . 0) }
as long as the default grace font sizes are used.
See attached example.
It is too lengthy to place in the Notation refer
Jan Nieuwenhuizen skrev:
In software there's no such thing as a temporary solution.
Quoting the changelog:
1.3.142.rz1
===
* Added "hacky" drum notation/midi. See input/tricks/drums.ly and
ly/drumpitch.ly. Moved midi-instruments to scm.
* Added temporary nested staffgroups/choirst
Trevor Daniels wrote:
>> In either case, is there an accepted 'best' method of adding
>> a slash now, should the user wish to have one?
Mats Bengtsson wrote:
Since the general intention of LilyPond is to support many different
notation conventions (at least by tweaking some properties), I woul
If you want the same setting in all your TabStaff contexts in a .ly file
or in a set of .ly files, then the recommended solution is instead to
redefine
the default definition of TabStaff, see section "Changing context
default settings"
(such a definition can be put in a separate .ly file to be
On 10/29/07, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote:
> Am Montag, 29. Oktober 2007 schrieb Trevor Bača:
> > Unfortunately, I know of no better way to create cross-staff chords
> > than the documentation you point to in the manual.
> >
> > I'm just finishing a score with cross-staff chords, so
Hi,
Looking at the documentation for non-guitar tab staves
(http://reinhold.kainhofer.com/~lilypond/Documentation/user/lilypond/Non_002dguitar-tablatures.html
),
I realized that the example might be simplified. In particular, in the
following snippet, both staves look exactly the same:
\versi
On 10/29/07, Rune Zedeler <[EMAIL PROTECTED]> wrote:
> Back in 2001 I made a patch to allow for nested StaffGroups.
> Unfortunately the introduced cycle in the context-hierarchy introduced a
> infinite loop in lilypond, leading to a stack overflow.
> I therefore replaced the nested StaffGroups with
Since the general intention of LilyPond is to support many different
notation conventions (at least by tweaking some properties), I would
classify this as a missing feature. As far as I can recall, the workarounds
that have been posted on the mailing list require some trial and error
to get the co
Hi,
On Mon, 29 Oct 2007, Rune Zedeler wrote:
> Because I by mistake did a merge of the master into dev/rune before the last
> time I pushed to git.sv.gnu.org, I undid these changed in my local branch
> before making my new changes locally.
> But now, if I do
>
> $ git push -f ssh+git://[EMAIL PR
10 matches
Mail list logo
