On Tue, 15 Feb 2005 12:13:16 -0300 (EST)
"Francisco Welington de Sousa Lima" <[EMAIL PROTECTED]> wrote:
deixa eu ver se adivinho. digamos que voc� tem o script s1 no dir ~/scripts/.
Voc� entra no dir ~/scripts e ao digitar s1 o script n�o executa e o shell
d� uma mensagem de erro?
� isso?
Se for, a sugest�o do seu amigo vai funcionar, mas � uma gambiarra.
Botar o '.' no seu PATH � potencialmente perigoso. O que eu sugiro � que
voc� ligue o script s1 digitando o caminho dele: ~/scripts/s1
ou se estiver em ~/scripts/ simplesmente digite ./s1
Era isso?
Paro por aqui, Fred
>
>
> Ol� pessoal,
> Este � o meu .bashrc do sarge
> # ~/.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 running interactively, then:
> if [ "$PS1" ]; then
>
> # don't put duplicate lines in the history. See bash(1) for more options
> # export HISTCONTROL=ignoredups
>
> # check the window size after each command and, if necessary,
> # update the values of LINES and COLUMNS.
> #shopt -s checkwinsize
>
> # enable color support of ls and also add handy aliases
> if [ "$TERM" != "dumb" ]; then
> eval `dircolors -b`
> alias ls='ls --color=auto'
> #alias dir='ls --color=auto --format=vertical'
> #alias vdir='ls --color=auto --format=long'
> fi
>
> # some more ls aliases
> #alias ll='ls -l'
> #alias la='ls -A'
> #alias l='ls -CF'
>
> # set a fancy prompt
> PS1='${debian_chroot:+($debian_chroot)[EMAIL PROTECTED]:\w\$ '
>
> # If this is an xterm set the title to [EMAIL PROTECTED]:dir
> case $TERM in
> xterm*)
> PROMPT_COMMAND='echo -ne "\033]0;[EMAIL PROTECTED]: ${PWD}\007"'
> ;;
> *)
> ;;
> esac
>
> # enable programmable completion features (you don't need to enable
> # this, if it's already enabled in /etc/bash.bashrc).
> #if [ -f /etc/bash_completion ]; then
> # . /etc/bash_completion
> #fi
>
> fi
> source /opt/intel_fc_80/bin/ifortvars.sh
> O quero saber � se est� faltando um "." no meu PATH, pois estou tentando
> executar uns scripts e n�o funciona , ent�o meu colega questionou isso,
>
>
>
> I think there is a problem with the path defined in your shell (for
> example in your ~/.bashrc file: is there also "." in your definition of
> variable PATH ?)
>
>
>
>
>
>
>
>
> Dr. F. W. S. Lima
> Departamento de F�sica
> Centro de Ci�ncia da Natureza
> Campus Petr�nio Portela
> Universidade Federal do Piau�
> Teresina-Piau�-Brasil
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
