You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an outstanding issue for me, but I log it here for other beginners.
I had issues running the scripts/systemd-install.sh file.
There were two errors. First, the directory location of this line:
DECB_PATH=whereis dmenu_extended_cache_build | sed 's/dmenu_extended_cache_build: ?//'`
did not seem to work as it led to this line:
echo "dmenu_extended_cache_build not found at the default location."
However, running whereis dmenu_extended_cache_build separately did seem to yield a correct path. I think this had something to do with the fact that the path between my bash shell and zsh shell were not the same (I ran it via sudo bash systemd-install.sh but within a zsh shell).
However, I was able to put in the correct path when prompted.
The other issue for me was that I needed to correct this line:
so that it copied the correct script. I think for users that are cd'ed to the scripts folder (where the sh file resides) the ../ path specification is necessary.
The text was updated successfully, but these errors were encountered:
This is not an outstanding issue for me, but I log it here for other beginners.
I had issues running the
scripts/systemd-install.sh
file.There were two errors. First, the directory location of this line:
DECB_PATH=
whereis dmenu_extended_cache_build | sed 's/dmenu_extended_cache_build: ?//'`did not seem to work as it led to this line:
echo "dmenu_extended_cache_build not found at the default location."
However, running
whereis dmenu_extended_cache_build
separately did seem to yield a correct path. I think this had something to do with the fact that the path between my bash shell and zsh shell were not the same (I ran it viasudo bash systemd-install.sh
but within a zsh shell).However, I was able to put in the correct path when prompted.
The other issue for me was that I needed to correct this line:
cp -v ../systemd/update-dmenu-extended-db.timer $SCRIPT_PATH
so that it copied the correct script. I think for users that are cd'ed to the scripts folder (where the sh file resides) the ../ path specification is necessary.
The text was updated successfully, but these errors were encountered: