From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: Re: Documentation for ido-mode is not very enlightening Date: Mon, 25 Feb 2008 22:49:35 +0100 Message-ID: <47C337EF.3050208@gmx.at> References: <20080224190416.AFBCA5D513@indeed> <47C2CC51.8050802@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1203976221 32646 80.91.229.12 (25 Feb 2008 21:50:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Feb 2008 21:50:21 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org, "Kim F. Storm" To: era eriksson Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Feb 25 22:50:46 2008 Return-path: Envelope-to: geb-bug-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 1JTlDg-0004dj-58 for geb-bug-gnu-emacs@m.gmane.org; Mon, 25 Feb 2008 22:50:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JTlDA-0002FK-9m for geb-bug-gnu-emacs@m.gmane.org; Mon, 25 Feb 2008 16:50:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JTlD6-0002FF-2w for bug-gnu-emacs@gnu.org; Mon, 25 Feb 2008 16:50:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JTlD3-0002Et-DI for bug-gnu-emacs@gnu.org; Mon, 25 Feb 2008 16:50:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JTlD3-0002El-Ag for bug-gnu-emacs@gnu.org; Mon, 25 Feb 2008 16:50:05 -0500 Original-Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1JTlD3-00050P-0J for bug-gnu-emacs@gnu.org; Mon, 25 Feb 2008 16:50:05 -0500 Original-Received: (qmail invoked by alias); 25 Feb 2008 21:50:03 -0000 Original-Received: from N805P011.adsl.highway.telekom.at (EHLO [62.47.44.139]) [62.47.44.139] by mail.gmx.net (mp054) with SMTP; 25 Feb 2008 22:50:03 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+Rak5LptuRnjLQfy5JlGHhuDejzrdRUIRnybZuvR 0R81elbjV/drUE User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:17593 Archived-At: > What's an "ido speed-up"? What are "ido versions" of the find-file functions? > If you are terminally curious, you might try it out, but you should not assume > your users have indefinite time and patience. For many users, the amount of > modes and features you could try out at one point or another is overwhelming, > and those with obscure or hard-to-find features are going to go undiscovered by > most users, and waste the time of many who try them out only to find the > features are not useful to them. > > Even just the following very brief introduction from the beginning of the > "Comments" section in the ido.el source would help a lot: > > Ido - interactive do - switches between buffers and opens files and > directories with a minimum of keystrokes. > > Like I wrote in my original report, it would be even better if the entire > comments section of the source file could be turned into documentation. It's > fairly detailed and comprehensive. Sorry, I don't use ido and don't know what it does. I fully agree with your remarks but am afraid that the Emacs development team doesn't have the necessary ressources to fill your needs. How about writing a patch giving all the details you consider essential? You could try copying the style of a minor mode you like and whose doc-string you consider adequate. You might even consider writing an Info node for this - I think Kim would agree and give you any help you need.