Phundrak’s fish config

Presentation
Fish from within Emacs
Tramp remote access
Regular fish shell appearance
Global variables
Abbreviations

Presentation

The file present in ~/.config/fish/config.fish is the configuration file for the fish shell. It contains custom functions, environment variables and abbreviations.

Just in case, we might need sometimes to declare the fish function fish_title as true, so let’s do so.

  function fish_title
      true
  end

Fish from within Emacs

I sometimes call fish from within emacs, with M-x ansi-term. In this case, the variable TERM needs to have the value eterm-color.

  if test -n "$EMACS"
      set -x TERM eterm-color
  end

Tramp remote access

When accessing from a remote machine our computer from Emacs, tramp needs a precise shell appearance: a simple $ followed by a space after which to put the commands it needs to execute, and nothing else. Due to this, let’s deactivate and redefine some of the functions defining the appearance of fish.

  if test "$TERM" = "dumb"
      function fish_prompt
          echo "\$ "
      end
      function fish_right_prompt; end
      function fish_greeting; end
      function fish_title; end
  end

Regular fish shell appearance

Now, there is only one function I modify when it comes to the appearance of fish when I’m the one using it: I simply “delete” the fish_greeting function.

  function fish_greeting; end

Global variables

Some global variables might sometimes be needed and need to be modified. This is for example the case with my PATH variable in which I add Rust’s Cargo’s binaries, Go’s binaries and my own executables. And of course, don’t forget to add the already existing PATH.

additional path	what it leads to
$HOME/.pub-cache/bin	Dart binaries and executables
$HOME/.local/bin	Custom executables, see /phundrak/config.phundrak.com/src/commit/82eab10cde0408a26222a6cf90007ef9df07ae62/org/config/bin.org
$HOME/go/bin	Go binaries and executables
$HOME/.cargo/bin	Rust binaries and executables
$HOME/.gem/ruby/2.6.0/bin	Ruby binaries and executables

$HOME/.pub-cache/bin $HOME/.local/bin $HOME/go/bin $HOME/.cargo/bin $HOME/.gem/ruby/2.6.0/bin

  set -gx PATH <<generate-extra-paths()>> $PATH

Sometimes, software will rely on SUDO_ASKPASS to get a GUI from which it can get the sudo password. So, let’s declare it.

  set -gx SUDO_ASKPASS ~/.local/bin/askpass

Now, let’s declare our editor of choice, EmacsClient; not Emacs itself since it will most often be just quick edits, nothing too heavy, if it is called from the EDITOR variable (from Git, for example).

  set -gx EDITOR emacsclient -c

We also need to set the path to the Dart SDK.

set -gx DART_SDK /opt/dart-sdk/bin

And we also need to specify where the Android SDK it located.

set -gx ANDROID_HOME $HOME/Android/Sdk

Finally, some development packages require the PKG_CONFIG_PATH to be set, so let’s do so.

  set -gx PKG_CONFIG_PATH /usr/local/lib/pkgconfig/ $PKG_CONFIG_PATH

Abbreviations

System monitoring

Here I have some abbreviations which are quite useful when performing some system monitoring. With df, we can get an overview of our filesystem usage, while with diskspace we get some more precise information. meminfo is a call to free with sane defaults, and similar to meminfo, we also have gpumeminfo so we can get a quick look at the memory-related logs of our X session. I also declared cpuinfo an alias of lscpu in order to keep consistent with meminfo. pscpu gives us information on what the CPU is running right now, and pscpu10 limits that to the top 10 threads. Similarly, psmem gives us information on the memory usage of the current threads, and psmem10 only the ten most important threads in terms of memory usage.

abbreviation	command
df	df -H
diskspace	sudo df -h \| grep -E "sd\|lv\|Size"
meminfo	free -m -l -t
gpumeminfo	grep -i –color memory /var/log/Xorg.0.log
cpuinfo	lscpu
pscpu	ps auxf \| sort -nr -k 3
pscpu10	ps auxf \| sort -nr -k 3 \| head -10
psmem	ps auxf \| sort -nr -k 4
psmem10	ps auxf \| sort -nr -k 4 \| head -10

  <<generate-abbr(table=mgmt-abbr)>>

System management (packages and services)

I added some of these abbreviations due to how often I have to write the whole thing.

Package management

The first command is remove which removes a package from my system, as well as its dependencies no longer needed. p. pacman's or yay's. This is why I simply type purge. And if I want to simply seach among the pacman repos, I can type search. Otherwise, if I want to include AUR results, I’ll use yay.

abbreviation	command
remove	sudo pacman -Rscnd
p	sudo pacman
purge	yay -Sc
search	yay -Ss

  <<generate-abbr(table=pm-abbr)>>

Service management

I don’t have the muscle memory of systemctl. So instead, I simply type c when I want to do something user service related. And if I want to manipulate system services, I can instead type a simple capital S.

abbreviation	command
s	systemctl –user
S	sudo systemctl

  <<generate-abbr(table=service-abbr)>>

Development

A good amount of these commands are development related, especially when it comes to compilation or Docker.

CMake

I have the following abbreviations so I can quickly run CMake and create a configuration for debug or release profiles.

abbreviation	command
cdebug	cmake -DCMAKE_BUILD_TYPE=Debug
crelease	cmake -DCMAKE_BUILD_TYPE=Release