[Pharo-dev] Github and Pharo

kilon alios kilon.alios at gmail.com
Mon Nov 4 06:11:39 EST 2013

yeap filetree did the trick here. However it does not allow to browse
through the git commits as gitfiletree does, the only commit available is
the last commit.

I took a look at CommandShell and friends and they all look pretty much
very broken. For example in workspace I executed [ CommandShellTranscript
open.] and trying "ls" or "dir" it creates an error because it add C path
inside pharo subdirectories. Dont know if this is normal behavior.

I am coding in macos and ubuntu , but mostly on macos so for me this is not
a big deal. I am using Git Bash and SmartGit and I am very happy with both
so its no big loss for me.


SmartGit works great on windows, macos and linux. A very elegant

On Mon, Nov 4, 2013 at 12:34 PM, phil at highoctane.be <phil at highoctane.be>wrote:

> I guess that's why I used filetree:// and not gitfiletree:// along with
> the git client to do the CLI commits and pushes on Windows (one can use
> GitBash for example, or MobaXterm Git plugin http://mobaxterm.mobatek.net/>
> http://mobaxterm.mobatek.net/plugins.html > Git + Curl +Emacs [for you
> Gutenberg people, but Pdflatex is missing]).
> Additional benefit of MobaXterm on Windows: it has curl, wget etc, so
> Zeroconf scripts work easily.
> <rant>
> Now, I am more and more leaning towards having a debian VM into which I
> can do all the development. That's the kind of system production ends up on
> anyway. Debian 6 for me, as 7 requires to go into Multiarch + 32 bits libs
> which is not on by default and is a headache to get right. I had a hard
> time getting Pharo to run on Debian 7. And when faced with a given default
> server box, it was worse as there was no way to add the packages. This
> excluded Pharo while Rails/PHP people ran happily. :-(
> </rant>
> Phil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131104/15c9fcd2/attachment-0002.html>

More information about the Pharo-dev mailing list