config: add ‘include’ directive #561

Manually merged
dnkl merged 1 commits from include-directive into master 6 months ago
dnkl commented 6 months ago
Owner

This allows you to include sub-configurations. For example, theme files.

The include directive is a top-level keyword. I.e. it cannot be used inside sections.

  • The included file must be specified with an absolute path
  • The included file is parsed in its own scope
  • Nested includes are allowed
  • Multiple include directives are allowed

Closes #555

This allows you to include sub-configurations. For example, theme files. The `include` directive is a top-level keyword. I.e. it cannot be used inside sections. * The included file must be specified with an absolute path * The included file is parsed in its own scope * Nested includes are allowed * Multiple include directives are allowed Closes #555
dnkl added the
enhancement
label 6 months ago
dnkl added 1 commit 6 months ago
9055d3d921
config: add ‘include’ directive
dnkl merged commit 23e6a0a0ee into master manually 6 months ago

The included file must be specified with an absolute path

If I read the code correctly, there is no possibility to specify the homedir with e.g. ~, isn't it?

> The included file must be specified with an absolute path If I read the code correctly, there is no possibility to specify the homedir with e.g. `~`, isn't it?
Poster
Owner

@rumpelsepp correct. I wanted to start with the basics. ~ might be a special case we want to have support for from the get go. But things like environment variable expansion should be given a second thought before being implemented...

@rumpelsepp correct. I wanted to start with the basics. `~` might be a special case we want to have support for from the get go. But things like environment variable expansion should be given a second thought before being implemented...
The pull request has been manually merged as 23e6a0a0ee.
Sign in to join this conversation.
Loading…
There is no content yet.