Le 10/05/2022 à 01:58, John Wheeler a écrit :
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
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
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-tags a command line option
to the
John Wheeler writes:
> 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,
>>
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"),
Le 09/05/2022 à 22:56, John Wheeler a écrit :
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.
Random idea: how about taking a difference
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 Sun, 2022-05-08 at 22:10 -0500, John Wheeler wrote:
> On 5/8/22 09:17, Jonas Hahnfeld wrote:
> > Let me give a (very biased) summary of this: There's apparently a
> > related (and undocumented) 'make TAGS' that is broken for out-of-
> > tree builds. Instead of fixing this, the proposal was to
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 to
the
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 to
> > > > the LilyPond
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
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 script?
>>>
> Well, I'm an unsophisticated Emacs user, so I'd appreciate thoughts
> from Werner or David.
Mhmm, I don't use Emacs for editing LilyPond input files, so I don't
have an opinion here.
What I can imagine is to have, say, a git repository, and the CG
containing a link to that.
Werner
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 script?
>> > If so, it needs some consideration.
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 script?
> > If so, it needs some consideration. If not, can it fit in an @example
> > somewhere in the CG? That might
Le 07/05/2022 à 03:42, John Wheeler a écrit :
Please forgive this second attempt to reply:
Sorry, I received the first one, but dropped the ball.
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
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
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
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 (.ly) files as
well as tags defined in LY_DEFINE*
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,
20 matches
Mail list logo
