From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: jargon translation up-front in doc (was: Menu suggestion) Date: 30 Apr 2004 01:36:23 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1083276071 29763 80.91.224.253 (29 Apr 2004 22:01:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 29 Apr 2004 22:01:11 +0000 (UTC) Cc: Kevin Rodgers , eliz@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Apr 30 00:01:00 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BJJaW-0004AO-00 for ; Fri, 30 Apr 2004 00:01:00 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BJJaV-0005r7-00 for ; Fri, 30 Apr 2004 00:00:59 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BJJUU-0002zP-Ic for emacs-devel@quimby.gnus.org; Thu, 29 Apr 2004 17:54:46 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BJJUM-0002yD-Ak for emacs-devel@gnu.org; Thu, 29 Apr 2004 17:54:38 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BJJTq-0002nd-7C for emacs-devel@gnu.org; Thu, 29 Apr 2004 17:54:37 -0400 Original-Received: from [195.41.46.237] (helo=pfepc.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BJJRv-0002PA-OQ; Thu, 29 Apr 2004 17:52:07 -0400 Original-Received: from kfs-l.imdomain.dk.cua.dk (0x503e2644.bynxx3.adsl-dhcp.tele.dk [80.62.38.68]) by pfepc.post.tele.dk (Postfix) with SMTP id 5F213262D02; Thu, 29 Apr 2004 23:36:39 +0200 (CEST) Original-To: "Drew Adams" In-Reply-To: Original-Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:22381 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:22381 "Drew Adams" writes: > That might be good (though excessive hyperlinking can be obfuscating, so > occurrences should *not* all become hyperlinks automatically). If we > provided such hyperlinking, programmers should have a way to explicitly, > selectively apply it (just as they can selectively expand command names in > doc strings to provide key bindings: \\[foobar]). > > However, that does *not* address the main issue I raised. (Eli also missed > it, so I must not be making myself clear.) > > Explaining our jargon is one thing. Come across "yank" somewhere, don't know > what it means, click it, get the definition - great. > > What's missing is the set of common terms as user **entry points**. We > should *mention* those terms, and then provide a bridge to our similar > terms. Just defining our own terms doesn't provide this learning bridge. I think a very brief "emacs terms" section at the start of the tutorial would be ok. > > A user should be able to do `M-x command-apropos paste' and come up with the > *few, common* commands that involve pasting. Did you actually try C-h a paste RET ? (clue: apropos already knows that paste is synonymous with yank) -- Kim F. Storm http://www.cua.dk