From d004f28df4afb83d1a195c3ff57f6675ccd0f0ac Mon Sep 17 00:00:00 2001
From: Andy Stewart <lazycat.manatee@gmail.com>
Date: Wed, 11 Dec 2019 00:39:29 +0800
Subject: [PATCH] Update HACKING.md

---
 docs/HACKING.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/HACKING.md b/docs/HACKING.md
index ea8be82..c87c1f2 100644
--- a/docs/HACKING.md
+++ b/docs/HACKING.md
@@ -236,6 +236,23 @@ self.emacs_var_dict["eaf-camera-save-path"]
 
 Above is an example of ```eaf-camera-save-path```, you can customize any variable on elisp side actually, don't need modify python code to customize EAF application!
 
+### Call Python method and store function result to temp Elisp variable
+
+In EAF buffer have interface ```get_bookmark```
+
+```Python
+def get_bookmark(self):
+    return ""
+```
+
+At Elisp side, we can use below code call Python method and store function result to Elisp variable:
+
+```Elisp
+(setq temp-var (eaf-call "call_function" eaf--buffer-id "get_bookmark"))
+```
+
+Once you understand principle, you can define your own interface function in core/buffer.py , then use ```call_function``` method on Elisp side to fetch Python function result, don't need define temp elisp variable everywhere.
+
 ### Update settings at Python side along with customize option change at Elisp side.
 Once you change customize option by ```eaf-setq```, everytime EAF buffer is created, AppBuffer's interface ```update_settings``` will execute.