Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 03/04/2020, à 18:03

philoeil

[RESOLU] chemin path dans .bashrc non pris en compte pourquoi

Bonjour,

J'ai modifié ainsi mon fichier utilisateur .bashrc
Pour ajouter à mon path
:/home/phil/BinPhil
Ci-dessous mon fichier utilisateur .bashrc complet

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
	# We have color support; assume it's compliant with Ecma-48
	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
	# a case would tend to support setf rather than setaf.)
	color_prompt=yes
    else
	color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi
export PATH=$PATH:/home/phil/BinPhil

Pourquoi le script SavDD_V13.sh placé dans :/home/phil/BinPhil
ne s'execute pas ni depuis un autre repertoire ni depuis /home/phil/BinPhil

phil@phil-G750JH:~/BinPhil$ SavDD_V13.sh
SavDD_V13.sh : commande introuvable
phil@phil-G750JH:~/BinPhil$
phil@phil-G750JH:~/BinPhil$ pwd
/home/phil/BinPhil
phil@phil-G750JH:~/BinPhil$ 
phil@phil-G750JH:~/BinPhil$ ls -alh
total 20K
drwxr-xr-x  2 phil phil 4,0K avril  3 18:01 .
drwxr-xr-x 61 phil phil 4,0K avril  3 18:01 ..
-rwxr-xr-x  1 phil phil 8,2K avril  3 16:59 SavDD_V13.sh
phil@phil-G750JH:~/BinPhil$ 

Merci

Dernière modification par philoeil (Le 03/04/2020, à 19:18)

Hors ligne

#2 Le 03/04/2020, à 18:23

pingouinux

Re : [RESOLU] chemin path dans .bashrc non pris en compte pourquoi

Bonjour,
As-tu essayé de lancer ton script à partir d'un terminal ouvert après la modification de .bashrc ?

Hors ligne

#3 Le 03/04/2020, à 19:17

philoeil

Re : [RESOLU] chemin path dans .bashrc non pris en compte pourquoi

Bonjour,
Effectivement
C'est trop bête! 1h pour ça ! gasp!:(
Merci bien

Hors ligne

#4 Le 05/04/2020, à 19:45

Zococo

Re : [RESOLU] chemin path dans .bashrc non pris en compte pourquoi

Pour mettre à jour le terminal :

usr@pc: source .bashrc

Ubuntu 23.04 (64 bits) - Gigabyte B250M-DS3H / Core i5-7600K (Kaby lake) - Microsoft surface Go 3

Hors ligne