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

Usage instructions out-of-date #818

Closed
alethiophile opened this issue Jun 15, 2016 · 9 comments
Closed

Usage instructions out-of-date #818

alethiophile opened this issue Jun 15, 2016 · 9 comments

Comments

@alethiophile
Copy link

Various usage instructions and examples under using/filesystem are now apparently out of date. For instance: |merge %desk [~planet-name %desk] now gives nest-fail, and only functions with |merge %desk /~planet-name/desk=; |sync %desk ~planet-name fails, requiring instead |sync %desk ~planet-name %desk (docs state the remote desk is optional if the same as the local desk); |cp /path1 /path2 %init fails, requiring no merge strategy argument.

@galenwp
Copy link
Contributor

galenwp commented Jun 15, 2016

This is a good catch. Would you be up for submitting a PR?

@ohAitch
Copy link
Contributor

ohAitch commented Jun 15, 2016

I don't know about "out of date", none of those sound compatible with any
version of the generators I've ever seen. Definitely broken regardless.

On Wednesday, 15 June 2016, Tom Hunt notifications@github.com wrote:

Various usage instructions and examples under using/filesystem are now
apparently out of date. For instance: |merge %desk [~planet-name %desk]
now gives nest-fail, and only functions with |merge %desk
/~planet-name/desk=; |sync %desk ~planet-name fails, requiring instead |sync
%desk ~planet-name %desk (docs state the remote desk is optional if the
same as the local desk); |cp /path1 /path2 %init fails, requiring no
merge strategy argument.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/docs/issues/42, or mute the thread
https://github.com/notifications/unsubscribe/ABxXhl_ZKL7Rao986gOjHq2gEaho_eKDks5qMCoegaJpZM4I2jXo
.

@alethiophile
Copy link
Author

I could make a PR with examples of the invocations that have worked for me. I don't know enough about the underlying concepts to really correct the descriptions. (For instance, what exactly is a 'beak'? Docs say a cell [~planet-name %desk] qualifies, but that doesn't work. I don't know what's correct.)

@galenwp
Copy link
Contributor

galenwp commented Jun 15, 2016

Hm. Fair. To be clear, you're referring to: http://urbit.org/docs/using/filesystem/ ? I think @ohAitch will handle this.

@ohAitch
Copy link
Contributor

ohAitch commented Jun 15, 2016

On it. A beak is definitely neither a ship-desk cell nor
/~doznec/home/2/web/md(which has a subpath)

On Wednesday, 15 June 2016, Galen Wolfe-Pauly notifications@github.com
wrote:

Hm. Fair. To be clear, you're referring to:
http://urbit.org/docs/using/filesystem/ ? I think @ohAitch
https://github.com/ohAitch will handle this.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/urbit/docs/issues/42#issuecomment-226260334, or mute
the thread
https://github.com/notifications/unsubscribe/ABxXhpAgdExXw6SgGZT8rLXv_4IynyaXks5qMDbSgaJpZM4I2jXo
.

@galenwp
Copy link
Contributor

galenwp commented Jun 22, 2016

@ohAitch should we merge your branch?

@ohAitch
Copy link
Contributor

ohAitch commented Jun 22, 2016

Yup, when I made the PR I thought docs also had "master == deploy" semantics

@galenwp
Copy link
Contributor

galenwp commented Jun 22, 2016

Well, it looks like the PR didn't get closed for a few minor issues. You're free to close it when it's ready, of course.

And yeah: master gets deployed periodically.

@ohAitch
Copy link
Contributor

ohAitch commented Jun 22, 2016

Ah right, the ship vs urbit thing. I'll put it on my list

@drbeefsupreme drbeefsupreme transferred this issue from urbit/docs Aug 24, 2021
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

No branches or pull requests

3 participants