> > I'm not sure whether this has been discussed before: What do you
> > think of using `c[]' as a shorthand for `\autoBeamOff c
> > \autoBeamOn'?
>
> When I was first learning lilypond I remember trying this exact
> syntax to get an unbeamed note. I think it would be useful if it
> worked. It's a
Mats Bengtsson ee.kth.se> writes:
>
> We already have the predefined macro \noBeam. Do we really need yet another
> more or less obscure special case of the syntax?
>
> /Mats
>
> Werner LEMBERG wrote:
> > I'm not sure whether this has been discussed before: What do you think
> > of using `c
> > 1. I'm replacing hara-kiri with axis-group; however, whatever I
> >do, there is no (empty) lyrics line in the first system.
>
> This appears to be the same issue affecting the piano centred
> dynamics template when there's a system with no dynamics.
Ok. Is this classified as a bug or as
Hi,
On Thu, 4 Sep 2008, Till Rettig wrote:
> Johannes Schindelin schrieb:
> > You mean "git reset --hard"? That resets _all_ files. _And_ the
> > staging area.
>
> Guess I meant that one -- I had sometimes problems with wrong commits
> that I didn't get reset somehow. As I understand, if I do
Johannes Schindelin schrieb:
Hi,
On Thu, 4 Sep 2008, till Rettig wrote:
- -) "git checkout filename" -- discards all non-committed changes to the
file.
I thought that works only if you remove the file before?
No, it works also with dirty files, i.e. files that have been mo
> We already have the predefined macro \noBeam.
Ah, I wasn't aware of that! I overlooked it in the docs.
> Do we really need yet another more or less obscure special case of
> the syntax?
No.
Werner
___
lilypond-devel mailing list
lilypond-dev
Hi Werner,
2008/9/2 Werner LEMBERG <[EMAIL PROTECTED]>:
> 1. I'm replacing hara-kiri with axis-group; however, whatever I do,
> there is no (empty) lyrics line in the first system.
This appears to be the same issue affecting the piano centred dynamics
template when there's a system with no
On 2008/09/04 01:16 -0700, Patrick McCarty wrote:
> On Thu, Sep 04, 2008 at 12:38:08AM -0700, Patrick McCarty wrote:
> > Regardless, it's clear that my problem was due to an upstream change.
Yep, I should have suspected this :-P
> Well, it seems this is a pretty easy fix. It's a simple search an
Hi,
On Thu, 4 Sep 2008, till Rettig wrote:
> > - -) "git checkout filename" -- discards all non-committed changes to the
> > file.
>
> I thought that works only if you remove the file before?
No, it works also with dirty files, i.e. files that have been modified,
but not committed.
The only
We already have the predefined macro \noBeam. Do we really need yet another
more or less obscure special case of the syntax?
/Mats
Werner LEMBERG wrote:
I'm not sure whether this has been discussed before: What do you think
of using `c[]' as a shorthand for `\autoBeamOff c \autoBeamOn'?
Cur
I'm not sure whether this has been discussed before: What do you think
of using `c[]' as a shorthand for `\autoBeamOff c \autoBeamOn'?
Currently, `c[]' produces
_
|
|
O
(a note with a beamlet to the left and right), which is neither
document
On Thu, Sep 04, 2008 at 12:38:08AM -0700, Patrick McCarty wrote:
>
> Since an example with CSS_LINES is described, and this variable is
> used in the init file, I figured this might be relevant.
>
> Regardless, it's clear that my problem was due to an upstream change.
Well, it seems this is a pr
Just to add a couple of points to this which may be helpful to
some.
Creating new branches is easy and does not have a high overhead.
I usually have several on the go, one for each self-contained change
or set of changes currently under development. This permits several
commits to be under devel
Hi John,
On Wed, Sep 03, 2008 at 11:31:58PM +0200, John Mandereau wrote:
>
> Strange... There is in all HTML pages generated by
> texi2html in my build. Does anything look strange in "make web" output?
> You can do
>
> find -wholename '*out-www/*.html' -delete
> make out=www WWW-2 &>log
>
> a
14 matches
Mail list logo
