Edward Ardzinski writes:
> As for snippets - so far I've added a generic variable, generic drum
> high/low variable, the code to set a midi instrument, a drum staff, and a
> comment break (just a percent sign followed by a bunch of asterisks). As I
> have been working on an old tune of mine I al
On 2013-11-02 11:54, David Kastrup wrote:
> Hm, I like this idea of turning a mailing list into an entirely optional
> social networking medium by adding more of a feedback/scoring criterion
> than "Report Spam".
So the mailing-list continues to function as-is, with a separate system
for maintaini
David Kastrup wrote
> Uh, we do have a manual that can be edited, improved, and evolve over time
> with different versions of LilyPond...
Right, but formal documentation is not the same as more informal
Q&A/support, and they have different levels of editing
accessibility/difficulty and quality exp
Paul Morris writes:
> janek.lilypond wrote
>> Q&A sites like StackExchange are better for sharing Q&A knowledge than
>> mailing lists because they allow to edit information, update it,
>> remove duplicates, and make order.
>
> I think this is a good point. The mailing list is sufficient and fi
janek.lilypond wrote
> Q&A sites like StackExchange are better for sharing Q&A knowledge than
> mailing lists because they allow to edit information, update it,
> remove duplicates, and make order.
I think this is a good point. The mailing list is sufficient and fine, but
it's probably not opti
Hilary Snaden writes:
> On 2013-11-02 05:52, David Kastrup wrote:
>> Gilberto Agostinho writes:
>>
>>> I am also totally up for this idea as well.
>>
>> What's wrong with this list? Everybody wants to take his LilyPond
>> business to the web interface of his choice that takes a lot of
>> addi
I think there is one thing the mailing list can't really offer compared to a
Q&A site: accepted answers. This is really a good thing. But definitely no
reason to spread our forceds and competence.
Ther already _are_ places to present solutions, although not as answersx to
posted questions: the L
On 2013-11-02 05:52, David Kastrup wrote:
> Gilberto Agostinho writes:
>
>> I am also totally up for this idea as well.
>
> What's wrong with this list? Everybody wants to take his LilyPond
> business to the web interface of his choice that takes a lot of
> additional work over just reading and
Hmm, after reading all arguments against a Stack Exchange page, I have to
say I completely changed my opinion on this regards as well. Indeed it would
not be good for us to spread a small community in two places, and re-posting
questions on both would be a waste of time indeed. My first reaction o
Janek Warchoł writes:
> "when all you have is a hammer, every problem starts looking like a
> nail". Mailing lists are an all-purpose communication tool. Many
> things can be done using a mailing list, but some things may be done
> more efficiently using other tools - for example, most of us th
Hi,
my 3 eurocents:
1) StackExchange is great. It's Q&A style of sharing knowledge is
very efficient and pleasure to work with.
2) LilyPond is too small to have its own StackExcange site. If you look at
http://discuss.area51.stackexchange.com/questions/10733/leaving-beta-requirements
you'll se
> Maybe it is even better to send them directly to the posting!?
> http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general
Probably. I don't use gmane at all, so I can't give a
recommendation. However, as with StackExchange, people should
*search* first before post something whethe
Peter Bjuhr writes:
> On 11/02/2013 11:16 AM, Werner LEMBERG wrote:
>> It depends. For casual users, the gmane interface is perhaps better
>> suited, thus the link should rather be
>> http://news.gmane.org/gmane.comp.gnu.lilypond.general
>
> Maybe it is even better to send them directly to the p
On 11/02/2013 11:16 AM, Werner LEMBERG wrote:
It depends. For casual users, the gmane interface is perhaps better
suited, thus the link should rather be
http://news.gmane.org/gmane.comp.gnu.lilypond.general
Maybe it is even better to send them directly to the posting!?
http://post.gmane.org
> Then I suppose I should also post that answer to the meta question I
> linked to previously!?
I think this would be good, yes.
> So, is this the link to give?
> https://lists.gnu.org/mailman/listinfo/lilypond-user
It depends. For casual users, the gmane interface is perhaps better
suited, th
Werner LEMBERG writes:
>> If it's community policy or at least a general agreement that we
>> should always refer to this list, I will of course do so the next
>> time!
>
> Yes, please do so.
>
>> But I hope we agree that it, as Ryan wrote, would be helpful for the
>> community if we found ways t
On 11/02/2013 10:28 AM, Werner LEMBERG wrote:
If it's community policy or at least a general agreement that we
should always refer to this list, I will of course do so the next
time!
Yes, please do so.
No problem! Then I suppose I should also post that answer to the meta
question I linked to
> If it's community policy or at least a general agreement that we
> should always refer to this list, I will of course do so the next
> time!
Yes, please do so.
> But I hope we agree that it, as Ryan wrote, would be helpful for the
> community if we found ways to deal with questions posted outs
On 11/02/2013 08:28 AM, David Kastrup wrote:
Well, they are on-topic in this mailing list.
If it's community policy or at least a general agreement that we should
always refer to this list, I will of course do so the next time!
But I hope we agree that it, as Ryan wrote, would be helpful fo
ryanmichaelmcclure writes:
> Allow me to clarify that in no way did I intend for the Stack Exchange
> page to replace this list. It would have been purely an addition of
> resources.
>
> For me, the purpose of the Stack Exchange page is about accessibility
> to those who are 1) not familiar with
> Allow me to clarify that in no way did I intend for the Stack
> Exchange page to replace this list. It would have been purely an
> addition of resources.
Well, you might answer all lilypond questions by simply pointing
questioners to the list :)
> For me, the purpose of the Stack Exchange pag
Peter Bjuhr writes:
> I agree with Urs that a Stack Exchange page shouldn't be instead of
> this list, if that was the suggestion.
>
> But as Gilberto pointed out there is already LilyPond questions asked
> on different Stack Exchange forums (I answered one myself earlier this
> week). And it see
Allow me to clarify that in no way did I intend for the Stack Exchange page
to replace this list. It would have been purely an addition of resources.
For me, the purpose of the Stack Exchange page is about accessibility to
those who are 1) not familiar with LilyPond or 2) not familiar with mailing
I agree with Urs that a Stack Exchange page shouldn't be instead of this
list, if that was the suggestion.
But as Gilberto pointed out there is already LilyPond questions asked on
different Stack Exchange forums (I answered one myself earlier this
week). And it seems to be some confusion about
>> I am also totally up for this idea as well.
>
> What's wrong with this list? Everybody wants to take his LilyPond
> business to the web interface of his choice that takes a lot of
> additional work over just reading and typing text and further
> dilutes the LilyPond knowledge.
I second that.
I'm somewhat split in this question:
I very much like stackexchange and use it as a resource for latex, git and
python questions regularly.
Finding answers to Lilypond questions there would be nice too.
But I think the user base of Lilypond is significantly smaller than of the
other mentiones t
Gilberto Agostinho writes:
> I am also totally up for this idea as well.
What's wrong with this list? Everybody wants to take his LilyPond
business to the web interface of his choice that takes a lot of
additional work over just reading and typing text and further dilutes
the LilyPond knowledge
I am also totally up for this idea as well. I have been posting some
questions and answers related to LilyPond programming on the Stack Overflow
website, but unfortunately there are too few people dealing with LilyPond
over there. Stack Exchange also has a website called Musical Practice &
Performa
It seems like a good many people support the idea. Thanks Noeck for that
link--it seems like many supported it back then. It doesn't seem like too
much work to create a page. I have created a proposal for it:
http://area51.stackexchange.com/proposals/61575/lilypond
I have also created a generic s
I am very much in favour of it, see this post from *exactly* one year ago:
https://lists.gnu.org/archive/html/lilypond-user/2012-11/msg00018.html
Cheers,
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/l
I know that AskUbuntu is WONDERFUL--it is the webpage that helped me breech
the gap between being a newbie to a confident user in Ubuntu. A LilyPond
page would be tremendous not only to new users but also for archiving
information. Yes, the mailing list is excellent, but for someone who is
absolute
Hello Ryan:
On Fri, 2013-11-01 at 16:30 -0700, ryanmichaelmcclure wrote:
> What are your thoughts about creating a LilyPond Stack
> Exchange page?
I have found the LaTex Stack Exchange very useful. I think that
LilyPond would definitely benefit from a Stack Exchange-type website.
I don't mean
On Mon, 07 Sep 2009 11:15:21 +1000
Peter Chubb wrote:
> > "Grammostola" == Grammostola Rosea writes:
>
> Grammostola> David Raleigh Arnold wrote:
> >>>
> >> Again, why not get in touch with the developer(s) of midge? The
> >> syntax is completely different, but it is *text-based* and GNU.
For example, you can define your own music function that has a single
numerical argument (for example to modify some spacing parameters).
The syntax for such a function would be exacty of the form \myvar 1.
/Mats
[EMAIL PROTECTED] wrote:
I would expect that
\myvar1 refers to the variable
> I would expect that
>\myvar1 refers to the variable myvar1
>\myvar 1 refers to the var myvar followed by 1
As regards the expression
\myvar 1
in what context do you use that?
-- Tom
Andrew Black wrote:
I would r
Han-Wen Nienhuys wrote:
c4_\staccato_\markup { bla }
does this reference \staccato or \staccato_ ?
It might be possible to enable numbers, though. I would welcome an analysis.
I would really like to see numbers in name of variables.
I am not expert on parsers so apologies if this is hard
As regards allowing numbers in identifier-names:
> It might be possible to enable numbers, though. I would welcome an
> analysis.
For lyrics, I rely on the fact that identifier-names cannot contain
numbers:
I = \markup { C }
Vs = \markup { G7 }
and later, in lyricmode, things like
Am 28. Dezember 2006, 17:59 Uhr (+0100) schrieb Han-Wen Nienhuys:
>
> numbers and underscores do make things easier to read, but it makes things
> hard to parse. Consider:
>
> c4_\staccato_\markup { bla }
>
> does this reference \staccato or \staccato_ ?
Underscores make most sense in the mid
Orm Finnendahl escreveu:
> P.S.: Maybe one thing: Apart from suggesting to rewrite lilyponds
> parser from scratch it would be a tremendous thing if lilypond could
> get rid of some TeX related restrictions, especially the limitation to
> alphabetic characters in definitions. It would make things s
Orm Finnendahl wrote:
>
> Hi,
>
> I just wanted to add to my recent comments. It might seem that my
> posts are unadequately critical. Although they are fueled by my
> frustration using the program I want to make clear that I really
> appreciate the tremendous and excellent work which has bee
40 matches
Mail list logo
