Don't think i would recommend supporting backslash as folder delimiter as this introduces inconsistencies between the shells.
It's also the escape character in many linux shells so that might get a bit confusing and problematic when people share their examples (already the case for special characters of course, but less likely to happen).

I would personally prefer the root folder to be the default is it is now and explicitly denote relative paths with ../ (parent folder) and ./ (current folder) prefixes.
When used outside of a repository this should cause an error.
When used with a different --repo it should assume that to be a fork (or have a similar folder structure) and thus try to open the relative path.

Don't think i would recommend supporting backslash as folder delimiter as this introduces inconsistencies between the shells.
It's also the escape character in many linux shells so that might get a bit confusing and problematic when people share their examples (already the case for special characters of course, but less likely to happen).

Thanks for all of the feedback! I included both / and \ to make sure whatever is natural to the user / operating system is available. I take your point that examples might be confusing but ideally someone on linux should feel more inclined to use /, much like windows users would most likely use \. Could be wrong though

I would personally prefer the root folder to be the default is it is now and explicitly denote relative paths with ../ (parent folder) and ./ (current folder) prefixes.

Interesting, I also like this idea a lot but I would like another opinion. I'm not sure if this would make this feature too complex or not

When used outside of a repository this should cause an error.

gh browse should be taking care of this already, unless you mean starting in a repository, then using too many ../ until you are outside of the repo. In which case this will just open up to the main page of the repo

When used with a different --repo it should assume that to be a fork (or have a similar folder structure) and thus try to open the relative path.

I still need to test the --repo flag, but I see why you think it should be default "absolute" because of this. Assuming you are deep in one repository and want to look at another repository that isn't similar, this may cause issues.

@vilmibm will have better ideas, but just wanted to mention that you should probably take a look at using path/filepath in the Go standard library to help handle cross-platform file path issues. The first time I used this package, it was kind of life changing.

There's this Stack Overflow answer too.

@bchadwic,

Note: gh browse still opens up to the root of the repository to avoid confusion, I would like input on this decision. If a user wants to open the folder they are in, in the browser, they can type out gh browse #

To open the folder I'm in, gh browse . would seem more intuitive. This would be the GitHub equivalent of open . on MacOS or start . on Windows.

Just bumping this, I revised the pr description at the top to show the current functionality. Looking forward to feedback on the new approach.