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

all: port to Plan 9 #28

Closed
wants to merge 1 commit into from
Closed

all: port to Plan 9 #28

wants to merge 1 commit into from

Conversation

fhs
Copy link
Contributor

@fhs fhs commented Oct 9, 2018

Depends on PR #26 for consistent behavior of ReadAt.

Helps rjkroege/edwood#115

@ddevault
Copy link

Tested this on 9front, worked great after fixing the conflicts.

Depends on PR 9fans#26 for consistent behavior of ReadAt.

Helps rjkroege/edwood#115
@fhs
Copy link
Contributor Author

fhs commented Sep 19, 2019

@ddevault Thanks for testing. I've rebased.

@ddevault
Copy link

Thanks! I'm working on another patch which will add a factotum module as well.

@fhs
Copy link
Contributor Author

fhs commented Sep 20, 2019

@ddevault I worked on a factotum package a long time ago: bitbucket.org/fhs/go-plan9-auth/auth. It hasn't gotten much use over the years. Feel free to make use of it (if it's useful).

I should probably move the package from mercurial to git/github, since mercurial is going away in bitbucket. But then I'd rather have a factotum package inside 9fans.net/go/....

@ddevault
Copy link

Excellent! I'll pull it into 9fans/go. And if you're looking for a new Mercurial host, my own services are available.

@floren
Copy link

floren commented Oct 22, 2020

Registering a +1 in that this would be really useful for me.

@nvkv
Copy link

nvkv commented Nov 30, 2020

Is there any chance to get this merged? It would be really useful.

@rsc
Copy link
Contributor

rsc commented Apr 17, 2021

Apologies, but at least in this form, a port to Plan 9 is out of scope for this package. In particular I hope to kill off the entire devdraw RPC usage entirely, instead connecting directly to the host graphics and generally simplifying programs built against this API. That would invalidate much of the code being added to draw here, since the "draw protocol" will not exist anymore.

The situation for plan9.Client is similarly awkward: it seems wrong to have a mode where that code falls back to file system access.

I'm willing to make small Plan 9-related changes, but I don't want to have to maintain wholly separate implementations of the libraries just for Plan 9.

For now it seems best to maintain a fork of this package for use on Plan 9. Again, sorry. I appreciate the sad irony.

@rsc
Copy link
Contributor

rsc commented Apr 6, 2024

@fhs and I have been working to move github.com/fhs/acme-lsp to 9fans.net/acme-lsp, hosted in https://github.com/9fans/acme-lsp, and as part of that I have merged fhs/9fans-go's plan9 branch into the main 9fans.net/go branch. The fork should no longer be necessary.

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.

5 participants