Difference between revisions of "Environment variables"

From Linux Gaming
Jump to navigation Jump to search
(Created page with "Environment variables are settings that are passed to programs. == General usage == Environment variables can be written in front of the command that is executed. Syntax: <code>environmentVariable=value myProgram</code>. For example, if you want to pass the variable <code>EDITOR</code> set to <code>nano</code> to <code>crontab -e</code>, you could run <code>EDITOR=nano crontab -e</code>. == Lutris == Let's say you want to enable dxvk_async, so you want to pass <code>D...")
(No difference)

Revision as of 01:34, 23 March 2022

Environment variables are settings that are passed to programs.

General usage

Environment variables can be written in front of the command that is executed. Syntax: environmentVariable=value myProgram. For example, if you want to pass the variable EDITOR set to nano to crontab -e, you could run EDITOR=nano crontab -e.

Lutris

Let's say you want to enable dxvk_async, so you want to pass DXVK_ASYNC=1 to your game.

  • Right click your game, click Configure
  • Click System options and scroll down to Environment Variables
  • Click Add and input DXVK_ASYNC into the Key box, and 1 into Value.