store -dinclude-settings permanently?

[elu...@gmail.com]

hi

I couldn't find how to store this option and I don't like to add it T each run. did I overlook it?

Eluze

[Wilbert Berendsen]

Op Thu, 11 Apr 2013 08:02:41 -0700 (PDT)
elu...@gmail.com schreef:

> I couldn't find how to store this option and I don't like to add it T
> each run. did I overlook it?

Yes :-)

see Edit->Preferences->LilyPond->Include Path, there you can add
directories.

--
Wilbert Berendsen
(http://www.wilbertberendsen.nl)

[Eluze]

there I can only add directories ( --include=D:\Data\ly\includes)

what I want is

-dinclude-settings=D:/data/ly/includes/myInit.ly

Eluze

--
Frescobaldi homepage: http://www.frescobaldi.org/
Mailing list: http://groups.google.com/group/frescobaldi
Issue tracker: https://github.com/wbsoft/frescobaldi/issues

--
Eluze

[Wilbert Berendsen]

Op Fri, 12 Apr 2013 08:38:44 +0200
Eluze <elu...@gmail.com> schreef:

> what I want is
>
> -dinclude-settings=")


Ah, I'm sorry, I wasn't aware.

I could devise a way to permanently use custom LilyPond options, but
I've been reluctant to do that, it makes LilyPond files uncompilable
with another editor because such options are not known to the file
(only to the environment the writer is using).

You could write the option in the file, if that's not too tedious:

#(ly:set-option 'include-settings "D:/data/ly/includes/myInit.ly")

Then LilyPond itself will read it and obey.

But feel free to issue a feature request!

Best regards,
Wilbert

[Eluze]

On Fri, Apr 12, 2013 at 10:58 AM, Wilbert Berendsen <wbs...@xs4all.nl> wrote:

Op Fri, 12 Apr 2013 08:38:44 +0200
Eluze <elu...@gmail.com> schreef:

I could devise a way to permanently use custom LilyPond options, but
I've been reluctant to do that, it makes LilyPond files uncompilable
with another editor because such options are not known to the file
(only to the environment the writer is using).

 

that's true, but it's the same as adding an \include at the top of a  file and that folder is not around… 

You could write the option in the file, if that's not too tedious:

#(ly:set-option 'include-settings "D:/data/ly/includes/myInit.ly")

Then LilyPond itself will read it and obey.

unfortunately this doesn't work as an internal option (it has to be run before the file is compiling)

and yes - it is tedious!

But feel free to issue a feature request!

 

I will! 

Eluze

[Wilbert Berendsen]

Op Fri, 12 Apr 2013 13:04:41 +0200
Eluze <elu...@gmail.com> schreef:

> unfortunately this doesn't work as an internal option (it has to be
> run before the file is compiling)

> and yes - it *is* tedious!

Indeed! I'm sorry, I didn't think very well, I went very late to bed
yesterday....

> >
> > But feel free to issue a feature request!
> >
> >
>
> I will!

Good.
Yes I think it needs to be implemented.

Maybe the stuff running lilypond could use some kind of profile
manager: that you can define several ways of running LilyPond and some
way as the default. The "Engrave (custom)" dialog could then become a
generic profile editing dialog, and you could create more profiles than
just "preview" and "publish".

[Eluze]

On Fri, Apr 12, 2013 at 1:21 PM, Wilbert Berendsen <wbs...@xs4all.nl> wrote:

Op Fri, 12 Apr 2013 13:04:41 +0200

  Good.
Yes I think it needs to be implemented.

many thanks! 

Maybe the stuff running lilypond could use some kind of profile
manager: that you can define several ways of running LilyPond and some
way as the default. The "Engrave (custom)" dialog could then become a
generic profile editing dialog, and you could create more profiles than
just "preview" and "publish".

I mainly use this possibility to define my preferred \language or to include a few (scheme-) definitions taken from the LSR (e.g. \barre).

but of course there are many more conceivable items .

--
Eluze

[Wilbert Berendsen]

Op Fri, 12 Apr 2013 13:49:45 +0200
Eluze schreef:

> I mainly use this possibility to define my preferred \language or to
> include a few (scheme-) definitions taken from the LSR (e.g. \barre).
> but of course there are many more conceivable items .

I could also create a special variable that's read by Frescobaldi and
added to the LilyPond command line before running. Like:

% -*- extra-options: -dinclude-settings="D:\data\myinit.ily";

That way the user of the file can see its requirements later, and
Frescobaldi can handlte them automatically.