Githawk: Understanding relative paths

[Huddie]

When I updated our Readme I switched [setup guide](Setup.md)to [setup guide](full url) because in GitHawk clicking the setup guide link would direct you to Githubs 404 page not found error.

This seems to be a problem with GitHawk and relative paths. It should be aware that the user tapped a link and that the link is not a url and then should try pulling up the file at that path.

One thing I’m not sure about is why GitHawk opened GitHub at all when the link was just “Setup.md”, so maybe it does understand relative paths but there’s a different error somewhere

_{Sent with GitHawk}

[rnystrom]

There’s a bug somewhere already tracking this: #2256 I think

_{Sent with GitHawk}

[rnystrom]

Yup same issue

_{Sent with GitHawk}

[Huddie]

@rnystrom These issues are slightly different. Do you want to track them together?

One is Readme header one is finding local files via their relative paths.

_{Sent with GitHawk}