Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #50

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Update README.md #50

wants to merge 3 commits into from

Conversation

VAllens
Copy link

@VAllens VAllens commented Sep 20, 2017

Fixed start.sh bug.

Fixed start.sh bug.
@pecigonzalo
Copy link
Owner

pecigonzalo commented Sep 20, 2017

Fixes: #49
Relates to: #43

@pecigonzalo pecigonzalo mentioned this pull request Sep 20, 2017
@VAllens
Copy link
Author

VAllens commented Sep 20, 2017

Ok, this is good.
Thanks

@VAllens
Copy link
Author

VAllens commented Sep 21, 2017

Can you merge this PR? Thank you

@pecigonzalo
Copy link
Owner

Ill merge it once I had time to test it. You can freely change your script, as its not part of the Go compiled code.

@VAllens
Copy link
Author

VAllens commented Sep 22, 2017

I see. Thank you. :) 👍

Copy link
Owner

@pecigonzalo pecigonzalo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we sort the comments im ready to merge this.
Im a bit confused now tho, is /mnt/c the path for WSL and /c for Git Bash or the other way around?

@@ -54,7 +55,7 @@ add it to your $PATH.
```none
#!/bin/bash

export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"
   export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be causing a break in the codeblock. Could you verify?

Enter & Run `C:\Program Files\Docker Toolbox\start.sh` in `bash` window.

2. Change `export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"` to `export PATH="$PATH:/c/Program Files (x86)/VMware/VMware Workstation"` in `start.sh`.
  Find `Docker Quickstart Terminal` on the desktop and double-click to run(need installed `Git Bash`).
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(requires Git Bash)

could be better there, wdyt?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The better reason for WSL is that it is more convenient and quicker.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, i meant change the text to

(requires Git Bash)

instead of

need installed

@@ -141,6 +142,22 @@ add it to your $PATH.

## Usage

Usage `WSL (Windows Subsystem for Linux)` can be perfect to run this scripts, otherwise you can only modify the script after using `Git Bash` to run.
So you'd better install and use `WSL` to run scripts.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section is not that clear, maybe we can rephrase?

WSL (Windows Subsystem for Linux)is a perfect option to run this script otherwise, you can modify the scripts as outlined below to run with otherbashtools likeGit BashorMSYS2`

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can write two script files for WSL (Windows Subsystem for Linux) and Git Bash, or try to write a script file that is compatible with both.
This is WSL:
image
This is Git Bash:
image
There are some differences between the two.
The differences I have known are: path problems.
In the WSL: /mnt/c/xxxxx.
In the Git Bash: /c/xxxxx.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I know both, the main difference for this is just the mount path, that is all. It might be better to script the detection of the environment than to have 2 scripts.

2. Change `export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"` to `export PATH="$PATH:/c/Program Files (x86)/VMware/VMware Workstation"` in `start.sh`.
  Find `Docker Quickstart Terminal` on the desktop and double-click to run(need installed `Git Bash`).

3. Change `export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"` to `export PATH="$PATH:/c/Program Files (x86)/VMware/VMware Workstation"` in `C:\Program Files\Docker Toolbox\start.sh`.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both for 2. and 3. could we break the export [...] commands to multiple lines to make it more readable?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont really see the difference between 2. and 3. could you explain?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Usage WSL:
    Run directly using your script file.
  2. Usage Git Bash:
    After modifying the script file, run Docker Quickstart Terminal on the desktop directly.
    OR
    After modifying the script file, run Git Bash directly and Enter C:\Program Files\Docker Toolbox\start.sh in the Git Bash window.

Copy link
Author

@VAllens VAllens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okey

@@ -141,6 +142,22 @@ add it to your $PATH.

## Usage

Usage `WSL (Windows Subsystem for Linux)` can be perfect to run this scripts, otherwise you can only modify the script after using `Git Bash` to run.
So you'd better install and use `WSL` to run scripts.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can write two script files for WSL (Windows Subsystem for Linux) and Git Bash, or try to write a script file that is compatible with both.
This is WSL:
image
This is Git Bash:
image
There are some differences between the two.
The differences I have known are: path problems.
In the WSL: /mnt/c/xxxxx.
In the Git Bash: /c/xxxxx.

Enter & Run `C:\Program Files\Docker Toolbox\start.sh` in `bash` window.

2. Change `export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"` to `export PATH="$PATH:/c/Program Files (x86)/VMware/VMware Workstation"` in `start.sh`.
  Find `Docker Quickstart Terminal` on the desktop and double-click to run(need installed `Git Bash`).
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The better reason for WSL is that it is more convenient and quicker.

2. Change `export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"` to `export PATH="$PATH:/c/Program Files (x86)/VMware/VMware Workstation"` in `start.sh`.
  Find `Docker Quickstart Terminal` on the desktop and double-click to run(need installed `Git Bash`).

3. Change `export PATH="$PATH:/mnt/c/Program Files (x86)/VMware/VMware Workstation"` to `export PATH="$PATH:/c/Program Files (x86)/VMware/VMware Workstation"` in `C:\Program Files\Docker Toolbox\start.sh`.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Usage WSL:
    Run directly using your script file.
  2. Usage Git Bash:
    After modifying the script file, run Docker Quickstart Terminal on the desktop directly.
    OR
    After modifying the script file, run Git Bash directly and Enter C:\Program Files\Docker Toolbox\start.sh in the Git Bash window.

@Karrq
Copy link

Karrq commented Jul 18, 2019

If you add the WSL as requirement it locks out anybody not in Windows 10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants