One can read this and install plugins and follow instructions including what is said on the comments to solve pitfalls. So far is good the only thing that bothers me now is the file navigation and correct indexing of all files in projects.

http://lenss.nl/2011/04/vim-for-a-php-developer/

Now let’s take a look at this repo here:

https://github.com/tobyS/vip

After some tests trying to clone everzet/ornicar dot files and symlink the vim and vimrc to my dot versions on my home I failed because they use macs. I wish someone could point me to similar dot files for ubuntu/linux. Anyway, I will soon leave phpstorm.

I left it: https://github.com/spf13/spf13-vim This link just settled it for me, no more looking.

On our previous post we saw how to configure a default wemux session to pair program in mirror mode. In this post we will see how to switch to rogue mode so that we can have two terminals in our ubuntu or linux machines that can monitor one on the right and one on the left. The right one will display a shared view/edit session belonging to one programmer and the left one will display a shared view/edit session belonging to the other programmer on the other end.

In order to do this we configure the wemux.conf file:

sudo pico /usr/local/etc/wemux.conf

Here we switch the flags to support rogue mode and switching to servers as described in the text in there.

As default wemux only creates one session and expect everyone to reuse this session in a single host/server. In order to create more than one session we follow the series of commands as follows:

wemux list-sessions  // list sessions
wemux -S /tmp/wemux-wemux new-session -s checarlitos // creates new session named checarlitos
wemux -S /tmp/wemux-wemux attach-session -t checarlitos // attach to a previously created session named checarlitos

Following the creation of two sessions in separate terminals we put them side to side. In one we attach to one session and in the other to the other session. That is it!

So the first thing is of course to clone the repo and start following the first manual installing instructions from the reamde at https://github.com/zolrath/wemux.
The second thing is when you realize and say “what is this thing?” or “why am I doing this?”. Basically wemux is a wrapper like cli tool sitting on top of tmux. What is tmux? tmux is a terminal multiplexer tool, it basically allows splitting your windows into several panes and hook sessions with different users. You could just use tmux alone, but why trying to show off something we don’t know about? Let’s just use wemux, wemux saves us to do some hard work on tmux or so we think. So after setting everything wemux readme says we should we are still at odds because we want to know how do I tell my friend to pair program with me? Well, the thing you want to do is to first have a way your friend can connect to you and look up the same code via ssh to your computer. Then you both can edit the same file or different files at the same time in different panes. For that you would need a bit of setup.

Third thing, you want to make sure your IP is reachable by your friend. So you “port forward” from firewall to your ip on the inside. The port to forward is 22 from your router to your computer. This can be done by opening a browser on 192.168.1.1 and configuring your router ADSL or other to forward a port. If you cannot figure out where that option is it would be good to take a look at your router manual.

Fourth thing, because your ubuntu or linux box is running a firewall you need to open up to forward that port 22. This advanced stuff can be summarized with the following command:

sudo iptables -L -n | grep ACCEPT  // this is just to see what is there
sudo iptables -A INPUT -p tcp --dport ssh -j ACCEPT  // this one is the real stuff that makes the difference

This command opened the firewall on my box for the ssh to not timeout. Now an external user, my friend can join my box. However he does not have a user account yet!

Fifth thing, now we create an (ssh) user account into my box.

~ sudo adduser mark
Adding user `mark' ...
Adding new group `mark' (1002) ...
Adding new user `mark' (1002) with group `mark' ...
Creating home directory `/home/mark' ...
Copying files from `/etc/skel' ...
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully
Changing the user information for mark
Enter the new value, or press ENTER for the default
	Full Name []: Mark
	Room Number []: 
	Work Phone []: 
	Home Phone []: 
	Other []: 
Is the information correct? [Y/n]

Sixth thing, now I run:

wemux start
wemux users
// then use your vim or pico editor to work on your files
// and also use tmux commands to split or do work with your panes

Tell your friend to ssh you using the ip you see in http://www.whatsmyip.org with his user and password and then ask him to try to attach to server or join you. His username has to be in the host_list or such. He then can pair program with you!
Now I have problems with the pair mode, it seems everytime my friend connects it goes into mirror mode. How to solve this?

Special thanks to my friend Mark Badolato.

Doing better than what I deserve by the Lord’s grace!

Click here to view the embedded video.

~ git checkout -b feature/PHPCR-42-testRefactoring
~/sites-2/cmf-sandbox/vendor/doctrine-phpcr-odm (feature/PHPCR-42-testRefactoring)

Now it is time to find the way the do tests:

At this time I already found a file that was an exception and was empty and so I asked and I was told to remove it and PR. So I did.
Then taking another watch at the tests I started asking the right questions, what, where, why and got a lot of confirmations and answers which set me familiar with the code at large.

The first move has to be easy and focused. So I take the first digested sentence that I read, namely:

Refactor the tests about mapping to have abstract base tests to assert things,
and one test for each annotation/yml/xml/php so we really test the same outcome
https://github.com/doctrine/phpcr-odm/tree/master/tests/Doctrine/Tests/ODM/PHPCR/Mapping

It seems that someone else has already done it , at least part of it. But it is ok I learned something. Now I have asked with a PR about how to proceed https://github.com/doctrine/phpcr-odm/pull/133.

In one shell:

~ mongod

In another shell:

~ mongo
// and configure the authentication

The authentication commands are located here.

The most problematic point was because I had a process `mongo` running on the background and had to kill it with su:

~ ps -ef | grep mongo
~ sudo killall mongo -s 9

Now everything is:

~ mongod --version
db version v2.0.4, pdfile version 4.5
Thu Apr  5 17:37:11 git version: sha1
~ mongo --version
MongoDB shell version: 2.0.4

I am so excited about working the right way with mongodb!

~ grep -Rin todo ./src/

Also I am trying to replicate
git branch -vv
git log –oneline base..dest | wc -l
gitk –date-order –all