Proposal for adding `true` command

[exKAZUu]

There is no true command on Windows. Although some workarounds exist, I feel shx true is convenient.

[nfischer]

Thanks for the request! This is a duplicate of #105, so I'll close in favor of that issue. @exKAZUu could you provide some example use-cases on that issue?

[exKAZUu]

@nfischer Sorry for making a duplicated issue.
In my use case, I'd like to use a Windows-specific command like mklink on a cross-platform project and I'd like to use true command like mklink /d ..... || true in my npm script in order to prevent errors on non-Windows environments. I'm now using shx echo -n instead of true :)
Btw, the behavior of mklink /d and shx ln -s seems different. Is it expected? (So I need to use mklink)

[nfischer]

@exKAZUu I'm not familiar with mklink, so I'm not sure if this is a bug in our end. Could you give examples for how shx ln -s and mklink /d differ?

[exKAZUu]

@nfischer
shx ln -s creates a junction link, in contrast, mklink /d creates a symbolic link.
However, I now notice shx ln -s is better than mklink /d in our use case. Sorry.

Btw, I've investigated the link mechanism on Windows.
Just for your information, I'll explain the differences.

There are three kinds of links on Windows as follows. The third page summarizes them.
https://www.2brightsparks.com/resources/articles/NTFS-Hard-Links-Junctions-and-Symbolic-Links.pdf

Here is the current behavior of some commands.

• shx ln -s for a directory creates a junction link
• mklink /j for a directory creates a junction link
• mklink /d for a directory creates a symbolic link
• ln -s using Git for Winows for a directory copies the directory (?)

[nfischer]

@exKAZUu thanks! Yes, the junction link is intended behavior, this was merged into shelljs a long time ago (shelljs/shelljs#87 and shelljs/shelljs#104).