sorry for the typos in the previous email…
I’m really tired….

night…
mimmo

> On 14 Jan 2016, at 00:58, Mimmo Cosenza <[email protected]> wrote:
> 
> 
>> On 14 Jan 2016, at 00:27, Marc Boschma <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Funny I didn't see the tutorial as a github project per sae. I must admit I 
>> was following the tutorial but mapping it to my own project rather than 
>> blindly checking out each tutorial git repo as that tends to increase the 
>> learning, at least for me :)
> 
> Hi Marc,
> you di right: follow the tutorial by coding yourself. I prepared a branch for 
> each tutorial for more reasons:
> 
> 1. to allow the learner (and my self) to not get cracy when something does 
> not work (generally speaking it could be a typo or very subtle differences)
> 
> 2. to start any new tutorial from a sound base (the branch of the previous 
> tutorial)
> 
> At the beginning of a new tutorial n, you can start from a sound code base by 
> using the original branch of the tutorial n - 1, as I suggested in the 
> preamble of each tutorial, like so
> 
> Preamble
> 
> If you want to start working from the end of the previous tutorial 
> <https://github.com/magomimmo/modern-cljs/blob/master/doc/second-edition/tutorial-01.md>,
>  assuming you have git <https://git-scm.com/> installed, do as follows:
> 
> git clone https://github.com/magomimmo/modern-cljs.git 
> <https://github.com/magomimmo/modern-cljs.git>
> cd modern-cljs
> git checkout se-tutorial-01
> This clones the tutorial repo and starts you at the end of the first tutorial.
> 
> NOTE 1: the se- prefix means "second edition".
> 
> 
>> 
>> The end result was that there was some funny unicode character in 
>> build.boot. Probably a cut and paste error…
> 
> yep. most of the time these are the kind of issues I received in the past 
> (first edition), and doing as I said above saved me and the learners as well 
> from a lot of pain and waste of time. 
> 
> The only problem I have with this approach is the time it takes to update 
> each branch when new dependencies used in the project get released. I’m still 
> to understand what could be the quickest approch. Suggestions are very 
> welcome :-)
> 
> Good Night (here is 1.00 am)….
> 
> mimmo
> 
> 
> 
>> 
>> Regards,
>> 
>> Marc
>> 
>> -- 
>> Note that posts from new members are moderated - please be patient with your 
>> first post.
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "ClojureScript" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] 
>> <mailto:[email protected]>.
>> To post to this group, send email to [email protected] 
>> <mailto:[email protected]>.
>> Visit this group at https://groups.google.com/group/clojurescript 
>> <https://groups.google.com/group/clojurescript>.
> 

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/clojurescript.

Reply via email to