From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: The minibuffer vs. Dialog Boxes (Re: Making XEmacs be more up-to-date) Date: Sun, 21 Apr 2002 09:48:26 +0300 (IDT) Sender: emacs-devel-admin@gnu.org Message-ID: References: NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1019368284 2364 127.0.0.1 (21 Apr 2002 05:51:24 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 21 Apr 2002 05:51:24 +0000 (UTC) Cc: rms@gnu.org, xemacs-design@xemacs.org, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16zAFw-0000c1-00 for ; Sun, 21 Apr 2002 07:51:24 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 16zAG1-0005AG-00 for ; Sun, 21 Apr 2002 07:51:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zAFi-0002yH-00; Sun, 21 Apr 2002 01:51:10 -0400 Original-Received: from is.elta.co.il ([199.203.121.2]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zAEa-0002tx-00; Sun, 21 Apr 2002 01:50:00 -0400 Original-Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id JAA03291; Sun, 21 Apr 2002 09:48:26 +0300 (IDT) X-Sender: eliz@is Original-To: Brady Montz In-Reply-To: Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:2911 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:2911 On 20 Apr 2002, Brady Montz wrote: > For example, I often find functions by searching the lisp code for > certain strings, or following the chain of functions/variables from > a likely starting point, or searching through the info pages, > searching through keymaps. Basically, grepping and reverse > engineering. Could be a lot more automated. Would be nice to have that, but it's a non-trivial project, I think. The rules for such reverse engineering are most of the time fuzzy, so it's not easy to program. > 2. Once I've found a reference to it (an info page, the doc string, > the customize gunk), I want better cross referencing. > > We're not too far off here. A "see also" section to the doc strings > could be nice. Are you familiar with the cross-references in GNU Emacs doc strings? (I'm not sure if that feature exists in XEmacs.) They are displayed in a different face, and you can click on them (or type RET with point on them) to follow the reference. These references are used for related variables and functions and for showing the function's source, for example. > But, the interface for this cross referencing is > cumbersome. I can fire up info, describe variable, customize in > their own seperate ways, but it would be nicer for a beginner to > presented with a single buffer with everything you might want to > read or modify or use regarding that item. I'm afraid ``everything'' would take so much space that users will be unwilling to wade through all that stuff...