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.

Sign up for GitHub

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

Jump to bottom

Inference for URIs #56

Closed
hyperrealgopher opened this issue Apr 10, 2020 · 2 comments
Closed

Inference for URIs #56

hyperrealgopher opened this issue Apr 10, 2020 · 2 comments
Labels
bug Something isn't working enhancement New feature or request
Milestone
v0.2.0

Comments

@hyperrealgopher
Copy link
Collaborator

hyperrealgopher commented Apr 10, 2020 •
edited
Loading

This is both a feature and a bug request.

Goto: interpret what the type is; open more than just menus.

Goto currently only supports opening menus. I would like it so you can open text and other kinds of URIs. This ties into another issue about interpreting filetypes without menus telling telling us what to expect.

At least should handle errors for when the user tries to open a URI that isn't a Gopher menu.
@hyperrealgopher hyperrealgopher added bug Something isn't working enhancement New feature or request labels Apr 10, 2020
@hyperrealgopher hyperrealgopher added this to the v0.1.0 milestone Apr 10, 2020
@hyperrealgopher hyperrealgopher mentioned this issue Apr 10, 2020
Closed
@hyperrealgopher hyperrealgopher modified the milestones: v0.1.0, v1.0.0 Apr 10, 2020
@hyperrealgopher
Copy link
Collaborator Author

Related: #29

@hyperrealgopher hyperrealgopher changed the title Goto: interpret what the type is; open more than just menus Inference for URIs May 4, 2020
@hyperrealgopher hyperrealgopher mentioned this issue May 4, 2020
Closed
@hyperrealgopher hyperrealgopher modified the milestones: v1.0.0, v0.2.0 May 4, 2020
@hyperrealgopher
Copy link
Collaborator Author

Well in the gopher protocol you can tell what to expect when you follow a link in a gophermap. But if you just want to infer a type from a URI you basically have to read x bytes and make a guess, or maybe it's a binary you can try to read the header of, or you see via the file extension. I can expedite a type guesser ASAP, but I'm not aware of any other way it could work.

@hyperrealgopher hyperrealgopher mentioned this issue May 4, 2020
Closed
hyperrealgopher pushed a commit that referenced this issue May 4, 2020
@someodd
higher order writeAllBytes function
9ea11d0 
Done to prepare for v0.2.0, specifically #56: inference
for URIs, which is very useful for GotoMode, since GotoMode
and opening the first URI via CLI just assumes `MenuMode.`
hyperrealgopher pushed a commit that referenced this issue May 4, 2020
@someodd
higher order writeAllBytes function
fceeda2 
Done to prepare for v0.2.0, specifically #56: inference
for URIs, which is very useful for GotoMode, since GotoMode
and opening the first URI via CLI just assumes `MenuMode.`
hyperrealgopher pushed a commit that referenced this issue May 4, 2020
@someodd
higher order writeAllBytes function
8ef10cc 
Done to prepare for v0.2.0, specifically #56: inference
for URIs, which is very useful for GotoMode, since GotoMode
and opening the first URI via CLI just assumes `MenuMode.`
someodd added a commit that referenced this issue Aug 19, 2022
@someodd
higher order writeAllBytes function
ec90a6f 
Done to prepare for v0.2.0, specifically #56: inference
for URIs, which is very useful for GotoMode, since GotoMode
and opening the first URI via CLI just assumes `MenuMode.`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
v0.2.0
Development

No branches or pull requests
1 participant
@hyperrealgopher