From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: search files with conversion but fundamental mode, no handlers, no file-local vars Date: Fri, 21 Dec 2012 10:39:15 +0200 Message-ID: <83r4mjn6j0.fsf@gnu.org> References: <3D2A507FA3EE44909DF7CA025897BFC3@us.oracle.com> <83txrgmtof.fsf@gnu.org> <615E3EC604F94336B49A1812AC076EF8@us.oracle.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1356079177 5184 80.91.229.3 (21 Dec 2012 08:39:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Dec 2012 08:39:37 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 21 09:39:50 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tly8y-00016Q-Mz for ged-emacs-devel@m.gmane.org; Fri, 21 Dec 2012 09:39:48 +0100 Original-Received: from localhost ([::1]:54445 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tly8l-0001hD-21 for ged-emacs-devel@m.gmane.org; Fri, 21 Dec 2012 03:39:35 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:37968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tly8h-0001h8-K8 for emacs-devel@gnu.org; Fri, 21 Dec 2012 03:39:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tly8g-0006Et-4q for emacs-devel@gnu.org; Fri, 21 Dec 2012 03:39:31 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:54442) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tly8f-0006DM-TT for emacs-devel@gnu.org; Fri, 21 Dec 2012 03:39:30 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MFD00600H9JNV00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Fri, 21 Dec 2012 10:39:28 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MFD00630HDRBNA0@a-mtaout20.012.net.il>; Fri, 21 Dec 2012 10:39:28 +0200 (IST) In-reply-to: <615E3EC604F94336B49A1812AC076EF8@us.oracle.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155717 Archived-At: > From: "Drew Adams" > Cc: "'Eli Zaretskii'" , > Date: Thu, 20 Dec 2012 14:01:07 -0800 > > OK, from what you and Eli are saying, I'm starting to think that `i-f-c' might > be appropriate for my case. But I would like to see the doc for `i-f-c' spell > out specifically what it does and does not do. I don't think documenting the internals to such a degree is a good idea. It will make the doc string extremely long and tedious to read, full of details irrelevant to most Lisp programmers. Just imagine that insert-file-contents reads in the file's contents, doing TRT with what that requires, but nothing more. IOW, you get a buffer with the file's text, and that's it. > Like the doc for `mm-i-f-c' does. No, it does not. It says "like insert-file-contents, but only reads in the file." That doesn't describe much, because "like insert-file-contents" is still unexplained. And "just reads in the file" fits what insert-file-contents does, too. > And if the doc for `mm-i-f-c' is wrong about it being different in this or that > respect from `i-f-c', then it would be good to fix that doc too. I agree. The only real difference is that it disables file handlers (something that is not in its doc string, btw), which means remote files are not supported, compressed files are not decompressed, etc. -- which most applications like the one you described will actually want to have.