user-guide: improve Windows POSIX/terminal tips

[LucasErlacher]

For windows users is necessary past to the same line the command when has \ in the end of line.

For example:
dvc get https://github.com/iterative/dataset-registry \ tutorial/ver/data.zip

to

dvc get https://github.com/iterative/dataset-registry tutorial\ver\data.zip

It's also necessary use \ in the path on windows.

[shcheklein]

that's why it's better to keep CLI example as close to one line as possible

Unfortunately, don't see an easy way out of this. Switching modes is too expensive too support at this stage. Open to any other reasonable suggestions.

[dashohoxha]

Unfortunately, don't see an easy way out of this. Switching modes is too expensive too support at this stage. Open to any other reasonable suggestions.

I wonder what doc engine are they using in this tutorial, and how they make it possible to display command snippets with tabs ("Linux/Mac" and "Windows"):
https://dagshub.com/docs/pipeline/#featurization-or-pre-processing

It even seems like it is possible to convert automatically a Linux example to a Windows example.

[jorgeorpinel]

@LucasErlacher did you notice our doc on Windows caveats? We recommend POSIX-like terminals in there: https://dvc.org/doc/user-guide/running-dvc-on-windows

Perhaps we should link to this doc more so people are able to find our recommendations easily?

[shcheklein]

@jorgeorpinel agreed! the first link I would into install/windows.

[shcheklein]

@dashohoxha they are using MkDocs . I doubt that it can automatically translate windows <-> linux. Would be great if you can take a look and see what takes for an editor to supports this, how does it look in their markdown (or what do they use as a format?)

[dashohoxha]

how does it look in their markdown (or what do they use as a format?)

Unfortunately I could not find the code of their website/docs. DAGsHub does not seem to be open source (although they offer free service for open source projects).

However this discussion has some info about it: https://stackoverflow.com/questions/37606292/how-to-create-tabbed-code-blocks-in-mkdocs-or-sphinx

[shcheklein]

@dashohoxha some suggestions look reasonable. We can't probably use direct MkDocs analog - consequent blocks with different language specifications, since we have a single language usually - dvc or usage, but we can come up with something similar or use something similar to this https://github.com/apache/spark/blob/master/docs/quick-start.md. I wonder how many code snippets are affected by this?

let's create a ticker for the engine to add support for this.

[jorgeorpinel]

Per this conversation I just noticed is that the recommendations in https://dvc.org/doc/user-guide/running-dvc-on-windows may not really be super helpful:

• We should double check what POSX features other than -- and forward slash / Git Bash and Anaconda Prompt actually support (for example \ line continuation isn't available on Anaconda Powershell Prompt [miniconda]) before recommending them broadly.
• People may not want to use WSL because apparently it can't access GPUs for training.

Should we remove/de-emphasize/re-think these Windows terminal tips?

[shcheklein]

@jorgeorpinel git bash is pretty bad by itself ... let's do some research and recommend one best configuration.

[shcheklein]

@jorgeorpinel this is the good recommendation I would test and if it supports all the features we need would recommend it - https://cmder.net/ + git bash + conda

[jorgeorpinel]

recommend it - https://cmder.net/ + git bash + conda

Added in 5c07821 (as part of #915).

By "+ git bash + conda" you mean to not remove those suggestions, but to recommend full Cmder over those alternatives, right? (Feel fee to review in the PR, marked to close this issue.)