#40daysofnetbsd — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #40daysofnetbsd, aggregated by home.social.
-
Day 11
NetBSD is a nice thing. I donated a bit today so we can keep having nice things.
-
Day 11
NetBSD is a nice thing. I donated a bit today so we can keep having nice things.
-
Day 11
NetBSD is a nice thing. I donated a bit today so we can keep having nice things.
-
Day 11
NetBSD is a nice thing. I donated a bit today so we can keep having nice things.
-
Day 11
NetBSD is a nice thing. I donated a bit today so we can keep having nice things.
-
Day 10
I added colors to my PS1 in sh. Figuring out the proper color codes didn't take long, but I ran into the issue that moving up to view command history would mess up my prompt and send the cursor bouncing.
Turns out color bytes were throwing off the calculation of prompt length. There is a special built-in shell variable - PSlint - that allow marking non-printing chars and removing from that calculation.
Manpages for the win!
-
Day 10
I added colors to my PS1 in sh. Figuring out the proper color codes didn't take long, but I ran into the issue that moving up to view command history would mess up my prompt and send the cursor bouncing.
Turns out color bytes were throwing off the calculation of prompt length. There is a special built-in shell variable - PSlint - that allow marking non-printing chars and removing from that calculation.
Manpages for the win!
-
Day 10
I added colors to my PS1 in sh. Figuring out the proper color codes didn't take long, but I ran into the issue that moving up to view command history would mess up my prompt and send the cursor bouncing.
Turns out color bytes were throwing off the calculation of prompt length. There is a special built-in shell variable - PSlint - that allow marking non-printing chars and removing from that calculation.
Manpages for the win!
-
Day 10
I added colors to my PS1 in sh. Figuring out the proper color codes didn't take long, but I ran into the issue that moving up to view command history would mess up my prompt and send the cursor bouncing.
Turns out color bytes were throwing off the calculation of prompt length. There is a special built-in shell variable - PSlint - that allow marking non-printing chars and removing from that calculation.
Manpages for the win!
-
Day 10
I added colors to my PS1 in sh. Figuring out the proper color codes didn't take long, but I ran into the issue that moving up to view command history would mess up my prompt and send the cursor bouncing.
Turns out color bytes were throwing off the calculation of prompt length. There is a special built-in shell variable - PSlint - that allow marking non-printing chars and removing from that calculation.
Manpages for the win!
-
Day 9
Today was a step away from GUI back to console. By default in sh there is no persistent history saved between sessions. Add:
HISTFILE="$HOME/.sh_history"
HISTSIZE=10000
HISTAPPEND=true...to .shrc to make one.
Change directory and immediately list contents is one of the most frequent actions in console/terminal. Add function to combine them:
c() {
cd "${1:-$HOME}"
lsd -al --icon never
}Stick with sh or switch to a different shell? Hmm..
-
Day 9
Today was a step away from GUI back to console. By default in sh there is no persistent history saved between sessions. Add:
HISTFILE="$HOME/.sh_history"
HISTSIZE=10000
HISTAPPEND=true...to .shrc to make one.
Change directory and immediately list contents is one of the most frequent actions in console/terminal. Add function to combine them:
c() {
cd "${1:-$HOME}"
lsd -al --icon never
}Stick with sh or switch to a different shell? Hmm..
-
Day 9
Today was a step away from GUI back to console. By default in sh there is no persistent history saved between sessions. Add:
HISTFILE="$HOME/.sh_history"
HISTSIZE=10000
HISTAPPEND=true...to .shrc to make one.
Change directory and immediately list contents is one of the most frequent actions in console/terminal. Add function to combine them:
c() {
cd "${1:-$HOME}"
lsd -al --icon never
}Stick with sh or switch to a different shell? Hmm..
-
Day 9
Today was a step away from GUI back to console. By default in sh there is no persistent history saved between sessions. Add:
HISTFILE="$HOME/.sh_history"
HISTSIZE=10000
HISTAPPEND=true...to .shrc to make one.
Change directory and immediately list contents is one of the most frequent actions in console/terminal. Add function to combine them:
c() {
cd "${1:-$HOME}"
lsd -al --icon never
}Stick with sh or switch to a different shell? Hmm..
-
Day 9
Today was a step away from GUI back to console. By default in sh there is no persistent history saved between sessions. Add:
HISTFILE="$HOME/.sh_history"
HISTSIZE=10000
HISTAPPEND=true...to .shrc to make one.
Change directory and immediately list contents is one of the most frequent actions in console/terminal. Add function to combine them:
c() {
cd "${1:-$HOME}"
lsd -al --icon never
}Stick with sh or switch to a different shell? Hmm..