From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.help Subject: Re: Elisp: Setting column position? Date: Tue, 20 Jan 2009 11:40:42 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <86wscpg9k5.fsf@lifelogs.com> References: <86mydrhxpk.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1232473353 15098 80.91.229.12 (20 Jan 2009 17:42:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 20 Jan 2009 17:42:33 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 20 18:43:45 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LPKdU-0005l8-MM for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Jan 2009 18:43:36 +0100 Original-Received: from localhost ([127.0.0.1]:48907 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPKcD-0006sJ-Jb for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Jan 2009 12:42:17 -0500 Original-Path: news.stanford.edu!headwall.stanford.edu!news.glorb.com!newsfeed00.sul.t-online.de!t-online.de!news.albasani.net!not-for-mail Original-Newsgroups: comp.emacs,gnu.emacs.help Original-Followup-To: comp.emacs Original-Lines: 37 Original-X-Trace: news.albasani.net Jbh45KYf6N3UweU8n3XX/fPgR00p+SgsR7PzsulhbJR/FkR5IxvvoB+6lKTNsVKHoCh97D4Fbob5wVFhY7wRMWuQfH2UsHfQt60PmG2JE8Ka+3ASHP39gR3TaZcsxhRn Original-X-Complaints-To: abuse@albasani.net Original-NNTP-Posting-Date: Tue, 20 Jan 2009 17:39:39 +0000 (UTC) X-User-ID: kDXemtysvImC29yryVNVOhOgrqoOYPeyiw7mdhQVlds= X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Cancel-Lock: sha1:f5b+z4zGz2VHMmFJ+iv1VLrQtD4= sha1:o/h62WSvtG7qNSjQE/S5jAB8ZdI= User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) X-NNTP-Posting-Host: 19LkmG/vXejm4+fwYm8X8Y2QjJKyQspVtG+ldGqM8g0= Original-Xref: news.stanford.edu comp.emacs:97679 gnu.emacs.help:166184 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:61506 Archived-At: On Sat, 17 Jan 2009 10:23:23 -0800 (PST) Xah Lee wrote: XL> i vaguely recall also wanted move-to-column, but i recall thought it XL> didn't exist. Yes of course i knew apropos, and elisp-index-search and XL> reasonably familiar with elisp and its manual. XL> I think it would be great that in the function's in-line doc, it would XL> say related functions. For example, if one looks up on goto-line, then XL> at the bottom it might say: XL> See also: goto-char, move-to-column, ... On Sat, 17 Jan 2009 10:29:45 -0800 (PST) Xah Lee wrote: XL> Note that listing related functions in a function's doc is in many XL> programing manuals. e.g Mathematica, MS's JScript, PHP ... they are XL> quite useful. Because for those not expert yet of a lang (which is XL> majority), often they do not know similar functions or do not know if XL> there's manual section that list such, and often are confused about XL> the differences of many functions that seems the same .... I agree this would be useful. It's best done with tags IMO, rather than explicitly listing the related functions. For example, motion commands should be tagged "motion" and then every command with that tag can automatically list every motion command. The key is that the extra work is in classification, not in tediously listing every command's peers. Tags I could use: motion, file, coding-system, menu, buffer, process Each package should probably tag its commands with the package name. Short tags are not always descriptive enough, but long tags get unpleasantly verbose so the real art is in balancing between the two. Anything more hierarchical than tags is painful to manage in the long run. Ted