dotfiles/.exportenvs

45 lines
1.3 KiB
Plaintext
Raw Normal View History

#!/usr/bin/env bash
export EDITOR=nv
export DOOMDIR=~/.config/doom/
export EMACSDIR=~/.doomemacs/
export BROWSER=w3m
export FILEMAN=ranger
export TERM=xterm-256color
export GPG_TTY=$(tty)
2021-08-19 09:44:39 +00:00
# telemetry shit
export DO_NOT_TRACK=1 # https://consoledonottrack.com
export DOTNET_CLI_TELEMETRY_OPTOUT=1
2022-12-27 21:21:15 +00:00
export HINT_TELEMETRY="off"
2021-08-19 09:44:39 +00:00
export GATSBY_TELEMETRY_OPTOUT=1
export NEXT_TELEMETRY_DEBUG=1
export NUXT_TELEMETRY_DISABLED=1
export ET_NO_TELEMETRY=1
export NG_CLI_ANALYTICS=false
export INFLUXD_REPORTING_DISABLED=true
export NG_CLI_ANALYTICS=false
export CHOOSENIM_NO_ANALYTICS=1
export POWERSHELL_TELEMETRY_OPTOUT=1
# XDG Base Directory Specification
export XDG_CONFIG_HOME="$HOME/.config"
export XDG_DATA_HOME="$HOME/.local/share"
export XDG_CACHE_HOME="$HOME/.cache"
export XDG_USER_CONFIG_DIR="$XDG_CONFIG_HOME"
envs: Add LD_LIBRARY_PATH and PKG_CONFIG_PATH I use ~/local for compiling packages without root. It emulates /usr/local, basically. So sometimes it might have .pc files etc in corresponding pkgconfig/ in there or .so files in corresponding lib/. I do this because I almost always don't have root, because I work on tildes primarily (tilde.cafe to be specific) so yeah. If a package is written in go or similar where building would be easy, the basic workflow is this: cd ~/local/src git clone git@example.com:user/repo cd repo make PREFIX="$HOME/local" install If all goes well the binary would be available at ~/local/bin. For apt packages there is a higher chance of build failing and most of them need other dependencies (plus some other historical reasons idk) so I don't use ~/local/src[1], here's the general workflow: cd ~/Downloads apt source pkgname cd pkgname ls -A less INSTALL ./configure --prefix=~/local make PREFIX=~/local make install PREFIX=~/local And most likely it would complain about some package not found in the configure step, in which case I woukd repeat the steps for that package. Eventually (if I hadn't given up yet), the binary would be sitting in ~/local/bin nicely. Sometimes the package needs a lot of dependencies, in that case it may take up a shit ton of disk space, so I would pack it in a .tar.gz so it can be saved for future use. For meson projects: cd ~/local/src git clone git@example.com:user/repo ls -A meson setup build meson compile -C build meson install -C build --destdir ~/local rsync ~/local/usr/local/ ~/local/ -avr rsync ~/local/usr/ ~/local/ -avr && rm -rf ~/local/usr I don't use meson often so I'm unaware of a way to easily specify PREFIX, if any. So that's my life of getting stuff installed without root. Thanks for coming to my ted talk. One day I'll probably copy this entire commit msg and make it into a blog post.
2021-09-29 03:36:27 +00:00
# Paths
2023-08-15 13:08:37 +00:00
export LD_LIBRARY_PATH="$HOME/local/lib/x86_64-linux-gnu/:$HOME/local/lib:/opt/pkgsrc/opt/pkg/lib"
export DYLD_LIBRARY_PATH="/opt/pkgsrc/opt/pkg/lib"
envs: Add LD_LIBRARY_PATH and PKG_CONFIG_PATH I use ~/local for compiling packages without root. It emulates /usr/local, basically. So sometimes it might have .pc files etc in corresponding pkgconfig/ in there or .so files in corresponding lib/. I do this because I almost always don't have root, because I work on tildes primarily (tilde.cafe to be specific) so yeah. If a package is written in go or similar where building would be easy, the basic workflow is this: cd ~/local/src git clone git@example.com:user/repo cd repo make PREFIX="$HOME/local" install If all goes well the binary would be available at ~/local/bin. For apt packages there is a higher chance of build failing and most of them need other dependencies (plus some other historical reasons idk) so I don't use ~/local/src[1], here's the general workflow: cd ~/Downloads apt source pkgname cd pkgname ls -A less INSTALL ./configure --prefix=~/local make PREFIX=~/local make install PREFIX=~/local And most likely it would complain about some package not found in the configure step, in which case I woukd repeat the steps for that package. Eventually (if I hadn't given up yet), the binary would be sitting in ~/local/bin nicely. Sometimes the package needs a lot of dependencies, in that case it may take up a shit ton of disk space, so I would pack it in a .tar.gz so it can be saved for future use. For meson projects: cd ~/local/src git clone git@example.com:user/repo ls -A meson setup build meson compile -C build meson install -C build --destdir ~/local rsync ~/local/usr/local/ ~/local/ -avr rsync ~/local/usr/ ~/local/ -avr && rm -rf ~/local/usr I don't use meson often so I'm unaware of a way to easily specify PREFIX, if any. So that's my life of getting stuff installed without root. Thanks for coming to my ted talk. One day I'll probably copy this entire commit msg and make it into a blog post.
2021-09-29 03:36:27 +00:00
export PKG_CONFIG_PATH="$HOME/local/lib/x86_64-linux-gnu/pkgconfig:$HOME/local/lib/pkgconfig"
2022-03-31 09:50:59 +00:00
export NVM_DIR="$HOME/.config/nvm"
2023-01-17 06:54:36 +00:00
# GPG
export PASH_KEYID="F92200AF40D013F0"
# Ugh
export HOMEBREW_PREFIX="/opt/homebrew"
export HOMEBREW_CELLAR="/opt/homebrew/Cellar"
export HOMEBREW_REPOSITORY="/opt/homebrew"