Re: nopc -- Proposed Predefines

[Bertalan Fodor (LilyPondTool)]

Yeah, it was very difficult. Exactly 3 clicks in LilyPondTool since 
years. (LilyPond > Source editing > Toggle point-and-click)

I don't think we should crowd the LilyPond command namespace with editor 
features.

Bert

James E. Bailey wrote:
> Am 14.07.2008 um 04:21 schrieb Carl Sorensen:
>
> > Mats Bengtsson <mats.bengtsson <at> ee.kth.se> writes:
> >
> > > James E. Bailey wrote:
> > >
> > > > in 3.1.3
> > > > #(ly:set-option 'point-and-click #f)
> > > >
> > > > The last one is apparently deprecated.
> > >
> > > Why? The first two are only interesting if you have your own standard
> > > include file with utility functions. I guess that most users will copy
> > > paste the code from the manual or from some previous file and in that
> > > case, the third option is easiest to use, since it's only a single 
> > > line.
> > > Considering the recent trend to add predefined commands to LilyPond, 
> > > I'm
> > > surprised that noone has proposed to add the \noPointAndClick function.
> > > I prefer that one to the #(nopc) since it avoids the Scheme syntax for
> > > the end user.
> >
> >
> > OK, I'll bite.
> >
> > I propose some new predefined functions:
> >
> > \pointAndClickOn
> >
> > pointAndClickOn = #(ly:set-option 'point-and-click #t)
> >
> > and
> >
> > \pointAndClickOff
> >
> > pointAndClickOff = #(ly:set-option 'point-and-click #f)
> >
> >
> >
> >
> > If I get approval, I'll add them.
> >
> > Any votes?
> >
> > Carl
>
> I think it's brilliant, and I've always wondered why it was so 
> difficult to turn the feature off.
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user