-
Notifications
You must be signed in to change notification settings - Fork 72
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
gaps in doco #21
Comments
On Tue, Jan 14, 2014 at 1:02 PM, Ryan Davis notifications@github.com wrote:
I don't have a Mac handy but something like this should get you going: $ cd objects |
Ryan, can I suggest you subscribe to the mailing list at self-interest@yahoogroups.com? Email self-interest-subscribe@yahoogroups.com to subscribe. There is an archive at forum.selflanguage.org That way more people will see your questions. |
On Jan 13, 2014, at 16:13, Russell Allen notifications@github.com wrote:
I totally can, but I'm still gonna bug you here. :D Too much stuff gets dropped on the floor when support is done via mailing lists. I've been following self for.. well... prolly since my first OOPSLA. I want you guys to succeed and I'm really happy you guys got this release out. It's a big improvement, but needs to be more approachable by newbs. So I'm going at this like one. |
OK. Thanks to your help I got the VM built. Now what?
It seems to me that there's a huge gap in the doco regarding actually using self, esp out of the build directory.
I can't go from building the VM to running self via the doco. Additionally, I have no idea how to use the instructions on how to build the world. Here is some of my confusion illustrated:
The first one wants to use X11 for some reason. The second doesn't. Why are they different but named the same?
Running the second one:
and if I run the actual binary:
or:
This one was done because I overlooked the prose and went straight to the instructions. Having step 1 include
cd objects
would have helped.Even more confusing:
1900+ files are executable in the checkout. Why are source code and jpgs marked executable in the checkout? This just obscures discovery.
The text was updated successfully, but these errors were encountered: