Ph. Marek wrote, On 01/06/07 01:45:
But the default is wrong:
        $ fsvs st
        .mC.    100 ./bin/bash
        .mC.    200 ./etc/X11/xorg.conf

This is a bit ugly; it should only show the files below the current path.
This I'm fixing.
That is good news.

The other question that arises - where I'd need some feedback - is:


* How should the path be shown? *
\===============================/

<snip>
- "./xorg.conf", or "xorg.conf" - relative to commandline argument
  Providing a path relative to the commandline argument that references it
  is the way many utilities (including svn) work.
Probably my preference.
  Drawback: displaying something like
    ../../somewhere/../whereisit/../a_here/path/stumble/file.txt
  is not nice.
Not nice... but expected if you try something like "fsvs st ../../somewhere/../whereisit/../a_here/path/stumble/"

I think consistency with other cmd behaviour is important...
  - Should a "./" be included or not? Wouldn't be needed, but shows that
    they're only valid in *this* directory.
The "find" cmd behaviour seems to me the way to go:

$ pwd
/usr/src/fsvs-1.1.4

$ find
.
./CHANGES
./.svn
./.svn/prop-base
./.svn/props
./.svn/entries
<snip>


$ find $PWD
/usr/src/fsvs-1.1.4
/usr/src/fsvs-1.1.4/CHANGES
/usr/src/fsvs-1.1.4/.svn
/usr/src/fsvs-1.1.4/.svn/prop-base
/usr/src/fsvs-1.1.4/.svn/props
/usr/src/fsvs-1.1.4/.svn/entries
<snip>

$ cd src
$ find ../
../
../CHANGES
../.svn
../.svn/prop-base
../.svn/props
../.svn/entries

<snip>
But that just leaves more questions to answer ...
- Should ignore patterns be taken relative to the current subdirectory of
  the wc root, so that
    $ fsvs ignore './*.txt'
  is really
    $ ( cd $WCROOT ; fsvs ignore './$OLD_WC/*.txt' )
Or should ignore normally work as now, with a new "local-ignore"
  command?
hmmm.... Something like that?

$ find .
./a/1.txt
./a/2.txt
./a/3.jpg
./b/4.txt
./b/5.txt
./b/6.jpg

$ fsvs local-ignore './*.txt'
$ cd ./a
$ fsvs st
N...  3.jpg
$ cd ../b
$ fsvs st
N...  6.jpg
$ fsvs st ../a
N... ../a/1.txt
N... ../a/2.txt
N... ../a/3.jpg
- How about displaying paths in diff? Deriving the paths from the
  arguments makes a lot of sense, as the diff output might need them.
"A la" find / diff...

But... why not give the choice between...

- Relative to cmd (default)         fsvs st ./       ->  ./
- Absolute "WC root" fsvs st -p ./ -> ./cur/subdir/of/wc - Absolute "File system root" fsvs st -pp ./ -> /path/to/my/wc/cur/subdir/of/wc

So every need could be fulfilled...

Ben.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to