On 2019/08/02 23:10, Assaf Gordon wrote:
So when I look at the system call on linux for rename:
oldpath can specify a directory. In this case, newpath must
either not
exist, or it must specify an empty directory.
(complying with POSIX_C
Hello,
On Fri, Aug 02, 2019 at 10:47:18PM -0700, L A Walsh wrote:
> It's not a wish list that 'mv' doesn't work as documented.
The "wishlist" refers to the topic:
You are asking to add new funtionality to 'mv'.
That is a "wishlist" item.
(answering out of order:)
> > On 2019-08-02 9:56 p.m., L
It's not a wish list that 'mv' doesn't work as documented.
On 2019/08/02 22:45, Assaf Gordon wrote:
> severity 36901 wishlist
> retitle 36901 mv: merge directories where target already exists
> stop
>
> Hello,
>
> (for context: this is a new topic, diverged at https://bugs.gnu.org/36831#38 )
>
severity 36901 wishlist
retitle 36901 mv: merge directories where target already exists
stop
Hello,
(for context: this is a new topic, diverged at https://bugs.gnu.org/36831#38 )
For completeness, quoting your second message ( from
https://bugs.gnu.org/36831#50 ):
On 2019-08-02 9:56 p.m., L A
Hello,
On 2019-08-02 9:56 p.m., L A Walsh wrote:
On 2019/08/02 19:47, Assaf Gordon wrote:
Can new merging features be added to 'mv'? yes.
But it seems to me these would be better suited for 'higher level'
programs (e.g. a GUI file manager).
---
But neither the person who posted the ori
On 2019/08/02 19:47, Assaf Gordon wrote:
> Can new merging features be added to 'mv'? yes.
> But it seems to me these would be better suited for 'higher level'
> programs (e.g. a GUI file manager).
---
But neither the person who posted the original bug on this
nor I are using a GUI, we a
Reposting this, since I realize that fixing the target-exists cases
with a helpful algorithm could change or eliminate many cases
where where now the user gets an error instead.
On 2019/07/28 23:28, Assaf Gordon wrote:
>
>
> $ mkdir A B B/A
> $ touch A/bar B/A/foo
> $ mv A B
> m
Hello,
On Fri, Aug 02, 2019 at 02:41:31AM -0700, L A Walsh wrote:
> On 2019/07/28 23:28, Assaf Gordon wrote:
> >
> >
> > $ mkdir A B B/A
> > $ touch A/bar B/A/foo
> > $ mv A B
> > mv: cannot move 'A' to 'B/A': Directory not empty
> >
> > And the reason (as you've found out) is that
* src/dircolors: Add .webp for the WebP image format
---
src/dircolors.hin | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/dircolors.hin b/src/dircolors.hin
index 3aa445bfa..9aa5b07da 100644
--- a/src/dircolors.hin
+++ b/src/dircolors.hin
@@ -158,6 +158,7 @@ EXEC 01;32
.m2v 01;35
.mkv 01
On 2019/08/01 16:37, Paul Eggert wrote:
> Ulrich Mueller wrote:
>
>> Except for the surrogates
>> U+D800...U+DFFF, it looks like an arbitrary restriction
>>
>
> It's not entirely arbitrary. Because of the restriction, coreutils printf
> doesn't have to worry about what this command should
On 2019/07/28 23:28, Assaf Gordon wrote:
>
>
> $ mkdir A B B/A
> $ touch A/bar B/A/foo
> $ mv A B
> mv: cannot move 'A' to 'B/A': Directory not empty
>
> And the reason (as you've found out) is that the target directory 'B/A'
> is not empty (has the 'foo' file in it).
> Had this bee
> On Fri, 02 Aug 2019, Paul Eggert wrote:
> It's not entirely arbitrary. Because of the restriction, coreutils
> printf doesn't have to worry about what this command should do:
> printf '\u0025d\n' 1 2
Seems quite obvious, it should do the same as these commands:
printf '\045d\n' 1 2
12 matches
Mail list logo
