Show images from /usr/share/doc/elpa-epc/HEADarchive/debian/0.1.1-5master

This patch changes images location to /usr/share/doc/elpa-epc/.


Gbp-Pq: Name fix-documentation.diff

1 files changed, 12 insertions, 12 deletions

diff --git a/readme.md b/readme.md
index 27cd0d4..6d04096 100644
--- a/readme.md
+++ b/readme.md
@@ -35,12 +35,12 @@ Here is a client code.
 
 (deferred:$
   (epc:call-deferred epc 'echo '(10))
-  (deferred:nextc it 
+  (deferred:nextc it
     (lambda (x) (message "Return : %S" x))))
 
 (deferred:$
   (epc:call-deferred epc 'add '(10 40))
-  (deferred:nextc it 
+  (deferred:nextc it
     (lambda (x) (message "Return : %S" x))))
 
 ;; calling synchronously
@@ -61,12 +61,12 @@ use RPC::EPC::Service;
 
 sub echo_test {
     my $methods = {
-    
+
         'echo' => [sub {
             my $args = shift;
             return $args;
         },"args","just echo back arguments."],
-        
+
         'add' => sub {
             my $args_ref = shift;
             my ($a,$b) = @$args_ref;
@@ -86,7 +86,7 @@ Here is the equivalent server code in emacs lisp.
 (require 'epcs)
 
 (let ((connect-function
-       (lambda (mngr) 
+       (lambda (mngr)
          (epc:define-method mngr 'echo (lambda (&rest x) x) "args" "just echo back arguments.")
          (epc:define-method mngr 'add '+ "args" "add argument numbers.")
          )) server-process)
@@ -133,11 +133,11 @@ Let we define the words *server* and *client*. *Server* is a process which opens
 
 This diagram shows the API usage and the relation of processes.
 
-![API Overview](img/Overview.png)
+![API Overview](/usr/share/doc/elpa-epc/Overview.png)
 
 ### Object Serialization
 
-All values which are transferred as arguments and return values between processes, are encoded into the S-expression text format. 
+All values which are transferred as arguments and return values between processes, are encoded into the S-expression text format.
 
 Simple list structure and some primitive types can be transferred. Complicated objects, such as buffer objects, can not be serialized. The EPC stack doesn't provide transparent remote object service, that is ORB.
 
@@ -279,7 +279,7 @@ Here is a sample code for the EPC server:
 (require 'epcs)
 
 (let ((connect-function
-       (lambda (mngr) 
+       (lambda (mngr)
          (epc:define-method mngr 'echo (lambda (x) x) "args" "just echo back arguments.")
          (epc:define-method mngr 'add '+ "args" "add argument numbers.")
          )) server-process)
@@ -317,7 +317,7 @@ The EPC has a management interface for the EPC connections. Users can check the
 
 Executing `M-x epc:controller`, one can display the list of current established connections.
 
-![Current Connections](img/mm-conns.png)
+![Current Connections](/usr/share/doc/elpa-epc/mm-conns.png)
 
 This table shows following information:
 
@@ -346,7 +346,7 @@ One can use following key-bind:
 
 Displaying a method list, one can inspect the methods which are defined by the remote process.
 
-![Remote Method List](img/mm-methods.png)
+![Remote Method List](/usr/share/doc/elpa-epc/mm-methods.png)
 
 This table shows following information:
 
@@ -433,11 +433,11 @@ The EPC is developed on `deferred.el` and `concurrent.el`. The library `deferred
 
 The EPC user should learn asynchronous programing on `deferred.el`. The components of `concurrent.el` are just internally used at `epc.el`.
 
-![EPC Stack](img/epc-stack.png)
+![EPC Stack](/usr/share/doc/elpa-epc/epc-stack.png)
 
 Here is a diagram for the `epc.el` architecture, which diagram may be helpful for code reading of `epc.el`.
 
-![Internal Architecture](img/epc-internal.png)
+![Internal Architecture](/usr/share/doc/elpa-epc/epc-internal.png)
 
 ## Other Stacks