From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Masatake YAMATO Newsgroups: gmane.emacs.devel Subject: Re: Eldoc mode Date: Mon, 13 Feb 2006 16:05:16 +0900 (JST) Message-ID: <20060213.160516.218238842.jet@gyve.org> References: <20060208.133048.156717595.jet@gyve.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1139814405 8087 80.91.229.2 (13 Feb 2006 07:06:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 13 Feb 2006 07:06:45 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 13 08:06:42 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F8XnF-0002NJ-B6 for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2006 08:06:42 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F8XnE-0002Ks-LD for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2006 02:06:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F8XmT-0002At-Ib for emacs-devel@gnu.org; Mon, 13 Feb 2006 02:05:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F8XmR-0002A6-Gd for emacs-devel@gnu.org; Mon, 13 Feb 2006 02:05:53 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F8XmR-00029x-C9 for emacs-devel@gnu.org; Mon, 13 Feb 2006 02:05:51 -0500 Original-Received: from [66.187.233.31] (helo=mx1.redhat.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F8Xqh-0004Vq-Ht; Mon, 13 Feb 2006 02:10:15 -0500 Original-Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k1D75dmI016282; Mon, 13 Feb 2006 02:05:39 -0500 Original-Received: from pobox.tokyo.redhat.com (pobox.tokyo.redhat.com [172.16.33.225]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k1D75a118864; Mon, 13 Feb 2006 02:05:37 -0500 Original-Received: from localhost (gls07.tokyo.redhat.com [172.16.32.104]) by pobox.tokyo.redhat.com (8.12.8/8.12.8) with ESMTP id k1D75WP2000864; Mon, 13 Feb 2006 16:05:33 +0900 Original-To: rms@gnu.org In-Reply-To: X-Mailer: Mew version 4.2.53 on Emacs 22.0.51 / Mule 5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:50453 Archived-At: > No. I don't use eshell. However, AFAIK, Eshell accepts both > shell command line and Emacs lisp code. Here is the example: > > I did not know that. Could you possibly update the doc string of > eshell? > > Anyway, that clears up the question of what Eldoc mode does > in Eshell. I've look at the Eshell's code. Then I found that Eshell uses Eldoc only for getting the document string of a function. Eshell doesn't use Eldoc for displaying documentation in real time. So there is nothing to add to the document string. If what I wrote here is not clear enough, do M-x find-function eshell-exec-lisp It may be obvious. Masatake YAMATO