FISH Settings

A lot of the environment-setup stuff that Slackware sets up for BASH and CSH (and I assume, ZSH) isn't done for FISH. Here's my atttempt at adding them back, on a system with ktown and Alien Bob's OpenJDK package:

set -x JAVA_HOME /usr/lib64/java

set -x PATH $PATH /usr/games /usr/lib64/qt/bin /usr/lib64/qt5/bin /usr/lib64/kf5 /usr/lib64/kde4/libexec $JAVA_HOME/bin $JAVA_HOME/jre/bin

set -x MANPATH $MANPATH /usr/man $JAVA_HOME/man

if status --is-login
    echo
    fortune fortunes fortunes2 linuxcookie
    echo
end

if [ -f $HOME/.dir_colors ]
  eval (/bin/dircolors -c $HOME/.dir_colors)
else
  eval (/bin/dircolors -c /etc/DIR_COLORS)
end

set -x KDEDIRS /usr
set -x QT5DIR /usr/lib64/qt5
set -x QT4DIR /usr/lib64/qt
set -x CPLUS_INCLUDE_PATH /usr/lib64/qt/include
    
set -x FREETYPE_PROPERTIES "truetype:interpreter-version=40"
set -x GDK_USE_XFT 1
set -x LANG en_US.UTF-8
set -x T1LIB_CONFIG /usr/share/t1lib/t1lib.config
set -x VDPAU_LOG 0

# This line, in particular, seems to be needed for KDE 5. 
# Without it you just get a black desktop.
set -x XDG_CONFIG_DIRS /etc/xdg:/etc/kde/xdg

set -x XDG_RUNTIME_DIR /tmp/xdg-runtime-$USER
mkdir -p $XDG_RUNTIME_DIR
chown $USER $XDG_RUNTIME_DIR
chmod 700 $XDG_RUNTIME_DIR

set -x PKG_CONFIG_PATH /usr/lib64/pkgconfig /usr/share/pkgconfig

Thanks Dugan for sharing.

You made me discover yet_another_shell.

FWIW here is what I write in .profile, read by several shells including BASH:

export XDG_CACHE_HOME=/dev/shm/$(whoami)
mkdir -p /dev/shm/$(whoami)
chmod 700 /dev/shm/$(whoami)
export XDG_RUNTIME_DIR=$XDG_CACHE_HOME

Rationale:
1) Some upstream devs use XDG_RUNTIME_DIR for the same purposes as other use XDG_CACHE_HOME. Using the same directory for both helps e.g. to find a socket written in the former and looked for in the latter, or reverse, for instance.
2) Using /dev/shm provides an auto-cleaning of the cache when the system goes down for halt or reboot. This avoids the hassle of cleaning the cache manually or limiting it for applications cache-hungry like web browsers. Of course this is more useful when the system is used as a desktop or laptop than as an almost never rebooted server.
3) I didn't encounter an ill effect of these settings so far.

I will make this the default in upcoming Slint release.

As an aside, many people including me like to have /tmp in RAM, but i wouldn't like to impose that to others, especially newbies.

Originally Posted by dugan A lot of the environment-setup stuff that Slackware sets up for BASH and CSH (and I assume, ZSH) isn't done for FISH.

In case anyone is wondering why, the reason is that fish is inherently incompatible with any bourne or C shell. In their efforts of making their shell user friendly they broke any and all compatibility. Note that this is also true between bourne and c shells, but those both have a long history of use while fish reinvented the wheel out of ignorance of how other shells work... (I have friends who are all about fish and have exposed me to it...)

Originally Posted by orbea fish reinvented the wheel out of ignorance

Obviously, that's nonsense. Orbea, just a heads up: I'm tired of your attitude and I've had you on ignore since last week. Just so you know.

That's not a very productive response, if you have some specific complaints you should come out and explain them. Or do you want me to just guess at what attitude you have grown tired of?

That said its not a non-sense complaint. They even broke compatibility with the standard POSIX array. Something that works even with true bourne shells.

See the heirloom shell.
https://slackbuilds.org/repository/1...m/heirloom-sh/

$ eval "set -- foo bar baf"
$ echo $1
foo
$ echo $2
bar
$ echo $3
baf

Or how about the lack of the standard 'and' or 'or' operators.

foo && bar
foo || bar

I assume people who are reading this thread want more than one view point so they can make their own informed opinions. If you just want to sing to the choir I'm not sure a forum is your best venue.

EDIT:

Never mind. I just remembered that announcing that I have you on ignore and then continuing engage with you is silly.