This is a discussion on 2 files have same dir & name ?! within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> ls Ne* -l gives: -rw-r--r-- 1 root root 235 Jan 31 02:28 NewsLst -rw-r--r-- 1 root root 607 Jan ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| ls Ne* -l gives: -rw-r--r-- 1 root root 235 Jan 31 02:28 NewsLst -rw-r--r-- 1 root root 607 Jan 31 06:16 NewsLst The simplest explanation for me is that one's has a trailing invisible char[s]. How would I investigate this further ? == Chris Glur. |
| |||
| no-top-post writes: > ls Ne* -l gives: > -rw-r--r-- 1 root root 235 Jan 31 02:28 NewsLst > -rw-r--r-- 1 root root 607 Jan 31 06:16 NewsLst > > The simplest explanation for me is that one's has a trailing > invisible char[s]. > How would I investigate this further ? for f in *; do echo "'${f}'" done Would show any spaces or funny chars. Cheers, Phil -- "Solutions are not the answer." - Richard Nixon, former U.S. President |
| |||
| no-top-post wrote: > ls Ne* -l gives: > -rw-r--r-- 1 root root 235 Jan 31 02:28 NewsLst > -rw-r--r-- 1 root root 607 Jan 31 06:16 NewsLst > > The simplest explanation for me is that one's has a trailing > invisible char[s]. > How would I investigate this further ? > > == Chris Glur. I think "cat * | od -c | more" was one way we used to do this.. |
| |||
| no-top-post wrote: > ls Ne* -l gives: > -rw-r--r-- 1 root root 235 Jan 31 02:28 NewsLst > -rw-r--r-- 1 root root 607 Jan 31 06:16 NewsLst > > The simplest explanation for me is that one's has a trailing > invisible char[s]. > How would I investigate this further ? > > == Chris Glur. Opps.. not cat *.. |
| |||
| * no-top-post | ls Ne* -l gives: | -rw-r--r-- 1 root root 235 Jan 31 02:28 NewsLst | -rw-r--r-- 1 root root 607 Jan 31 06:16 NewsLst | | The simplest explanation for me is that one's has a trailing | invisible char[s]. | How would I investigate this further ? ls | od -a R' |
| |||
| On Tue, 30 Jan 2007 16:19:01 +0000, nntp@shellarchive.co.uk wrote: >> The simplest explanation for me is that one's has a trailing >> invisible char[s]. >> How would I investigate this further ? > > for f in *; do > echo "'${f}'" > done ls -Q [mozes@bladswede ii] $ ls -Q "Moose" "Moose " -- The Biscuit Appreciation Society : www.biscuit.org.uk Experimental ARM Linux distribution: www.armedslack.org |
| ||||
| no-top-post wrote : > The simplest explanation for me is that one's has a trailing > invisible char[s]. If you have copy/pasted from an xterm then I can see the last file has a trailing whitespace. > How would I investigate this further ? > ls -1 Ne* | hexdump -C Ask eight slackers.... -- Thomas O. This area is designed to become quite warm during normal operation. |