Re: Typo in documentation (3.5 MIDI Output)
On Mon, Jul 09, 2012 at 01:15:27AM +0200, David Kastrup wrote: > Colin Hall writes: > > > On Sun, Jul 08, 2012 at 06:27:04PM +, Micha wrote: > >> In NR 2.14.2 (and 2.15) section 3.5 (MIDI Output) there is a small typo. > >> > >> In the sentence "Standard MIDI oputput is somewhat crude" it should > >> say "output". > > > > Thanks for reporting that problem, Micha. > > > > I've created a new issue tracker: > > > > http://code.google.com/p/lilypond/issues/detail?id=2642 > > > > I see that David Kastrup has already submitted a patch to fix it. > > Actually, the idea was to avoid the red tape for this obvious > two-character change in text-only passage without markup. I guessed as much. > I properly tied all the knots in the red tape now, though. Thanks for doing that. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
"-Eluze" wrote in message news:34131686.p...@talk.nabble.com... Bernard Hurley-2 wrote: On Sun, Jul 08, 2012 at 11:12:40PM +0100, Colin Hall wrote: Hi, I'm a pretty much new user of lilypond and I have an idea for a almost dummy new feature: automatically attach lilypond code in pdf. With pdf files it is possible to attach a file into it. What a great idea! the basic function in LilyPond is given with \include "test.ly" \markup \verbatim-file #"test.ly" now I don't know what you mean with automatically - should it be attached every time? on a new page, in another (pdf) file? or did you mean something else? Eluze I do think this would do what the user wants, if we did not need to put the filename in explicitly. Is there any way of getting the filename into a variable? -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [Feature request] attach lilypond code in pdf.
Le 09/07/2012, Phil Holmes disait : [...] Hi, I'm a pretty much new user of lilypond and I have an idea for a almost dummy new feature: automatically attach lilypond code in pdf. With pdf files it is possible to attach a file into it. What a great idea! the basic function in LilyPond is given with \include "test.ly" \markup \verbatim-file #"test.ly" now I don't know what you mean with automatically - should it be attached every time? on a new page, in another (pdf) file? or did you mean something else? Eluze I do think this would do what the user wants, if we did not need to put the filename in explicitly. Is there any way of getting the filename into a variable? It might be OK when _one_ score means _one_ file. I see a problem when you deal with a full book and, for instance, have 646 files spread in 53 folders. You should then enclose an archive of the tree. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Parenthesizing multi measure rests
%% When using \parenthesize on whole bar or multi measure rests, no
parentheses
%% will be printed:
\version "2.14.2"
\paper { ragged-right=##t }
\parenthesize R1
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
Phil Holmes-2 wrote: > > >> >> the basic function in LilyPond is given with >> >> \include "test.ly" >> \markup \verbatim-file #"test.ly" >> >> now I don't know what you mean with automatically - should it be attached >> every time? on a new page, in another (pdf) file? >> >> or did you mean something else? >> >> Eluze > > > I do think this would do what the user wants, if we did not need to put > the > filename in explicitly. Is there any way of getting the filename into a > variable? > > there is a snippet that derives the filename from the command line: http://lsr.dsi.unimi.it/LSR/Item?id=197 File Information but it doesn't work with 2.15.41 and also for 2.14.2 the filename may not have blanks. Eluze -- View this message in context: http://old.nabble.com/Fwd%3A--Feature-request--attach-lilypond-code-in-pdf.-tp34131613p34133679.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
-Eluze writes: > Phil Holmes-2 wrote: >> >> >>> >>> the basic function in LilyPond is given with >>> >>> \include "test.ly" >>> \markup \verbatim-file #"test.ly" >>> >>> now I don't know what you mean with automatically - should it be attached >>> every time? on a new page, in another (pdf) file? >>> >>> or did you mean something else? >>> >>> Eluze >> >> >> I do think this would do what the user wants, if we did not need to put >> the >> filename in explicitly. Is there any way of getting the filename into a >> variable? >> >> > > there is a snippet that derives the filename from the command line: > http://lsr.dsi.unimi.it/LSR/Item?id=197 File Information but it doesn't > work with 2.15.41 and also for 2.14.2 the filename may not have blanks. What's wrong with using input-file-name ? This should work for the main input file. If you need more than that, you can likely work with something like #(read-hash-extend #\< (lambda (c p) (port-filename p))) #(display #<) This will not work before 2.15.twentyish (when I decided that the terrible error messages for Scheme code were not doing anybody a favor, and made port-filename, port-line, and port-column point to sensible locations). -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
On 2012-07-09 10:49, Phil Holmes wrote: "-Eluze" wrote in message news:34131686.p...@talk.nabble.com... Bernard Hurley-2 wrote: On Sun, Jul 08, 2012 at 11:12:40PM +0100, Colin Hall wrote: Hi, I'm a pretty much new user of lilypond and I have an idea for a almost dummy new feature: automatically attach lilypond code in pdf. With pdf files it is possible to attach a file into it. What a great idea! the basic function in LilyPond is given with \include "test.ly" \markup \verbatim-file #"test.ly" now I don't know what you mean with automatically - should it be attached every time? on a new page, in another (pdf) file? or did you mean something else? I do think this would do what the user wants, if we did not need to put the filename in explicitly. Is there any way of getting the filename into a variable? Actually, I don't think this is what the OP wanted. A pdf file can have other files attached (which are not displayed) and even signed for authenticity. These files are not included as text, but the PDF viewer typically displays a message that other files are attached to the PDF file and can be extracted and stored on disk. Attached is a sample file, created by pdftk (test.pdf is created by lilypond, and the test.ly file is attached to it, and everything is output as test_attached.pdf): pdftk test.pdf attach_files test.ly output test_attached.pdf If you open it in acroread (in okular the file name of the attached file seems messed up), you'll see that the test.ly file is attached to the pdf and can be opened from acroread. You'll probably need to look at the tab with the paper clip to list the attached files. I don't know if ps2pdf supports attaching files to the resulting pdf files, though... Cheers, Reinhold PS: While IMSLP.org does not allow upload of source files directly, it allows/encourages contributors to attach the source files to the output pdf file. -- -- Reinhold Kainhofer,reinh...@kainhofer.com, http://reinhold.kainhofer.com * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org test_attached.pdf Description: Adobe PDF document ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Parenthesizing multi measure rests
2012/7/9 Simon Albrecht :
> %% When using \parenthesize on whole bar or multi measure rests, no
> parentheses
>
> %% will be printed:
>
> \version "2.14.2"
>
> \paper { ragged-right=##t }
>
> \parenthesize R1
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi Simon,
have a look at this thread:
http://old.nabble.com/Whole-measure-rests-in-parentheses-td32197963.html
There are two workarounds posted.
HTH,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
Reinhold Kainhofer writes: > If you open it in No need for that, evince shows the attachment fine. It would be nice if we could do this directly through GhostScript or a PostScript command. Jan -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
David Kastrup wrote: > > > > What's wrong with using input-file-name ? This should work for the main > input file. If you need more than that, you can likely work with > something like > > #(read-hash-extend #\< (lambda (c p) (port-filename p))) > > #(display #<) > > This will not work before 2.15.twentyish (when I decided that the > terrible error messages for Scheme code were not doing anybody a favor, > and made port-filename, port-line, and port-column point to sensible > locations). > > this only lacks to be mentioned somewhere in the docs! great! - are there other such undocumented variables? Eluze -- View this message in context: http://old.nabble.com/Fwd%3A--Feature-request--attach-lilypond-code-in-pdf.-tp34131613p34134198.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
-Eluze writes: > David Kastrup wrote: >> >> >> >> What's wrong with using input-file-name ? This should work for the main >> input file. If you need more than that, you can likely work with >> something like >> >> #(read-hash-extend #\< (lambda (c p) (port-filename p))) >> >> #(display #<) >> >> This will not work before 2.15.twentyish (when I decided that the >> terrible error messages for Scheme code were not doing anybody a favor, >> and made port-filename, port-line, and port-column point to sensible >> locations). >> >> > > this only lacks to be mentioned somewhere in the docs! > > great! - are there other such undocumented variables? The elements of the read-hash-extend thing are all explained in the Guile manual and just "work as expected" (notwithstanding that this has not always been the case). Using a reader extension seems awkward, but most other stuff is executed at a time when the port is no longer available. Of course, pretty much every music expression (and the resulting stream event) has an 'origin property which you can call ly:input-file-line-char-column or ly:input_both_locations on (both are documented), and every music, scheme or event function has a location parameter carrying the same information. So it is not like one would be all that dependent on getting this info from the Scheme reader. It is not like it would be really hidden. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: inconsistency in documentation for baseMoment (patch proposed)
> Not sure about translations. But if it is "one over the denominator" in > English, you should _write_ "one over the denominator" rather than "the > one over denominator". > http://code.google.com/p/lilypond/issues/detail?id=2644 new patch added to the tracker. Frédéric ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: [Feature request] attach lilypond code in pdf.
On Mon, Jul 9, 2012 at 2:31 PM, Reinhold Kainhofer wrote: > > "-Eluze" wrote in message >> >> On Sun, Jul 8, 2012 at 8:27 PM, Da Mota Sam wrote: >>> I'm a pretty much new user of lilypond and I have an idea for a almost >>> dummy new feature: automatically attach lilypond code in pdf. >>> With pdf files it is possible to attach a file into it. >> >> the basic function in LilyPond is given with >> >> \include "test.ly" >> \markup \verbatim-file #"test.ly" > > Actually, I don't think this is what the OP wanted. Definitely! I'm sure that Samuel meant attaching .ly files to pdf files (like attachments in email), not quoting the source code in markup. I agree that this would be a very useful feature. My source files change even *after* the score was already "published", and sometimes i have trouble when i want to recompile and get the old version. Putting them under version control would help, but i don't think it would solve all the problems. Attaching sources to pdfs gives a really nice way to store music. I prefer to keep finished pdfs separately - for greater clarity, easy searching, easy sharing (my friends wouldn't know what to do with all these source files) and because i also have finale-made pdfs to mix with Lily-made ones. The downsides are that i may not have the sources when i need them or that the pdf doesn't match the source anymore - both of these would be solved by having appropriate .ly files attached to the score. They don't take much space and don't get in the way - really cool! cheers, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doc enhancement for \headers
On Mon, Jul 09, 2012 at 01:09:50AM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > On Thu, Jul 05, 2012 at 11:16:52AM -0700, -Eluze wrote:
> > It _is_ attacked from another starting point -- by explaining as
> > much as possible with working examples.
>
> If I have twenty relevant variables, I don't want to look for 200 lines
> of prose for finding the right one to use, and not through 400 lines of
> examples. I am more interested in 20 one-liners. And possibly a single
> example where each field is set to its own name, so you can look at the
> output and immediately see what goes where. Non-textual fields are
> somewhat more problematic. Take a look at the second page in
> ftp://ftp.fu-berlin.de/tex/CTAN/macros/latex/required/tools/layout.pdf>.
> Yes, definitely more effort than writing twenty paragraphs of text.
... I'm not certain what you mean by this. Are you agreeing or
disagreeing with my claim that working examples are easy to
maintain and easy to read?
IMO the second page in that link is an example of great
documentation. You can clearly see the variables, how the effect
the page creation [1], etc. Granted, by asking for a full working
example, I'm suggesting that we have a bit of "boilerplate" code
in there as well, so it wouldn't be _quite_ as clear as the latex
example. But anybody looking up such details in Notation
shouldn't be confused by the order of \score{} and \paper{}, and
IMO the ease of maintaining a full working example in the docs
makes that trade-off well worth it.
[1] http://xkcd.com/326/
> > But what's one "language" that we all speak? Regardless of our
> > country, any programming mind-set, etc? well, "lilypond", of
> > course.
>
> You can bore and confuse in every language including "LilyPond".
Sure. But we're all fluent in "ly", and there's now pretty good
understanding of the term "Tiny examples", so I expect that it's
much easier to create high-quality "ly" explanations than
high-quality "english" explanations.
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Parenthesizing multi measure rests
On Mon, Jul 09, 2012 at 02:46:28PM +0200, Thomas Morley wrote:
> 2012/7/9 Simon Albrecht :
> > %% When using \parenthesize on whole bar or multi measure rests, no
> > parentheses
> >
> > %% will be printed:
> >
> > \version "2.14.2"
> >
> > \paper { ragged-right=##t }
> >
> > \parenthesize R1
Thanks for the bug report, Simon.
It appears there are workarounds (thanks, Thomas), and there is an
existing tracker which may be the same problem (1523) but I decided to
create a new tracker and refer to everything from there.
See this tracker for your report, links to the workarounds reported by
Thomas, and a link to that older issue tracker, 1523, which may be
related.
http://code.google.com/p/lilypond/issues/detail?id=2646
Cheers,
Colin.
--
Colin Hall
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Repeat Dots and Staff Size in 2.15.41
My first reply, identifying this bug as a regression ... - Original Message - From: "Trevor Daniels" To: "David Stocker" ; Sent: Sunday, July 08, 2012 12:48 PM Subject: Re: Repeat Dots and Staff Size in 2.15.41 > Damn! Another regression. (Sorry, David, I'm not > swearing at you - in fact, many thanks to you for picking > this up.) > > This one first appeared in 2.15.40. 2.15.39 is OK. > > Trevor > > - Original Message - > From: "David Stocker" > To: > Sent: Sunday, July 08, 2012 12:31 PM > Subject: Repeat Dots and Staff Size in 2.15.41 > > >> I've discovered a strange behavior in 2.15.41 when I alter the size of the >> staff space in the \layout block. >> >> I've played around with the different settings and overrides I have in the >> layout block and the layout-set-staff-size and StaffSymbol #'thickness >> settings seem to be blameless. StaffSymbol #'staff-space is definitely the >> culprit. >> >> The behavior doesn't occur when I compile the same score with 2.14 >> >> Have a look at the attached files. >> >> Thanks, >> >> David >> > > > > > >> ___ >> lilypond-user mailing list >> lilypond-u...@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-user >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Fw: Repeat Dots and Staff Size in 2.15.41
My second reply, identifying a possible source of the bug. Trevor - Original Message - From: "Trevor Daniels" To: "Trevor Daniels" ; "David Stocker" ; Sent: Sunday, July 08, 2012 12:52 PM Subject: Re: Repeat Dots and Staff Size in 2.15.41 > > Trevor Daniels wrote Sunday, July 08, 2012 12:48 PM > > >> Damn! Another regression. (Sorry, David, I'm not >> swearing at you - in fact, many thanks to you for picking >> this up.) >> >> This one first appeared in 2.15.40. 2.15.39 is OK. > > This is worth checking: > >line_count fixes > >1. implementation does not assume staff centered at zero >2. where used for determining whether something falls on a line, > use Staff_symbol_referencer::on_line or on_staff_line >3. where used for determining whether something is within staff or not, > use Staff_symbol_referencer::staff_span > > 2a872121379fffe7b1cd5d23048b7ea04b4d1f68 > > Trevor > ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LM: 1.4.2 Clickable examples
On Tue, Jul 10, 2012 at 12:13:46AM +0200, Federico Bruni wrote: > Hi, > > I remember that I used to click an example in the doc and see the > text file in the browser window. Now I'm prompted with a window > which asks me which application I should use. Thanks for the report, Federico. I agree with your description of browser behaviour when clicking on images of music in the docs. I'm not sure what the doc authors intend to happen, so I hope that the first step in resolving this bug is to confirm the design intent for clicking on music images. All you have requested is a change to the documentation, which seems reasonable, so I have created a new tracker for this report. http://code.google.com/p/lilypond/issues/detail?id=2647 Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fw: Repeat Dots and Staff Size in 2.15.41
On Mon, Jul 09, 2012 at 11:47:46PM +0100, Trevor Daniels wrote: > It seems like my attempts to forward this and my replies to the bug > list failed to get through, so here they are again. Thanks for fowarding the report, Trevor. > > Here's the original bug report: > > - Original Message - > From: "David Stocker" > To: > Sent: Sunday, July 08, 2012 12:31 PM > Subject: Repeat Dots and Staff Size in 2.15.41 > > > > I've discovered a strange behavior in 2.15.41 when I alter the size of the > > staff space in the \layout block. > > > > I've played around with the different settings and overrides I have in the > > layout block and the layout-set-staff-size and StaffSymbol #'thickness > > settings seem to be blameless. StaffSymbol #'staff-space is definitely the > > culprit. > > > > The behavior doesn't occur when I compile the same score with 2.14 > > > > Have a look at the attached files. I've created a tracker for this here http://code.google.com/p/lilypond/issues/detail?id=2648 Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
