Bertalan Fodor wrote:
Well, we have a webpage about at least one quite good editor:
http://lilypondtool.organum.hu ;-)
So spend 30 minutes and create a general editor webpage for lilypond.
If you omit emacs or vim you'll probably have a riot, but you only need
one paragraph about each. Then
Well, we have a webpage about at least one quite good editor:
http://lilypondtool.organum.hu ;-)
Graham Percival írta:
Bertalan Fodor wrote:
I don't think it should be in the manual at all; I'd prefer this
info to be on the webpages.
Ok, but the link to the webpage about editors should be a
Bertalan Fodor wrote:
I don't think it should be in the manual at all; I'd prefer this info
to be on the webpages.
Ok, but the link to the webpage about editors should be at an emphasized
place in the doc.
We don't _have_ a webpage about editors. At least, not that I'm aware of.
Cheers,
-
I don't think it should be in the manual at all; I'd prefer this info
to be on the webpages.
Ok, but the link to the webpage about editors should be at an emphasized
place in the doc.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
htt
Mats Bengtsson wrote:
Some more information that might be worth adding already in the tutorial
(again specifically for Windows):
Thanks, I did all these updates.
Finally, it's probably a good idea to add a footnote with a link to some
overview
of different text editors, since the one supplied
Bertalan Fodor wrote:
Finally, it's probably a good idea to add a footnote with a link to
some overview
of different text editors, since the one supplied with LilyPond on
Windows and
probably also on Mac is fairly rudimentary. This should replace the
current
footnote 1.
I don't think it shou
Joe Neeman escreveu:
> On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> + if (chunks.size () != div.size () + 1)
>> +{
>> + programming_error ("did not find a valid page breaking
>> configuration");
>> + ignore_div = true;
>> + assert (0);
>>
>>
>> this is better, but
Finally, it's probably a good idea to add a footnote with a link to
some overview
of different text editors, since the one supplied with LilyPond on
Windows and
probably also on Mac is fairly rudimentary. This should replace the
current
footnote 1.
I don't think it should be a footnote. Using
Graham Percival wrote:
Mats Bengtsson wrote:
- The instructions for Windows need some polishing. Basically,
you could more or less the same as on Mac, namely double-click
the LilyPond icon on the desktop to start a simple text editor.
I can come back with more details when I have a Windows
Joe Neeman escreveu:
> On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> Joe Neeman escreveu:
>> > On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> >> + if (chunks.size () != div.size () + 1)
>> >> +{
>> >> + programming_error ("did not find a valid page breaking
>> >>
On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Joe Neeman escreveu:
> On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> + if (chunks.size () != div.size () + 1)
>> +{
>> + programming_error ("did not find a valid page breaking
>> configuration");
>> + ignore_div =
Joe Neeman escreveu:
> On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> + if (chunks.size () != div.size () + 1)
>> +{
>> + programming_error ("did not find a valid page breaking
>> configuration");
>> + ignore_div = true;
>> + assert (0);
>>
>>
>> this is better, but
Joe Neeman escreveu:
> On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> + if (chunks.size () != div.size () + 1)
>> +{
>> + programming_error ("did not find a valid page breaking
>> configuration");
>> + ignore_div = true;
>> + assert (0);
>>
>>
>> this is better, but
On 1/24/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
+ if (chunks.size () != div.size () + 1)
+{
+ programming_error ("did not find a valid page breaking
configuration");
+ ignore_div = true;
+ assert (0);
this is better, but can we skip the assert()?
If this assert fai
One general note about these categories:
The LSR is still perfectly usable on its own. You can search for words
(ie "articulation" or "scheme" or "lyrics"). If you _want_, you could
filter the search by these categories... but the main point of the
categories is for the semi-automatic import
Graham Percival escreveu:
> Han-Wen Nienhuys wrote:
>>
>> Why do you use exclusive categories? Isn't it better to devise some
>> sort of tagging scheme, eg.
>
> I'm reluctant to propose something unless I can do it myself (or if it's
> a clear feature request). And I don't want to put LSR on hol
Mats Bengtsson wrote:
Why is scheme programming so special? If I, as an ordinary user, want to
solve
a certain typesetting problem, I mostly don't have any idea if the
solution requires
Scheme programming or not and at least as long as the solution can be
copy/pasted
into my own file as it is,
Han-Wen Nienhuys wrote:
Why do you use exclusive categories? Isn't it better to devise some
sort of tagging scheme, eg.
I'm reluctant to propose something unless I can do it myself (or if it's
a clear feature request). And I don't want to put LSR on hold for
another year while we wait for
Graham Percival wrote:
Agree! Often such division into different categories don't help at
all, they just give you more places to search from.
Other than one example (scheme programming), I have no objection to
this -- but please don't say "text, lyrics, articulation etc". I'd
like to dis
Alard de Boer wrote:
The tutorial is great! Some minor comments:
2.1.1 second footnote: These easiest -> The easiest
2.1.1 Section MacOS X, 2nd par: lilypond -> LilyPond (all other uses
except the Unix command line have the two capital letters)
2.3.1 3rd paragraph: means that are -> means that
+ if (chunks.size () != div.size () + 1)
+{
+ programming_error ("did not find a valid page breaking configuration");
+ ignore_div = true;
+ assert (0);
this is better, but can we skip the assert()?
The problem with assert is that it prevents people from getting a PDF
and loo
Han-Wen Nienhuys escreveu:
> - produce a page per tag: a page for all lyrics examples, a page for
>all piano stuff etc.
>
>This is a bit unnatural, though, so it would be better if we could
>find some lightweight method to dynamically generate those
>pages. It be possible with jav
Graham Percival escreveu:
>> Agree! Often such division into different categories don't help at
>> all, they just give you more places to search from.
>
> Other than one example (scheme programming), I have no objection to this
> -- but please don't say "text, lyrics, articulation etc". I'd like
On 23/01/07, Graham Percival <[EMAIL PROTECTED]> wrote:
The rewritten tutorial is online,
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Tutorial
Could a few people proofread it? In the near future the translation
teams will be working on it, so it would be good if we finalized node
Mats Bengtsson wrote:
Bertalan Fodor wrote:
I feel that these categories are not leading the mind. Users usually
wants to make a graphical representation of some music, and not doing
scheme, or trick, or whatever.
For example, many tweaks are ''simple'' ''scheme-trick''s, that
(naturally) inv
On 24/01/07, Ted Walther <[EMAIL PROTECTED]> wrote:
Thank you, that worked very nicely. Results here:
http://hymns.reactor-core.org/SacredHarp/Pilgrim.pdf
(forwarded from the user-list)
I opened this file (just to see what Sacred Harp music looks
like :) and noticed that the point-and-click
Bertalan Fodor wrote:
I feel that these categories are not leading the mind. Users usually
wants to make a graphical representation of some music, and not doing
scheme, or trick, or whatever.
For example, many tweaks are ''simple'' ''scheme-trick''s, that
(naturally) involves some ''scheme-pr
I feel that these categories are not leading the mind. Users usually
wants to make a graphical representation of some music, and not doing
scheme, or trick, or whatever.
For example, many tweaks are ''simple'' ''scheme-trick''s, that
(naturally) involves some ''scheme-programming''... I'd better
could LSR tweaks be accessible from the corresponding chapter in the user
documentation ?
On the part concerning dynamics, at the end one could put a link to the most
significant tricks concerning dynamics etc.
About your classification I would have chosen a thematic based one. When I
use LSR, I
Could somebody check why this doesn't compile in 2.11.13 ? It's the
first example of "Lyrics to multiple notes of a melisma"
I'm suspicious about the multiple lyrics to the same context, but as far
as I can see, nobody's changed this example in a while.
<<
\relative \new Voice = "lahlah" {
30 matches
Mail list logo
