#[Solved stupid mistake on my part] did smthing change in bash?

11 messages · Page 1 of 1 (latest)

stiff rampart
#

I usually execute scripts with dot i.e. $ . script.sh
Suddenly it just closes my terminals instead.
sh script.sh still works
Did smthing actually change or ?

#

same thing happens in tty i think it just exits

#

tried to -x but same was happening
./script.sh was working
quick reboot seems like everything s fine but idk what it might ve been nvm i ll try to see if there s smthing wrong in some config or in some scripts themselves i guess

#

# to help with pip update script
if [ -n "$VIRTUAL_ENV" ]; then
    echo "You are in a virtual environment."
    exit 0
else
    echo "You are not in a virtual environment."
    exit 1
fi

example script that just exits when i run with dot pretty sure it s not the scripts that re the problems but smthing potentially in some config?

stiff rampart
#

tried changing .bashrc to
just

#
# ~/.bashrc
#

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

alias ls='ls --color=auto'
alias grep='grep --color=auto'
PS1='[\u@\h \W]\$ '

from /etc/skel/.bashrc still same
I just dont know how to go about debuggin this

#

atleast managed to officially catch it i guess in vsocde in an emulator it s too fast it exits with code 1

#

same with sourcing them

#

f it might just be smthing with pip/python or some error with the outputs from the command that i check with instead others seem to be running fine

stiff rampart
#

f duh sry i exit and i dont remember it exiting actual terminal cuz i was using this within other scripts my bad

#

I guess it was more of a question between running in current or new session

#

did smthing change in bash? [Solved stupid mistake on my part]