Fix rscope-find-cscope-process for dired buffers

Dired buffers don't have associated filename, so each time
'rscope-find-cscope-process is executed from a dired buffer, a new
cscope process is created.

This patch uses default-directory instead of filename of a buffer to
find its associated cscope-process

Signed-off-by: Sylvain Chouleur <sylvain.chouleur@gmail.com>
Avoid multiple cscope process for one true path

Use absolute path for rscope buffer to avoid having two processes for ~/
and /home/$USERNAME paths

Signed-off-by: Sylvain Chouleur <sylvain.chouleur@gmail.com>
Fix non killed process in rscope-init

When calling multiple times rscope-init for the same directory, some
processes were not (and so never) killed.

'get-process function take a process name as argument, not a buffer
name. Use 'get-buffer-process instead.

Signed-off-by: Sylvain Chouleur <sylvain.chouleur@gmail.com>
Merge pull request #1 from schouleu/dev

Bug fixes & improvements on cscope process handling and cscope files handling.