Development > Scripting and Bash

What shell do YOU use for scripting or command-line on LL?

<< < (2/5) > >>

Moltke:

--- Quote ---If it is completely safe, please post this idea with a "HELPFUL TIP" tag on it - after all, you make the claim that
it is completely safe and no harm will be made.
Why should I make any backups if it's completely safe? Should it read then: "not so completely safe" ?
--- End quote ---

Indeed. That's how smart Linux is  ;D otherwise those kind of files like .bashrc wouldn't be in your home folder where you can manipulate them at will and you'd need to become root in order to make any changes on them. It is completely safe to do so, I only suggested that in the event that you wished/were to change your shell login and /or prompt, you could make a backup of the the original .bashrc file, just for the sake of it, but it's really not neccesary.


--- Quote ---I'm not making any changes, I use #!/bin/bash in my bash scripts, instead of the usual #!/bin/sh -
because /bin/sh points to dash shell.
--- End quote ---


I never said you should/have to change anything, that's entirely up to you. If you're happy with your config keep it that way no matter what anyone else may say. I use bash, fish, dash, zsh and switch back from one to the other and haven't had any problems whatsoever.  Like I said, it's entirely up to you and nobody else.

This is the contents of my .bashrc:

#
# ~/.bashrc
#

# If not running interactively, don't do anything
[[ $- != *i* ]] && return

alias ls='ls --color=auto'
PS1='[\[email protected]\h \W]\$ '
EDITOR=/usr/bin/nano
# You may uncomment the following lines if you want `ls' to be colorized:
eval "`dircolors -b ~/.dircolorsrc`"
export LS_OPTIONS='--color=auto'
export PS1='\[\e[1;36m\][\t \u \[\e[0m\]\W \$] '

# Correct dir spellings
shopt -q -s cdspell

# Make sure display get updated when terminal window get resized
shopt -q -s checkwinsize

# Turn on the extended pattern matching features
shopt -q -s extglob

# Append rather than overwrite history on exit
shopt -s histappend

# Make multi-line commandsline in history
shopt -q -s cmdhist

# Get immediate notification of background job termination
set -o notify

# Store 2000 commands in history buffer
export HISTSIZE=2000

# Store 2000 commands in history FILE
export HISTFILESIZE=2000     

# Avoid duplicates in hisotry
export HISTIGNORE='&:[ ]*'

And this is how my terminal looks like:



Sorry if I bother you somehow, I didn't mean to do that, I simply shared something that it's posisible and completely, entirely safe to do, because like I said before, Linux is smart enough not to let you screw things up. :)

Cheers!

kpanic:

--- Quote from: Moltke on September 17, 2018, 03:31:36 PM [email protected] it is completely safe to change your login shell and/or prompt to whatever else you want. No harm will be made. However, you can always make a backup of your .bashrc file before whatever change you plan to do and if for any reason you don't feel saisfied with the result or anything goes wrong, you can just replace the .bashrc and get everyhing back to its default. 

hope this helps! :)

--- End quote ---


@Moltke ,

If it is completely safe, please post this idea with a "HELPFUL TIP" tag on it - after all, you make the claim that
it is completely safe and no harm will be made.
Why should I make any backups if it's completely safe? Should it read then: "not so completely safe" ?

I'm not making any changes, I use #!/bin/bash in my bash scripts, instead of the usual #!/bin/sh -
because /bin/sh points to dash shell.

Moltke:
@kpanic it is completely safe to change your login shell and/or prompt to whatever else you want. No harm will be made. However, you can always make a backup of your .bashrc file before whatever change you plan to do and if for any reason you don't feel saisfied with the result or anything goes wrong, you can just replace the .bashrc and get everyhing back to its default. 

hope this helps! :)

kpanic:
@Moltke ,

Thank you for the information!
chsh changes the login shell, I would leave that as it is though, since it is part of the OS.

I suggest that people won't touch the system-wide settings like this. It is so much safer to
just invoke #!/bin/bash to the user scripts instead of the usual #!/bin/sh (which points to dash shell in LL).

Moltke:

--- Quote [email protected] can you add the links in to the threads for the 2 books please ? :)
--- End quote ---

Sure, I will. :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version