Hi,
Stephen P. Molnar wrote:
> None of the alias's work.
That would be the effect of
unalias -a
or of a subshell which exits before you try to execute "l" again
$ ( alias xyz='echo xyz' ; alias xyz ) ; alias xyz
alias xyz='echo xyz'
bash: alias: xyz: not found
Have a nice day :)
On Mon, Oct 17, 2016 at 03:32:20PM -0400, Stephen P. Molnar wrote:
> None of the alias's work.
Please show us what you're doing. What commands are you running
in between the point where the alias works, and the point where it
does not work? What happens when you run "l" after the latter point?
-Original Message-
From: Thomas Schmitt [mailto:scdbac...@gmx.net]
Sent: Monday, October 17, 2016 3:18 PM
To: debian-user@lists.debian.org
Subject: Re: Jessie - Strange Alias Problem
Hi,
S. P. Molnar wrote:
> comp@AbNormal:~$ trap
> ...
> comp@AbNormal:~$ echo "$
Hi,
S. P. Molnar wrote:
> comp@AbNormal:~$ trap
> ...
> comp@AbNormal:~$ echo "$PROMPT_COMMAND"
These do not look like they could be the culprit.
> comp@AbNormal:~$ alias
> alias adt='/home/comp/Apps/MGLTools-latest/bin/adt'
> alias l='ls -l --color'
> alias ls='ls --color=auto'
> alias
On 10/17/2016 01:41 PM, Thomas Schmitt wrote:
Hi,
S. P. Molnar wrote:
-bash: alias: l: not found
The command which makes this reproducible for me is
unalias l
Greg Wooledge wrote:
[...] DEBUG trap [...] PROMPT_COMMAND [...]
[...] alias or function overriding the cd command.
So many
Hi,
S. P. Molnar wrote:
> > -bash: alias: l: not found
The command which makes this reproducible for me is
unalias l
Greg Wooledge wrote:
> [...] DEBUG trap [...] PROMPT_COMMAND [...]
> [...] alias or function overriding the cd command.
So many interesting ways to shoot the own foot.
@S.
On Mon, Oct 17, 2016 at 12:53:41PM -0400, S. P. Molnar wrote:
> comp@AbNormal:~$ alias l
> -bash: alias: l: not found
Use "type l" immediately after sourcing the .bashrc file. Then do it
again, then do your cd, then do it a third time.
If the .bashrc is simply malformed, then the alias ought
On 10/17/2016 12:55 PM, Thomas Schmitt wrote:
Hi,
i wrote:
What exactly do you mean by "[to] source" ?
Stephen P. Molnar wrote:
source /home/comp/.bashrc
I had already tested with
. ~/.bashrc
Now re-tried with
source ~/.bashrc
and the same result. I get colors if there are
Hi,
i wrote:
> > What exactly do you mean by "[to] source" ?
Stephen P. Molnar wrote:
> source /home/comp/.bashrc
I had already tested with
. ~/.bashrc
Now re-tried with
source ~/.bashrc
and the same result. I get colors if there are color-worthy files.
When it does not work for you, what
-Original Message-
From: Thomas Schmitt [mailto:scdbac...@gmx.net]
Sent: Monday, October 17, 2016 12:27 PM
To: debian-user@lists.debian.org
Subject: Re: Jessie - Strange Alias Problem
Hi,
S. P. Molnar wrote:
> I have the following line in my /home/comp/.bashrc; alias l='ls
Hi,
S. P. Molnar wrote:
> I have the following line in my /home/comp/.bashrc;
> alias l='ls -l --color'
> If I source the file in my /home/comp it works - once!, and only in my home
> directory!!!
What exactly do you mean by "[to] source" ?
> If I change to another directory - it doesn't
I am running an up to date Jessie with the bash shell and have
encountered a very strange problem.
I have the following line in my /home/comp/.bashrc;
alias l='ls -l --color'
If I source the file in my /home/comp it works - once!, and only in my
home directory!!! If I change to another
On Mon, Oct 17, 2016 at 10:34:11AM -0400, S. P. Molnar wrote:
> I have the following line in my /home/comp/.bashrc;
>
> alias l='ls -l --color'
>
> If I source the file in my /home/comp it works - once!, and only in my
> home directory!!! If I change to another directory - it doesn't work!
13 matches
Mail list logo
