--> 2 - I think that properties should be fine (parsing of config file has to be very fast), but multiline options should be available e.g.:

(In the above example indentation and margin, denote multiline literal. It's just my suggestion on how to handle multiline literals - it can also be implemented differently)

Please see 'test/resources/custom_dsl/mydsl' for a full example of a script with the preamble.

kscript configuration file should be optional - without it, the app should work as it works now. Resolving configuration should be always done in order: 1) kscript parameters, 2) env variables, 3) config file, 4) defaults. Please see at ConfigBuilder to get an idea of how it works now.

You can implement just single property as proof of concept, let's say above 'kscript.preamble'. Other properties can be added later, as needed.

--> 3 - Yes, that's probably the most difficult part of developing kscript - it should work on many different OS-es, and no one can be expert in every OS... :-) Please just try to do your best - maybe someone else can help later.

Respect XDG Spec #323

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions