On 9/29/2021 3:35 PM, David Kastrup wrote:
John Wheeler writes:
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing
issue?
It was more of a matter of it having become comparatively uninformative
due
On 9/29/2021 6:13 PM, Jean Abou Samra wrote:
Le 30/09/2021 à 01:11, John Wheeler a écrit :
I must be the one exception to "nobody uses this", I appreciate the
"good luck" wish.
Curious: what is your use case?
I originally started down this path because I wante
On 9/29/2021 6:32 PM, David Kastrup wrote:
John Wheeler writes:
On 9/29/2021 3:35 PM, David Kastrup wrote:
John Wheeler writes:
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing
issue
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing issue?
Thank you,
John Wheeler
On 9/30/2021 1:17 AM, Jean Abou Samra wrote:
Le 30/09/2021 à 05:38, John Wheeler a écrit :
In jest I add: reading the code is a lot of fun, but I miss the
programmer's guide to the lilypond language and it's libraries.
Do you think there is enough interest in programming in lilypond
Jean,
My concern for color blindness stemmed from having worked on government
manuals probably two decades ago. We were taught that you should
include nothing that relied solely on color to make sense of the text.
If you are working to modern web accessibility guidelines you are
certainly
On 11/20/2021 5:57 AM, Michael Käppler wrote:
The thing is that it is part of a 'heredoc' string, which is written to
.bashrc.
Without escaping the '$', the shell will evaluate the result of
$(declare -F __git_ps1 &>/dev/null && __git_ps1 " (%s)")
before writing to .bashrc, which is not what
On 11/15/21 1:12 PM, Jean Abou Samra wrote:
Le 15/11/2021 à 20:05, Aaron Hill a écrit :
It looks like some folks even go as far as prefixing
'dev//'. Is this again just personal preference?
Even though I haven't seen it documented, it
is the overwhelming convention to be sure to
avoid
Jean,
My build was failing with similar messages until I ran
rm -fr ./configure
./autogen.sh --noconfigure
in the source directory.
This seems to have been needed to get ./configure to assign the correct
program name to the PLTOTF make variable.
Would this need a note in CG?
John
On
To facilitate using emacs xref in lilypond work, I wrote a script to
assemble the needed TAGS file. The unique feature of the script is that
it includes the regex to find tags in Lilypond (.ly) files as well as
tags defined in LY_DEFINE* macros, in addition to the normal c++,
python, lisp,
ng the script should be kept,
which seems to imply that the script should works.
Is this a known issue?
Thank you,
John Wheeler
This is a probably nit, but I thought I'd ask.
The Contributor's Guide 4.2.2 subheading Other states a requirement for
Texinfo version 6.1 or newer.
The web.texi file contains the excerpt:
@c next line is necessary for broken pre-4.13 texinfo's
@c install-info, so leave it there until we
All,
I am looking for any information that can help me understand
decisions made a year or so ago relating to the install/uninstall
process for info files.
First, why is the default 'make install' behavior to not install
the web and snippets info docs or the images?
Second, why is it assumed
Please forgive this second attempt to reply:
Jean,
On 4/28/22 16:14, Jean Abou Samra wrote:
Is it a large script?
If so, it needs some consideration. If not, can it fit in an @example
somewhere in the CG? That might also make it more visible.
The 'script' consists of a shell script to gather
On 5/7/22 06:05, David Kastrup wrote:
David Kastrup writes:
Jonas Hahnfeld via Discussions on LilyPond development
writes:
On Fri, 2022-05-06 at 20:42 -0500, John Wheeler wrote:
Please forgive this second attempt to reply:
Jean,
On 4/28/22 16:14, Jean Abou Samra wrote:
Is it a large
Jean,
On 4/28/22 16:14, Jean Abou Samra wrote:
Hi John,
Le 24/04/2022 à 21:10, John Wheeler a écrit :
To facilitate using emacs xref in lilypond work, I wrote a script to
assemble the needed TAGS file. The unique feature of the script is
that it includes the regex to find tags in Lilypond
On 5/8/22 09:17, Jonas Hahnfeld wrote:
On Sat, 2022-05-07 at 22:14 -0500, John Wheeler wrote:
On 5/7/22 06:05, David Kastrup wrote:
David Kastrup writes:
Jonas Hahnfeld via Discussions on LilyPond development
writes:
I've traditionally been opposed to adding more such scripts
Indeed, the second regex would add a tag for the Scheme function name
before Jean's change. Maybe it's worth considering reverting it?
If my merge request is accepted there will be no need to revert it.
John
On 5/9/22 16:10, Jean Abou Samra wrote:
Random idea: how about taking a difference approach and doing this
in LY_DEFINE instead? You can do something along the lines
of
scm_set_object_property_x (the_resulting_scm_procedure,
ly_symbol2scm ("c++-location"),
On 5/9/22 17:43, Jean Abou Samra wrote:
Le 10/05/2022 à 00:37, John Wheeler a écrit :
The TAGS file structure is simple enough, and I agree having
only one place to maintain name mangling logic is good.
But, I am not following you on the reference to
'out/bin/lilypond -ddump-tags'. Is -ddump
On 3/19/23 11:51, David Kastrup wrote:
So how to better involve others?
Maybe a good place to start is by asking a few questions.
What you would like these others to do? What qualifications
would they need?
John Wheeler
ular
David Zelinsky or I could do to help your current efforts? Perhaps,
if you have a some specific improvements you think are worth
pursuing we could see how well we could contribute.
Thank you,
John Wheeler
arser.yy code trying
to put together something along those lines for own use. Right now that
work is stuck at a *rough* draft.
Given that effort, I think I have a fair idea of how the lexer/parser
functions. I would be happy to contribute in this area.
How can I be of service?
John Wheeler
23 matches
Mail list logo
