I don't think you guys should invent new eye-catching strings.
Aren't there already standard ways to show what is going on under the
hood? Let's see, sh -x uses + and ++... strace uses... maybe just use '# '
comments.
On 05/18/2017 08:09 AM, Bernhard Voelker wrote:
the '->' style is a great eye-catcher in such
listings.
We could address that issue by outputting an eyecatching string at the
start of each -v output line. E.g.,:
+ src/mv -v /tmp/mv-test .
:;:; mkdir './mv-test'
:;:; cp '/tmp/mv-test/fi
I'm fine with whatever you guys come up with, just don't
R> - Leave the output like it was initially.
else I'll just be back here five years later after forgetting the whole episode.
On 05/18/2017 04:41 PM, Paul Eggert wrote:
> $ src/mv -v /tmp/mv-test .
> mkdir './mv-test'
> cp '/tmp/mv-test/file' './mv-test/file'
> rm '/tmp/mv-test/file'
> rmdir '/tmp/mv-test'
>
> $ src/mv -v mv-test mv-test-2
> mv 'mv-test' 'mv-test-2'
I think this may be confusing in longer shell output wi
On 05/18/2017 09:41 AM, Paul Eggert wrote:
>
> If we're changing the format, I suggest having the output be useful as
> input to the shell, like this:
>
> $ src/mv -v /tmp/mv-test .
> mkdir './mv-test'
If we do this, you'd probably want to use:
mkdir -- './mv-test'
at least when the destinati
Hi,
> Am 18.05.2017 um 16:41 schrieb Paul Eggert :
>
> On 05/17/2017 06:11 PM, Pádraig Brady wrote:
>> created directory './mv-test'
>> copied '/tmp/mv-test/file' -> './mv-test/file'
>> removed '/tmp/mv-test/file'
>> removed directory '/tmp/mv-test'
>>
>> $ src/mv -v mv-test mv-test-2
>> renamed
On 05/17/2017 06:11 PM, Pádraig Brady wrote:
created directory './mv-test'
copied '/tmp/mv-test/file' -> './mv-test/file'
removed '/tmp/mv-test/file'
removed directory '/tmp/mv-test'
$ src/mv -v mv-test mv-test-2
renamed 'mv-test' -> 'mv-test-2'
If we're changing the format, I suggest having t
On 05/18/2017 03:11 AM, Pádraig Brady wrote:
> Subject: [PATCH] mv: distinguish copy and rename operations with --verbose
+1 looks nice, thanks.
Have a nice day,
Berny
On 17/05/17 22:46, 積丹尼 Dan Jacobson wrote:
> PB> So this is working across file systems
> Yes.
>>> '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs'
> This says to me "I, the mv command, have just moved A to B.
>
> PB> create dir /tmp/programs
> If that (create B) is what it i
On 05/17/2017 01:55 PM, Pádraig Brady wrote:
there is nothing ambiguous here
Although it's not ambiguous it is a bit confusing for non-experts, and
part of the point of -v is to help non-experts.
PB> So this is working across file systems
Yes.
>> '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs'
This says to me "I, the mv command, have just moved A to B.
PB> create dir /tmp/programs
If that (create B) is what it is doing in that step, then it should not
mention the unr
On 17/05/17 21:19, 積丹尼 Dan Jacobson wrote:
> I do
> mv -v /home/jidanni/jidanni.org/location/grow/programs /tmp
So this is working across file systems
> and see
> '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs'
create dir /tmp/programs
> '/home/jidanni/jidanni.org/locatio
12 matches
Mail list logo
