LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Poll: What shell do YOU use for scripting or command-line on LL?
You do not have permission to vote in this poll.
bash
88.89%
8 88.89%
csh
0%
0 0%
tcsh
0%
0 0%
fish
11.11%
1 11.11%
Other shell, or 2 shells for different purposes (please comment)
0%
0 0%
Total 9 vote(s) 100%
* You voted for this item. [Show Results]

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What shell do YOU use for scripting or command-line on LL?
#19
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" ?

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.


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='[\u@\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:

[Image: t9uu8o.jpg]

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. Smile

Cheers!
Without each others help there ain't no hope for us Smile
Need a translation service? https://www.deepl.com/es/translator
Reply


Messages In This Thread
Re: What shell do YOU use for scripting or command-line on LL? - by Moltke - 09-17-2018, 10:10 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)