From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xah Lee Newsgroups: gmane.emacs.help Subject: Re: Elisp: Setting column position? Date: Tue, 20 Jan 2009 09:46:09 -0800 (PST) Organization: http://groups.google.com Message-ID: <188347aa-2032-4735-b68b-ee682784c338@i20g2000prf.googlegroups.com> References: <86mydrhxpk.fsf@lifelogs.com> <86wscpg9k5.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1232572495 6781 80.91.229.12 (21 Jan 2009 21:14:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2009 21:14:55 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 21 22:16:07 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 1LPkQh-0000NV-KC for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Jan 2009 22:16:07 +0100 Original-Received: from localhost ([127.0.0.1]:42936 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPkPQ-00032Q-7T for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Jan 2009 16:14:48 -0500 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!i20g2000prf.googlegroups.com!not-for-mail Original-Newsgroups: comp.emacs,gnu.emacs.help Original-Lines: 54 Original-NNTP-Posting-Host: 24.6.175.142 Original-X-Trace: posting.google.com 1232473569 8934 127.0.0.1 (20 Jan 2009 17:46:09 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 20 Jan 2009 17:46:09 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: i20g2000prf.googlegroups.com; posting-host=24.6.175.142; posting-account=bRPKjQoAAACxZsR8_VPXCX27T2YcsyMA User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1, gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu comp.emacs:97680 gnu.emacs.help:166185 X-Mailman-Approved-At: Wed, 21 Jan 2009 16:13:52 -0500 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:61539 Archived-At: On Jan 20, 9:40=C2=A0am, Ted Zlatanov wrote: > 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 an= d > XL> reasonably familiar with elisp and its manual. > > XL> I think it would be great that in the function's in-line doc, it woul= d > XL> say related functions. For example, if one looks up on goto-line, the= n > 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. =C2=A0It's best done with tags IMO, rather = than > explicitly listing the related functions. =C2=A0For example, motion comma= nds > should be tagged "motion" and then every command with that tag can > automatically list every motion command. =C2=A0The 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 can you send this suggestion to the emacs dev? :) Xah =E2=88=91 http://xahlee.org/ =E2=98=84