Installing ncurses-5.6 breaks mv in zsh-4.3.2-r2. Anytime you attempt to mv a file that spans another partition while using the ncurses use flag in zsh you get the following error "invalid cross-device link". This goes for any files not symlinks or hardlinks. Downgrading ncurses to 5.5-r3 or compiling zsh without ncurses use flag solves the problem. Reproducible: Always Steps to Reproduce: 1.Installing ncurses-5.6 2.Install zsh-4.3.2-r2 with ncurses useflag 3.mv a file outside it's current partition. Actual Results: invalid cross-device link Not sure why you can still move a file as long as it does not leave the current partition. You can also call /bin/mv directly and it works. I know ncurses use flag enables a menu where you can use arrow keys to select a file or directory during tab completion.
Not sure it is even ncurses now. I was interested in gathering some more info but have only gave myself a headache. I realized there was a ncurses-5.6-r1 with some new patches so i installed that and recompiled zsh against it. Died again. So I installed ncurses-5.6 dies. (Now before I reported this, i had installed 5.5-r3 to solve my problem). Well decided it was not the patches in -r1 and it has to be 5.6 . I'll go say that much at least and maybe save someone a few minutes time. Now to install 5.3 and have a working mv again. Blows up in my face, can't get it to work at all again. I also realized that i have ncurses-5.6 and the latest zsh on my servers working just fine without this error. Again though if i call mv with the full path I do not have the problem for example. mv notes /storage would return invalid cross-device link but /bin/mv notes /storage would work just fine. I can't seem to get things working again even if i compile without ncurses support so my original idea of it being ncurses with what i noticed tonight is pretty much bs from what i see. Still not sure what causes it.
Src/Modules/files.c with line numbers included. 175 /* bin_ln actually does three related jobs: hard linking, symbolic * 176 * linking, and renaming. If called as mv it renames, otherwise * 177 * it looks at the -s option. If hard linking, it will refuse to * 178 * attempt linking to a directory unless the -d option is given. */ 179 180 /**/ Then we have: 703 BUILTIN("mv", 0, bin_ln, 2, -1, BIN_MV, "fi", NULL), Which is pretty much a internal hardlink to mv. Which is the cause of my headaches. This also explains why when i Call /bin/mv directly things are just dandy. I have this changed to the following. BUILTIN("zsh-gay-mv", 0, bin_ln, 2, -1, BIN_MV, "fi", NULL), for my local fix. I have not had time to contact them about this, i really do not know what in there internal mv causes the error but as far as i see it can be blamed on that. I apparently have to join a mailing list to contact them about bugs which is making me want to stab someone. They are also doing this for a lot of other commands that you will see in the area of line 703. Find this really stupid and working on moving to bash and dealing with the (in my opinion) worse tab completion. Just want to explain what i have found. Maybe I'm dead wrong. This was in zsh 4.3.2-r2 tarball. Have not looked into other versions and I do not know what it appears to randomly fail. Someone with much more C experience will need to tell me that.
Could you confirm this bug in zsh-4.3.4-r1 ? I'd like to mark zsh-4.3.4-r1 as stable, as zsh-4.3.6 is coming, zsh-4.3.2 will certainly be removed if zsh-4.3.4 does not have this bug and is stable enough.
zsh-4.3.4-r1 is now stable, can you try to reproduce your bug as I am not able to reproduce it. Otherwise the bug could perhaps be closed ?
Please reopen if the problem still exists in later versions. Thanks.
