half-dot

Some time ago I posted a query/suggestion/observation regarding a notation convention I saw in a piece we were performing in our orchestra. Following a notehead, in the position of a dot, there was a small '×'. Upon examination it became clear that it was, in effect, a 'half-dot'. It added o

Re: half-dot

2010/3/26 David Bobroff : > Now, however, this notation convention has appeared again in another piece > by a different composer.  An example can bee seen here: > > http://centrum.is/~bobroff/lilypond/half-dot.png As a first step, you can do the following to make quarter+16th to appear as plain qu

Re: Enhancement request: Termination message for lilypond compilations

On 25/03/10 00:22, Han-Wen Nienhuys wrote: On Wed, Mar 24, 2010 at 6:31 PM, Ian Hulin wrote: I've always thought it a real shame that the standard set of messages from lilypond left you with a nagging sense of uncertainty whether it had actually completed or not. Typically, you would see this:

Re: Enhancement request: Termination message for lilypond compilations

(lilypond "$*"&& echo Success) || echo Failed 1. Lilypond is a multi-OS application, it doesn't just run under bash on a Linux-derived OS (e.g cmd on Windows, running from detached "gui" environment from JEdit or Frescobaldi - btw JEdit could also be running under Windows). Doesn't LilyP

Re: half-dot

Francisco Vila wrote: 2010/3/26 David Bobroff : Now, however, this notation convention has appeared again in another piece by a different composer.  An example can bee seen here: http://centrum.is/~bobroff/lilypond/half-dot.png As a first step, you can do the following

Re: half-dot

On 3/26/2010 1:22 PM, Bertalan Fodor (LilyPondTool) wrote: Francisco Vila wrote: 2010/3/26 David Bobroff : Now, however, this notation convention has appeared again in another piece by a different composer.  An example can bee seen here: http://centrum.is/~bobroff/lily

Re: all must do a new clone - new git repository with fixed history

2010/3/25 Jan Nieuwenhuizen : > Hi, > > The git repository at savannah has been updated, everyone > should do a fresh clone. I am trying to merge master into lilypond/translation. >From your last commit (which you have commited into master branch) some conflicts result. Where did you take 5eb98733

Re: all must do a new clone - new git repository with fixed history

2010/3/26 Francisco Vila : > 2010/3/25 Jan Nieuwenhuizen : >> Hi, >> >> The git repository at savannah has been updated, everyone >> should do a fresh clone. > > I am trying to merge master into lilypond/translation. > From your last commit (which you have commited into master branch) > some confli

Re: all must do a new clone - new git repository with fixed history

Op vrijdag 26-03-2010 om 18:40 uur [tijdzone +0100], schreef Francisco Vila: > 2010/3/26 Francisco Vila : > > 2010/3/25 Jan Nieuwenhuizen : > To be more precise: I've still haven't found any of the new > translation markers which doesn't give "bad object" error. Oops. Hold still, I'll have a loo

Re: half-dot

On 3/26/10 8:43 AM, "David Bobroff" wrote: > On 3/26/2010 1:22 PM, Bertalan Fodor (LilyPondTool) wrote: >> Francisco Vila wrote: >>> >>> 2010/3/26 David Bobroff : >>> >>> >> >> >> My favorite tweak helps here, overriding the stencil with text interface. >

AGAIN: all must do a new clone - new git repository with fixed history

Op vrijdag 26-03-2010 om 20:01 uur [tijdzone +0100], schreef Jan Nieuwenhuizen: > Op vrijdag 26-03-2010 om 18:40 uur [tijdzone +0100], schreef Francisco > Vila: > > 2010/3/26 Francisco Vila : > > > 2010/3/25 Jan Nieuwenhuizen : > > > To be more precise: I've still haven't found any of the new > >

Re: AGAIN: all must do a new clone - new git repository with fixed history

On 2010-03-27, Jan Nieuwenhuizen wrote: > > So, if you already pulled, pull again. All should be fine > now. One further note: also make sure to pull with the `-r' flag: git pull -r If you don't, then you'll see a million warnings fly down the terminal. :-) It's pretty simple to clean up t