Re: Doc-string with newline character
Am Do., 31. Dez. 2020 um 00:00 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mi., 30. Dez. 2020 um 10:37 Uhr schrieb Jonas Hahnfeld
> > :
> >>
> >> Hi,
> >>
> >> Am Mittwoch, dem 30.12.2020 um 10:31 +0100 schrieb Thomas Morley:
> >> > Hi,
> >> >
> >> > while preparing a patch a noticed a problem with a doc-string:
> >> > I want to refer to newline characters and wrote "@code{#\newline}",
> >> > but it comes out as
> >> > # ewline
> >> > for both pdf and html.
> >> > I couldn't figure how to let print
> >> > #\newline
> >> >
> >> > Any hint?
> >>
> >> I didn't try, but I could imagine that you need to escape the backslash
> >> so it's not expanded when parsing the string, like so:
> >> @code{#\\newline}
> >>
> >> Does this help?
> >>
> >> Jonas
> >
> > @code{#\\newline} did the trick already (I thought I had checked this...)
> > Patch is now up
> > https://gitlab.com/lilypond/lilypond/-/merge_requests/581
> >
> > Though, there is a further question.
> > The patch aims at introducing a new markup-list-command. Thus the
> > doc-string is taken for
> > NR A.12 Text markup list commands
> > This now looks as attached.
> >
> > I'd love to see there
> > "
> > Used properties
> > - split-char (#\newline)
> > "
> >
> > Any chance?
> >
> > Thanks,
> > Harm
> >
> >
> >
>
> It's probably a bug. Try replacing in
>
> (format #f "@item @code{~a} (~a)\n"
>
> in the function doc-markup-function-properties in
> scm/document-markup.scm the second ~a with ~s (which should quote
> everything in read syntax). This would likely have more consequences,
> like when there are string defaults.
>
> --
> David Kastrup
I'll have a look.
Many thanks,
Harm
Re: Doc-string with newline character
Thomas Morley writes:
> Am Mi., 30. Dez. 2020 um 10:37 Uhr schrieb Jonas Hahnfeld :
>>
>> Hi,
>>
>> Am Mittwoch, dem 30.12.2020 um 10:31 +0100 schrieb Thomas Morley:
>> > Hi,
>> >
>> > while preparing a patch a noticed a problem with a doc-string:
>> > I want to refer to newline characters and wrote "@code{#\newline}",
>> > but it comes out as
>> > # ewline
>> > for both pdf and html.
>> > I couldn't figure how to let print
>> > #\newline
>> >
>> > Any hint?
>>
>> I didn't try, but I could imagine that you need to escape the backslash
>> so it's not expanded when parsing the string, like so:
>> @code{#\\newline}
>>
>> Does this help?
>>
>> Jonas
>
> @code{#\\newline} did the trick already (I thought I had checked this...)
> Patch is now up
> https://gitlab.com/lilypond/lilypond/-/merge_requests/581
>
> Though, there is a further question.
> The patch aims at introducing a new markup-list-command. Thus the
> doc-string is taken for
> NR A.12 Text markup list commands
> This now looks as attached.
>
> I'd love to see there
> "
> Used properties
> - split-char (#\newline)
> "
>
> Any chance?
>
> Thanks,
> Harm
>
>
>
It's probably a bug. Try replacing in
(format #f "@item @code{~a} (~a)\n"
in the function doc-markup-function-properties in
scm/document-markup.scm the second ~a with ~s (which should quote
everything in read syntax). This would likely have more consequences,
like when there are string defaults.
--
David Kastrup
Re: output-distance is broken
On Dec 30, 2020, at 14:53, Dan Eble wrote: > > On Dec 30, 2020, at 14:45, Dan Eble wrote: >> >> On Dec 30, 2020, at 13:15, Han-Wen Nienhuys wrote: >>> >>> On Wed, Dec 30, 2020 at 6:23 PM Dan Eble wrote: >>> On Dec 30, 2020, at 11:36, Dan Eble wrote: output-distance fails to detect significant differences (added text, removed bar numbers) in this change: https://gitlab.com/lilypond/lilypond/-/merge_requests/582 https://lilypond.gitlab.io/-/lilypond/-/jobs/938180873/artifacts/test-results/index.html >>> >>> Hm... there are no *.signature files for that case. >>> >>> Looks like the known issue that \book (used for testing page breaking) >>> doesn't generate .signature files. >> >> There must be another factor. When I run this command, I get signature >> files: >> >> out/bin/lilypond -ddump-signatures >> ~/lilypond-src/input/regression/page-turn-page-breaking-repeats.ly > > The other factor is -dbackend=eps. There's an obvious 2-line cut & paste > candidate that I'm trying now. https://gitlab.com/lilypond/lilypond/-/merge_requests/583 — Dan
Re: output-distance is broken
On Dec 30, 2020, at 14:45, Dan Eble wrote: > > On Dec 30, 2020, at 13:15, Han-Wen Nienhuys wrote: >> >> On Wed, Dec 30, 2020 at 6:23 PM Dan Eble wrote: >> On Dec 30, 2020, at 11:36, Dan Eble wrote: >>> >>> output-distance fails to detect significant differences (added text, >>> removed bar numbers) in this change: >>> >>> https://gitlab.com/lilypond/lilypond/-/merge_requests/582 >>> https://lilypond.gitlab.io/-/lilypond/-/jobs/938180873/artifacts/test-results/index.html >> >> Hm... there are no *.signature files for that case. >> >> Looks like the known issue that \book (used for testing page breaking) >> doesn't generate .signature files. > > There must be another factor. When I run this command, I get signature files: > > out/bin/lilypond -ddump-signatures > ~/lilypond-src/input/regression/page-turn-page-breaking-repeats.ly The other factor is -dbackend=eps. There's an obvious 2-line cut & paste candidate that I'm trying now. — Dan
Re: output-distance is broken
On Dec 30, 2020, at 13:15, Han-Wen Nienhuys wrote: > > On Wed, Dec 30, 2020 at 6:23 PM Dan Eble wrote: > On Dec 30, 2020, at 11:36, Dan Eble wrote: > > > > output-distance fails to detect significant differences (added text, > > removed bar numbers) in this change: > > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/582 > > https://lilypond.gitlab.io/-/lilypond/-/jobs/938180873/artifacts/test-results/index.html > > Hm... there are no *.signature files for that case. > > Looks like the known issue that \book (used for testing page breaking) > doesn't generate .signature files. There must be another factor. When I run this command, I get signature files: out/bin/lilypond -ddump-signatures ~/lilypond-src/input/regression/page-turn-page-breaking-repeats.ly -- Dan
Re: output-distance is broken
On Wed, Dec 30, 2020 at 6:23 PM Dan Eble wrote: > On Dec 30, 2020, at 11:36, Dan Eble wrote: > > > > output-distance fails to detect significant differences (added text, > removed bar numbers) in this change: > > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/582 > > > https://lilypond.gitlab.io/-/lilypond/-/jobs/938180873/artifacts/test-results/index.html > > Hm... there are no *.signature files for that case. > Looks like the known issue that \book (used for testing page breaking) doesn't generate .signature files. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: output-distance is broken
On Dec 30, 2020, at 11:36, Dan Eble wrote: > > output-distance fails to detect significant differences (added text, removed > bar numbers) in this change: > > https://gitlab.com/lilypond/lilypond/-/merge_requests/582 > https://lilypond.gitlab.io/-/lilypond/-/jobs/938180873/artifacts/test-results/index.html Hm... there are no *.signature files for that case. — Dan
output-distance is broken
output-distance fails to detect significant differences (added text, removed bar numbers) in this change: https://gitlab.com/lilypond/lilypond/-/merge_requests/582 https://lilypond.gitlab.io/-/lilypond/-/jobs/938180873/artifacts/test-results/index.html — Dan
Re: Elysium help
Daniel, Elysium is a third party tool integrating lilypond (the tool whose -dev maillist you've sent your mail to) and the Eclipse IDE. Your best bets for getting it working would be Elysium's User Community (a Google group) and Elysium github issues. See Elysium's Contact page for links http://elysium.thsoft.hu/contact Kind regards, Hans > On 28 Dec 2020, at 23:05, Daniel Xu wrote: > > Hey there, > I am a student trying to use your eclipse plugin for an app I'm developing, > however, I cannot seem to add the plugin to my IDE despite trying many > suggestions from 3rd party websites, I was wondering if you guys could give > me a demonstration on how to install the plugin and how it would work? > Thanks! > > Kind regards > Daniel Xu >
Re: Doc-string with newline character
Am Mi., 30. Dez. 2020 um 10:37 Uhr schrieb Jonas Hahnfeld :
>
> Hi,
>
> Am Mittwoch, dem 30.12.2020 um 10:31 +0100 schrieb Thomas Morley:
> > Hi,
> >
> > while preparing a patch a noticed a problem with a doc-string:
> > I want to refer to newline characters and wrote "@code{#\newline}",
> > but it comes out as
> > # ewline
> > for both pdf and html.
> > I couldn't figure how to let print
> > #\newline
> >
> > Any hint?
>
> I didn't try, but I could imagine that you need to escape the backslash
> so it's not expanded when parsing the string, like so:
> @code{#\\newline}
>
> Does this help?
>
> Jonas
@code{#\\newline} did the trick already (I thought I had checked this...)
Patch is now up
https://gitlab.com/lilypond/lilypond/-/merge_requests/581
Though, there is a further question.
The patch aims at introducing a new markup-list-command. Thus the
doc-string is taken for
NR A.12 Text markup list commands
This now looks as attached.
I'd love to see there
"
Used properties
- split-char (#\newline)
"
Any chance?
Thanks,
Harm
PATCHES - Countdown for December 30th
Hello, Here is the current patch countdown list. The next countdown will be on January 1st. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !562 Extend CG with a remark about deleting remote local branches - Thomas Morley https://gitlab.com/lilypond/lilypond/-/merge_requests/562 !561 Custos_engraver: avoid reading whichBar - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/561 !560 Melody_engraver: respect mid-measure barlines - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/560 !559 HOWTO.index: Updated. - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/559 !558 Grob_info: miscellaneous clean-up - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/558 Countdown: !566 Engraver/Performer: remove unused code and virtuality - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/566 !565 Encoding fixes for Guile 2.x - Jonas Hahnfeld https://gitlab.com/lilypond/lilypond/-/merge_requests/565 !564 Auto_beam_engraver: clean up the use of whichBar - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/564 !563 backend-library.scm: Sort font definitions in output. - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/563 Review: !576 Bar_number_engraver: fix order dependence - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/576 !575 Timing_translator: measureStartNow and \partial - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/575 !574 Add ly:smob-counts, a histogram of live smob types - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/574 !573 Remove separate CSS files for Internet Explorer - Jonas Hahnfeld https://gitlab.com/lilypond/lilypond/-/merge_requests/573 !571 Add option -ddebug-eval - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/571 !570 Remove -ddebug-gc-assert-parsed-dead - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/570 New: No patches in New at this time. Waiting: No patches in Waiting at this time. *** Regards, James
Re: Doc-string with newline character
> I couldn't figure how to let print
> #\newline
Try the ugly
#@backslashchar{}newline
:-)
Werner
Re: Doc-string with newline character
Hi,
Am Mittwoch, dem 30.12.2020 um 10:31 +0100 schrieb Thomas Morley:
> Hi,
>
> while preparing a patch a noticed a problem with a doc-string:
> I want to refer to newline characters and wrote "@code{#\newline}",
> but it comes out as
> # ewline
> for both pdf and html.
> I couldn't figure how to let print
> #\newline
>
> Any hint?
I didn't try, but I could imagine that you need to escape the backslash
so it's not expanded when parsing the string, like so:
@code{#\\newline}
Does this help?
Jonas
signature.asc
Description: This is a digitally signed message part
Doc-string with newline character
Hi,
while preparing a patch a noticed a problem with a doc-string:
I want to refer to newline characters and wrote "@code{#\newline}",
but it comes out as
# ewline
for both pdf and html.
I couldn't figure how to let print
#\newline
Any hint?
Thanks,
Harm
