-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Pedro,
I've written you this exact mail before but only just today realised why
you did neither respond nor fix the bug.
I was guessing from your name that you're German which I figured is not
the case after seing a message in portugese on your
On March 25, 2005 05:17 am, [EMAIL PROTECTED] wrote:
I had the same problem, try one of
lexer-gcc-3.1.sh (should be in the root of the package)
or
http://lists.gnu.org/archive/html/lilypond-devel/2005-02/msg00015.html
Many thanks for replying. Timing was great as I'd set this aside to
Hello,
I've found some problems in Instrument_name_engraver that make severe
limitations on ChoirStaff (GrandStaff etc.) instrument names.
- \RemoveEmptyStaffContext does not remove instrument name on these staves.
- Lyrics staff gets counted for setting the position of the instrument
name in
I had the same problem, try one of
lexer-gcc-3.1.sh (should be in the root of the package)
or
http://lists.gnu.org/archive/html/lilypond-devel/2005-02/msg00015.html
and the following discussion:
http://lists.gnu.org/archive/html/lilypond-devel/2005-02/msg00057.html
Some versions of Flex generate
INSTALL.txt says Pango is only needed at runtime but I could not make until
I had installed a recent enough version of Pango.
Should a note be added to INSTALL.txt and a check added to configure?
Also I've just noticed that clicking on the Warning next to the download
link for the 2.5 series on
Hello,
I've found some problems in Instrument_name_engraver that make severe
limitations on ChoirStaff (GrandStaff etc.) instrument names.
- \RemoveEmptyStaffContext does not remove instrument name on these staves.
- Lyrics staff gets counted for setting the position of the instrument
name in
Citerar Bertalan Fodor [EMAIL PROTECTED]:
Hello,
I've found some problems in Instrument_name_engraver that make severe
limitations on ChoirStaff (GrandStaff etc.) instrument names.
- \RemoveEmptyStaffContext does not remove instrument name on these staves.
Of course not, since
Mats Bengtsson wrote:
Citerar Bertalan Fodor [EMAIL PROTECTED]:
Hello,
I've found some problems in Instrument_name_engraver that make severe
limitations on ChoirStaff (GrandStaff etc.) instrument names.
- \RemoveEmptyStaffContext does not remove instrument name on these staves.
Of course
On 25-Mar-05, at 12:12 PM, Mats Bengtsson wrote:
Of course not, since \RemoveEmptyStaffContext only redefines what
happens to an ordinary Staff, not to a ChoirStaff or whatever.
The solution is to do the same redefinition of the ChoirStaff as
the \RemoveEmptyStaffContext does to the Staff context.
On 25-Mar-05, at 8:04 AM, Hans Forbrich wrote:
To dev team, esp. Graham - there is an explicit gcc 3.1.1 reference on
the
2.5.16 Installation pages in the section Flex-2.5.4a and gcc-3.x:
Flex 2.5.4a does not produce g++-3.1.1 compliant C++ code. To compile
LilyPond with gcc-3.1.1 you may do
On 24-Mar-05, at 1:47 AM, Mats Bengtsson wrote:
Also, the fact that you cannot have simultaneous slurs is not mentioned
in the documentation.
Whoops. Fixed in CVS.
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
11 matches
Mail list logo