1 |
On Mon, Nov 01, 2010 at 01:07:34PM +0200, Alan McKinnon wrote: |
2 |
> > >> Something I have not run into before. |
3 |
> > >> |
4 |
> > >> Following a major update still in progress I find the ls command will |
5 |
> > >> not run on $HOME. |
6 |
> > >> |
7 |
> > > By the time the command hits ls itself, the shell has already expanded |
8 |
> > > the HOME variable. So it's unlikely to be the command and more something |
9 |
> > > dodgy with your shell. |
10 |
> > > |
11 |
> > > What shell are you using? |
12 |
> > > What is the output of "echo $HOME"? |
13 |
> > |
14 |
> > My shell is xterm... and was just updated to: |
15 |
> > Wed Oct 27 10:15:06 2010 >>> x11-terms/xterm-262 |
16 |
> |
17 |
> That's the terminal. |
18 |
> |
19 |
> What shell do you use/ |
20 |
> |
21 |
> > echo $HOME |
22 |
> > /home/reader |
23 |
|
24 |
Before we go further, when you said `ls' will not complete against |
25 |
$HOME, which of the following scenario did you mean? |
26 |
|
27 |
a) you typed `ls $HOME' as a user (the one I think Alan thinks you |
28 |
mean) |
29 |
b) you type `ls' while in your home directory (/home/reader) |
30 |
c) you typed `ls /home/reader' ? |
31 |
|
32 |
W |
33 |
-- |
34 |
Willie W. Wong wwong@××××××××××××××.edu |
35 |
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire |
36 |
et vice versa ~~~ I. Newton |