Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No .bashrc or .zshrc files #13

Closed
alexholox opened this issue Sep 16, 2021 · 3 comments
Closed

No .bashrc or .zshrc files #13

alexholox opened this issue Sep 16, 2021 · 3 comments

Comments

@alexholox
Copy link

alexholox commented Sep 16, 2021

LibreGaming command not found. The files you listed simply don't exist. There aren't anywhere and this needs an update. Fix it please.

openSUSE Tumbleweed, followed the instructions religiously and there is absolutely no .bashrc or .zshrc on any part, nor where the guide says nor in /LibreGaming, anywhere. It does not exist. Fix please, thanks.

@ahmed-al-balochi
Copy link
Owner

ahmed-al-balochi commented Sep 16, 2021

Hi,

  • Any file or folder that starts with a dot(.) is always hidden by default. So, you need to show them.
  • to show the files using a terminal:
ls -alh
  • You can access your shell files using this command.
  • for bash
nano .bashrc
  • for zsh
nano .zshrc
  • after you access the shell file you need to add the following lines to your shell file.
### PATH

if [ -d "$HOME/.local/bin" ] ;
  then PATH="$HOME/.local/bin:$PATH"
fi

@alexholox
Copy link
Author

GNU nano 5.8                                  .bashrc                                            
# Sample .bashrc for SUSE Linux
# Copyright (c) SUSE Software Solutions Germany GmbH

# There are 3 different types of shells in bash: the login shell, normal shell
# and interactive shell. Login shells read ~/.profile and interactive shells
# read ~/.bashrc; in our setup, /etc/profile sources ~/.bashrc - thus all
# settings made here will also take effect in a login shell.
#
# NOTE: It is recommended to make language settings in ~/.profile rather than
# here, since multilingual X sessions would not work properly if LANG is over-
# ridden in every subshell.

test -s ~/.alias && . ~/.alias || true

### PATH

if [ -d "$HOME/.local/bin" ] ;
  then PATH="$HOME/.local/bin:$PATH"
fi


This is what I get from using nano .bashrc, is it normal? I don't seem to be able to edit or doing anything with this. What should I do to access the file?

@ahmed-al-balochi
Copy link
Owner

Yes. You need to close the terminal after you paste the PATH. and I have used SUSE to test my LibreGaming and when I pasted the PATH it worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants