From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: FFAP Date: Fri, 06 Nov 2009 10:18:32 -0500 Message-ID: References: <3b31caf90911051613w80af4cu61352a29ce5dcd77@mail.gmail.com> <87vdhoe73d.fsf@mail.jurta.org> <87y6mkb6qr.fsf@mail.jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1257520751 11615 80.91.229.12 (6 Nov 2009 15:19:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 6 Nov 2009 15:19:11 +0000 (UTC) Cc: Edward O'Connor , emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 06 16:19:04 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N6Qad-00064U-Ko for ged-emacs-devel@m.gmane.org; Fri, 06 Nov 2009 16:19:03 +0100 Original-Received: from localhost ([127.0.0.1]:47016 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6Qac-0007em-UW for ged-emacs-devel@m.gmane.org; Fri, 06 Nov 2009 10:19:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N6QaG-0007UC-KU for emacs-devel@gnu.org; Fri, 06 Nov 2009 10:18:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6QaB-0007SD-E8 for emacs-devel@gnu.org; Fri, 06 Nov 2009 10:18:39 -0500 Original-Received: from [199.232.76.173] (port=35614 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6QaB-0007S8-7E for emacs-devel@gnu.org; Fri, 06 Nov 2009 10:18:35 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:25119 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N6QaA-0003YZ-HL for emacs-devel@gnu.org; Fri, 06 Nov 2009 10:18:34 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EADPN80pMCqkr/2dsb2JhbACBTtwfhD0EiQg X-IronPort-AV: E=Sophos;i="4.44,694,1249272000"; d="scan'208";a="48806960" Original-Received: from 76-10-169-43.dsl.teksavvy.com (HELO pastel.home) ([76.10.169.43]) by ironport2-out.pppoe.ca with ESMTP; 06 Nov 2009 10:18:32 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 441EF7F0F; Fri, 6 Nov 2009 10:18:32 -0500 (EST) In-Reply-To: <87y6mkb6qr.fsf@mail.jurta.org> (Juri Linkov's message of "Fri, 06 Nov 2009 06:45:45 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116686 Archived-At: > I had an idea for a long time how to do such an integration, but > not implemented it yet because I currently don't see how to do this > without loading the whole ffap.el by default. Perhaps we should > rewrite most of the ffap functionality and simplify it. By "integration" I mostly mean the functionality, not necessarily the code. But if it means preloading ffap.el, that's not necessarily a bad thing, although I think that by integrating it, we can make it a lot simpler, so I expect that a complete rewrite will be preferable (especially since we probably wouldn't provide every single last detail of ffap's functionality). > The idea is to put a file/URL from the text around the point into > the minibuffer's default values list. So typing `C-x C-f M-n' > on a file name will bring in it from the current buffer into the > minibuffer. I thought about it but M-n is already used in some file prompts for other purposes, so the user would then have to hit M-n more than once to get the file-at-point, which makes it cumbersome. I think a dedicated keybinding would be better. BTW, another possibility is to do what complete.el does: use a special file name (complete.el uses "<>" but we could choose something else, like " ") to mean file-at-point. I think it's a worse solution (both because it may collide with a real file name, and more importantly because it makes it impossible/difficult to edit the file-at-point), but I throw it out, for completeness's sake. Stefan