On 2013/04/27 06:14:00, Keith wrote:
That
symptom is probably a sign that it was unwise to have \hspace try to
correct for
inter-word space.
Definitely. Given the amount of trouble we have had with \hspace so far
(we have several alignment problems open in the context of trying to
allow \hs
On 2013/04/27 05:38:12, dak wrote:
On 2013/04/27 05:29:48, Keith wrote:
> (In version 2.16, \hspace sees the global 'word-space' and corrects
for it
> whether it locally effective or not, closing the gap in the first
line, "Page3
> contains".)
Issue 1100 has only been fixed in version 2.17
On 2013/04/27 05:29:48, Keith wrote:
https://codereview.appspot.com/8639045/diff/1/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (left):
https://codereview.appspot.com/8639045/diff/1/scm/define-markup-commands.scm#oldcode4083
scm/define-markup-commands.scm:4083: (markup
https://codereview.appspot.com/8639045/diff/1/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (left):
https://codereview.appspot.com/8639045/diff/1/scm/define-markup-commands.scm#oldcode4083
scm/define-markup-commands.scm:4083: (markup #:concat (#:hspace gap
page-markup)))
On 2013/04/24 17:16:14, fanziye1 wrote:
I found the variable 'pitchnames'(Thanks for your teaching:).
There is a note-name->lily-string procedure can be used to get a
pitch's name.
Now I want to use it in C++ code. According to the Guile Reference,
'gh_call'
seems a right choice. But I found
