On Fri, Dec 6, 2019 at 17:31 ToddAndMargo via perl6-users <perl6-users@perl.org> wrote: > > On 2019-12-06 04:19, Tom Browder wrote: > > Todd, arguing via email is almost guaranteed to be fruitless. You need > > to learn to use Github and make pull requests (PRs) for the EXACT > > changes you think should be made to the docs. ... > Hi Tom, > What makes you think I do not know how to use > the bug reporting system?
Todd, a Pull Request is NOT a bug report. YOU get a Github account, and YOU fork the Raku docs repository and YOU either make changes on your Github fork via a browser or, better, clone your fork onto your favorite local host and make desired changes there. Then, when you are satisfied, you commit your changes, push them to your Github account, and then submit a Pull Request which lets a member either approve your changes or suggest something else. I wish you could get over your aversion to reading what we have in the docs. For example, one of the first things you should learned, a long time ago was about the REPL which you just found about today. The REPL is mentioned in several places, one place a person new to the language wold be looking: On the home page (raku.org), select the "Download" menu tab on the top row. In the right column, in the second pane entitled "Introductory Material", select the "Raku Guide" In the "Table of Contents" in the left column, select "1.4, Running Raku Code" Granted, it isn't shouted out, but if you had looked around the various pages you would have found it. Also, if you would find an IRC client and join channel #raku, you could ask questions AND try out code online while people are watching. I realize we all don't search for things or learn them the same way, but goodness knows the folks who have been helping you on this mailing list have shown great patience in the face of a lot of criticism without a lot of constructive help from you in return. Best regards, -Tom
