Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing Environement variables in settings #388

Open
hashken opened this Issue Apr 11, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@hashken
Copy link
Contributor

hashken commented Apr 11, 2015

I want to be able to set my logs folder to $XDG_CACHE_HOME/weechat/logs and scripts folder to $XDG_DATA_HOME/weechat/scripts. But, giving these strings in the respective log path and script path settings, doesn't seem to work. How can I access exported environment variables in weechat settings?

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Apr 11, 2015

You can not access environment variables from WeeChat options.
But I could add a way to do it: some options where you need that (like logger path) could be evaluated, and I could add a format like ${env:XDG_CACHE_HOME} to read the environment variable XDG_CACHE_HOME.

flashcode added a commit that referenced this issue Apr 26, 2015

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Apr 26, 2015

This commit is a first step, it allows use of ${env:XXX} in evaluated strings.

The next step is to evaluate options with paths, and if needed add new options to customize paths (for example path to scripts can not be customized currently; it's just possible to change path for repository file, which is ~/.weechat/script/plugins.xml.gz by default).

@flashcode flashcode self-assigned this Apr 26, 2015

@flashcode flashcode added this to the 1.3 milestone May 1, 2015

flashcode added a commit that referenced this issue Jun 19, 2015

flashcode added a commit that referenced this issue Jun 20, 2015

flashcode added a commit that referenced this issue Jun 21, 2015

flashcode added a commit that referenced this issue Jun 27, 2015

@flashcode flashcode modified the milestones: 1.4, 1.3 Aug 14, 2015

@flashcode flashcode removed this from the 1.4 milestone Jan 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.