Linux

48310 readers

645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

What's the best way to have a .bashrc that I can use throughout systems? (lemmy.ml)

submitted 10 months ago by gary_host_laptop@lemmy.ml to c/linux@lemmy.ml

24 comments fedilink hide all child comments

So, I just found out about a programme called SynthShell which kind of does the work for you and gives you a nice looking shell, the thing is that this also creates some config files and other stuff in my system, instead of just one .bashrc file to edit. What would be the best way to learn to have a nice looking bash where I can just have a backup of it that I can use throughout systems?

you are viewing a single comment's thread
view the rest of the comments

[–] Dirk@lemmy.ml 10 points 10 months ago* (last edited 10 months ago) (1 children)

I personally use yadm

I just use some code and Git.

if [ ! -z "$PS1" ]; then
    repo="${XDG_CONFIG_HOME}/dotfiles/"
    br='origin/main'

    title="\e[1m\e[31m\n ░▒▓\e[7m    %s    \e[27m▓▒░\e[0m\n\n%s\n\n"
    status="$(git --git-dir="$repo" --work-tree="$HOME" status -s)"
    diff=$(git --git-dir="$repo" --work-tree="$HOME" diff --stat --cached $br)

    [ -n "$status" ] && printf "$title" "Uncommited changes!" "$status"
    [ -n "$diff" ] && printf "$title" "Not yet pushed commits!" "$diff"

    unset title status diff br
    alias dotfiles="/usr/bin/git --git-dir=$repo --work-tree=$HOME"
fi

The code runs when it's an interactive shell with a PS1 prompt and just checks if any of the tracked files have changed or if there are commits that are not pushed. By configuration I ignore all untracked files. If something has changed or wasn't pushed it always prints an annoying message.

Whenever I want to do something I use dotfiles ..... instead of git ....., everything else works the same.

[–] beejjorgensen@lemmy.sdf.org 2 points 10 months ago (1 children)

This is the fun way. I have a ton of configuration files in git and I symlink to them from various places with an install script. And zshrc has enough brains to determine the OS it's running under and the hostname. Between those two, I can have it do all the Right Things no matter what system it's on. So far, it deploys to my personal Mac, my work Mac, my personal Linux box, my SDF account, and my Android phone with tmux.

Basically I clone the repo into .local/share/beejsys and then run the install script and everything just works. And I don't typically have to rerun the install script after a pull.

[–] amzd@kbin.social 0 points 10 months ago (1 children)

Do I understand correctly you use the install script for files outside home dir? If so could you share this as I’m running into that issue.

[–] beejjorgensen@lemmy.sdf.org 1 points 10 months ago

No, they're inside my home directory, alas.