On 11/29/21 14:06, Bob Proulx wrote:
mv calls it SOURCE and DEST. cp calls it SOURCE and DEST. Perhaps ln
should also call it SOURCE and DEST too for consistency?
That's what ln did long ago, but that wording was deemed too confusing.
Here's where we changed it to use something more like the
> I don't observe this problem with the latest development version of
> coreutils. Here's how I tried to reproduce the problem on macOS 11.3.1 20E241:
>
> % touch /tmp/
> % src/mv /tmp/ /tmp/
>
> and it worked OK.
macOS is different in that /tmp isn’t actually on a tmpfs filesyste
On 11/29/21 16:50, Sudhip Nashi via GNU coreutils Bug Reports wrote:
It appears that in coreutils 9.0 and greater, the mv command is broken on
non-APFS filesystems on macOS. For example, on Apple tmpfs, it fails whenever
moving a file with ENOTSUPP.
I don't observe this problem with the late
Hello,
It appears that in coreutils 9.0 and greater, the mv command is broken on
non-APFS filesystems on macOS. For example, on Apple tmpfs, it fails whenever
moving a file with ENOTSUPP. It works fine on APFS filesystems (which is the
primary macOS filesystem), however, so I assume it slipped
Bob Proulx wrote:
> With symbolic links the symlink contains a string. The string could
> be pretty much anything.
The more I think about it the more I think it should say CONTENT
rather than either TARGET or SOURCE. Because it is actually setting
the content of the symbolic link. Therefore tha
On November 27, 2021 9:41:07 AM GMT+01:00, Paul Eggert
wrote:
>On 11/25/21 15:10, Warren Parad wrote:
>> except mv(1) and cp(1) are both "FROM" and then "TO", but ln is backwards
>> from thi, it is "TO" then "FROM"
>
>No, ln is exactly like mv and cp here: the source is the first argument,
>and
Ulf Zibis wrote:
> Currently we have:
> List-Post: GNU coreutils Bug Reports
>
> When using "reply list" to answer to a comment of bug 12345 in a email client
> such as Thunderbird, my reply is sent to bug-coreutils@gnu.org, but it should
> be sent to 12...@debbugs.gnu.org
>
> So I think, we s
Chris Elvidge wrote:
> Paul Eggert wrote:
> > Ulf Zibis wrote:
> > > I think, for beginners it would be less confusing, if the most
> > > simple form would be the first.
> >
> > Unfortunately the simple form "ln TARGET" is quite rarely used, so
> > putting it first is likely to confuse beginners e
On 29/11/2021 07:07 pm, Paul Eggert wrote:
On 11/29/21 02:34, Ulf Zibis wrote:
I think, for beginners it would be less confusing, if the most simple
form would be the first.
Unfortunately the simple form "ln TARGET" is quite rarely used, so
putting it first is likely to confuse beginners even
On 11/29/21 02:34, Ulf Zibis wrote:
I think, for beginners it would be less confusing, if the most simple
form would be the first.
Unfortunately the simple form "ln TARGET" is quite rarely used, so
putting it first is likely to confuse beginners even more than what we
have already. Come to th
Hi,
Currently we have:
List-Post: GNU coreutils Bug Reports
When using "reply list" to answer to a comment of bug 12345 in a email client
such as Thunderbird, my reply is sent to bug-coreutils@gnu.org, but it should be sent to
12...@debbugs.gnu.org
So I think, we should have:
List-Post: GNU
Am 27.11.21 um 09:41 schrieb Paul Eggert:
On 11/25/21 15:10, Warren Parad wrote:
except mv(1) and cp(1) are both "FROM" and then "TO", but ln is backwards
from thi, it is "TO" then "FROM"
No, ln is exactly like mv and cp here: the source is the first argument, and
the destination is the sec
On 29/11/2021 01:07 am, Bob Proulx wrote:
Warren Parad wrote:
except mv(1) and cp(1) are both "FROM" and then "TO", but ln is backwards
from thi, it is "TO" then "FROM", the least the command could do is put
these in the correct order.
But that is not correct. The order for ln is the same
13 matches
Mail list logo
