> For the complete documentation index, see [llms.txt](https://zh.chanyuan8.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zh.chanyuan8.org/xue-feng-wen-ji-chan-yuan-pian/ba-dao-you-dang-zuo-ren-sheng-lu-shang-de-wan-ban.md).

# 把导游当作人生路上的玩伴

所有言过其实的赞美都让人不舒服，有禅院草把我说成是上帝，这是对上帝的亵渎，也是对我的陷害。

有禅院草把我看成神，这叫神神叨叨，我明明是一个有肉体的人，怎能称为神？这种对我的拔高不仅不利于生命禅院的建设事业，更对人类有害，说不定哪天人类接受了生命禅院理念，就把我奉为神明了，这多可怕！

有禅院草称呼我为大佛，听着也让我很不舒服，因为我不仅不是大佛，连菩萨也不是。

有禅院草称呼我为伟人，说实话，我才不当伟人呢！我只是实事求是，实话实说，既没有伟人的胸襟，也没有伟人的雄心和品质。

许多禅院草一直称呼我为师父，我三番五次地说过，我只是导游，不当师父，因为我不具备当师父的德行。

有人曾经说我像泼妇，反复寻思，我确实在某些方面像泼妇，这种称呼我接受。

有人说我是大骗子，这让我哭笑不得，对此，我也不辩解，让事实和历史去回答吧！

总之，任何对我固定的称谓我都觉得不符合实情，当然称我为导游是最恰当的，我希望大家把我当作人生路上的玩伴，玩，是我最拿手的技能，我是最能玩的人，不是玩物玩人，而是玩游戏，我觉得一切都是游戏，人生除了玩游戏，再没有什么重要的事，不会玩的人生太无聊，人不会玩，活一辈子太不值得了。

天下任何事，在我眼里性里，都是游戏，所以，我是一个玩乐的人，所以，你若把我当作你最好的人生玩伴，就是对我最好的赞美和尊敬。

2011-5-15


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zh.chanyuan8.org/xue-feng-wen-ji-chan-yuan-pian/ba-dao-you-dang-zuo-ren-sheng-lu-shang-de-wan-ban.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.