From 0ea03d7f266b419d34238daa883d8a2641c0b875 Mon Sep 17 00:00:00 2001
From: camoz <camoz@users.noreply.github.com>
Date: Mon, 16 May 2022 17:48:13 +0200
Subject: [PATCH] Updated Setting Environmental Variables (markdown)

---
 Setting-Environmental-Variables.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/Setting-Environmental-Variables.md b/Setting-Environmental-Variables.md
index c9d7504..34d48b8 100644
--- a/Setting-Environmental-Variables.md
+++ b/Setting-Environmental-Variables.md
@@ -12,10 +12,7 @@ Environment variables are inherited from the process that starts sway. You need
 ## Login Manager
 
 ### PAM
-Set environment variables specific to user session in the `$HOME/.pam_environment`. That gets them set right on log in and would work for most methods of launching sway.
-Note: these variables will be set in non-sway sessions too.
- 
-For more info: ```man 8 pam_env```
+Setting user environment variables via PAM (`$HOME/.pam_environment`) is deprecated since PAM 1.5.0 and therefore discouraged, see https://github.com/linux-pam/linux-pam/releases/tag/v1.5.0.  
 
 ### Set the Sway Config
 Technically, you could set them in your sway config.