Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On Sun 03 Oct 2010, 14:52 Graham Percival wrote: On Sun, Oct 03, 2010 at 02:37:59PM +0100, James Lowe wrote: 1. Open Email 2. Read Email. Spot problem. Reply Yes. mutt! all-in-one, whether example is attached or inline =O] ((2Graham: i know you know,)) If someone sends an ly file that is umpty-thrumpty lines long let's add one more point: 2b. if you can't spot the problem, point them at http://lilypond.org/tiny-examples.html This is rather for bug-lilypond, i'd say. In lilypond-user it is customary to send larger samples *and* deal with other's larger samples. It's good. Why not. So, if someone sends an ly file that is umpty-thrumpty lines long -- let it be attached, of course. -- Dmytro O. Redchuk Bug Squad Be careful! These are some commonly used abbreviations: • LM -- Learning Manual • NR -- Notation Reference • IR -- Internal Reference Look at LilyPond’s documentation to find more. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On Sun, Oct 3, 2010 at 8:49 PM, Carl Sorensen c_soren...@byu.edu wrote: I greatly prefer having short snippets inline. That way I can read them in my mail reader, rather than having to open them to see what's up. Ditto. If I ever want to compile one, I have a dedicated ~/toto.ly file that I only use for pasting code excerpts :-) Long files are better as attachments than inline. It's possible, but then there's a good chance most readers won't go through the hassle of downloading/saving/compiling/deleting the file (as pointed out by James; BTW he missed the part where your home directory is clobbered with random .ly files and you have to remember which ones are important and which ones you may delete). Cheers, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On Mon, Oct 04, 2010 at 09:21:49AM +0300, Dmytro O. Redchuk wrote: On Sun 03 Oct 2010, 14:52 Graham Percival wrote: 2b. if you can't spot the problem, point them at http://lilypond.org/tiny-examples.html This is rather for bug-lilypond, i'd say. In lilypond-user it is customary to send larger samples *and* deal with other's larger samples. That's a problem that will hopefully change, now that Tiny-examples are much more obvious on the website. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On Sun, 3 Oct 2010, Phil Holmes wrote: There were a couple of errors in the snippet you posted - the version number should be in inverted commas , and you have arpeggi which I assume should be arpeggio. I personally would prefer it if lilypond snippets and example code in this mailinglist were posted as separate attachement(s) to the mail. I then just simply can save the snippet to disk. Now I first have to copy and paste the lilypond code in my text editor, and save it from there before running lilypond on it. What do other lilypond mailinglist readers think ? If many people agree, we could encourage people to follow this practice. -- Martin Tarenskeen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On 3 October 2010 14:36, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: I personally would prefer it if lilypond snippets and example code in this mailinglist were posted as separate attachement(s) to the mail. I then just simply can save the snippet to disk. Now I first have to copy and paste the lilypond code in my text editor, and save it from there before running lilypond on it. What do other lilypond mailinglist readers think ? If many people agree, we could encourage people to follow this practice. I depends. When this is a whole lilypond file I prefer it as separate attachement. But for minimal examples, i.e. code including only 2-3 measures showing an issue, I prefer it included directly in the mail. I think my reasoning is somewhat similar to the difference between @lilypond and @lilypondfile we can see in LilyPond .itely doc. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
Hello, On 03/10/2010 13:36, Martin Tarenskeen wrote: On Sun, 3 Oct 2010, Phil Holmes wrote: There were a couple of errors in the snippet you posted - the version number should be in inverted commas , and you have arpeggi which I assume should be arpeggio. I personally would prefer it if lilypond snippets and example code in this mailinglist were posted as separate attachement(s) to the mail. I then just simply can save the snippet to disk. Now I first have to copy and paste the lilypond code in my text editor, and save it from there before running lilypond on it. What do other lilypond mailinglist readers think ? If many people agree, we could encourage people to follow this practice. 1. Open Email 2. Read Email 3. Download attachment 4. Find/open attachment 5. Read in text editor. Spot Problem 6. Back to email to reply as opposed to 1. Open Email 2. Read Email. Spot problem. Reply If someone sends an ly file that is umpty-thrumpty lines long they do tend to attach them - generally. Which leads to the point where I follow my 6 steps above realise the example is simply too big for me to help with a trivial issue but I only realise that after I have downloaded the attachment. I understand what you are getting at, but I am guessing if it is anything but trivial to see what users are asking for help on this list are then as many won't (probably) bother to download that attachment to help. I'm not so sure this is a good idea. James ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On Sun, Oct 03, 2010 at 02:37:59PM +0100, James Lowe wrote: 1. Open Email 2. Read Email. Spot problem. Reply Yes. If someone sends an ly file that is umpty-thrumpty lines long let's add one more point: 2b. if you can't spot the problem, point them at http://lilypond.org/tiny-examples.html Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Snippets in mailinglist (Was: Re: bad cross-staff slurs)
On 10/3/10 6:36 AM, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: On Sun, 3 Oct 2010, Phil Holmes wrote: There were a couple of errors in the snippet you posted - the version number should be in inverted commas , and you have arpeggi which I assume should be arpeggio. I personally would prefer it if lilypond snippets and example code in this mailinglist were posted as separate attachement(s) to the mail. I then just simply can save the snippet to disk. Now I first have to copy and paste the lilypond code in my text editor, and save it from there before running lilypond on it. I greatly prefer having short snippets inline. That way I can read them in my mail reader, rather than having to open them to see what's up. Long files are better as attachments than inline. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
