README, git clone with parallel jobs #686
Conversation
| @@ -20,7 +20,7 @@ directory ``~/pelican-themes``, but yours could be different. Clone the | |||
|
|
|||
| .. code-block:: sh | |||
|
|
|||
| git clone --recursive https://github.com/getpelican/pelican-themes ~/pelican-themes | |||
| git clone --jobs 8 --recursive https://github.com/getpelican/pelican-themes ~/pelican-themes | |||
There was a problem hiding this comment.
The whole document has a bit of a "POSIX-or-die" slant that might not be the most helpful, but in keeping with that motif, wouldn't it be more adaptive to set --jobs "$(nproc)" here rather than supply a fixed value when we have no a priori knowledge about their environment?
As far as the POSIX-or-die part, I think that can be resolved pretty well by prepending bash -c to what's already there (since we can reasonably assume that however someone got Git installed on Windows it includes a Bash interpreter in PATH) and replacing ~ with $HOME in the target path argument (PowerShell Core aliases that to $Env:UserProfile I'm pretty sure, no idea about CMD.exe though), but my familiarly with both the Windows Command Interpreter and Windows PowerShell makes me wish someone with more experience in that domain would spot check my thinking on that part.
No description provided.