From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: Underscore in filenames and M-x locate Date: Fri, 04 May 2007 00:54:00 -0600 Message-ID: References: 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: sea.gmane.org 1178261686 8238 80.91.229.12 (4 May 2007 06:54:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 4 May 2007 06:54:46 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri May 04 08:54:45 2007 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 1Hjrgc-0003ch-Rn for geh-help-gnu-emacs@m.gmane.org; Fri, 04 May 2007 08:54:39 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HjrnE-0002Oc-4b for geh-help-gnu-emacs@m.gmane.org; Fri, 04 May 2007 03:01:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hjrmx-0002H7-GR for help-gnu-emacs@gnu.org; Fri, 04 May 2007 03:01:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hjrmw-0002FC-EG for help-gnu-emacs@gnu.org; Fri, 04 May 2007 03:01:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hjrmw-0002Eb-5Q for help-gnu-emacs@gnu.org; Fri, 04 May 2007 03:01:10 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HjrgJ-0006qi-Ok for help-gnu-emacs@gnu.org; Fri, 04 May 2007 02:54:20 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Hjrg8-0005OY-PU for help-gnu-emacs@gnu.org; Fri, 04 May 2007 08:54:08 +0200 Original-Received: from c-67-162-159-170.hsd1.co.comcast.net ([67.162.159.170]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 May 2007 08:54:08 +0200 Original-Received: from kevin.d.rodgers by c-67-162-159-170.hsd1.co.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 May 2007 08:54:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 42 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: c-67-162-159-170.hsd1.co.comcast.net User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) In-Reply-To: X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:43639 Archived-At: Holger Sparr wrote: > Kevin Rodgers wrote: > >> Holger Sparr wrote: >>> When using M-x locate the default pattern to use is evaluated by >>> `locate-word-at-point'. >>> >>> Why isn't the Underscore included in the expression of characters to >>> skip for a sensible default value? >> Uh, because underscore is not a _word_ constituent character? >> Still, locate-word-at-point could be changed to use \sw instead >> of [-a-zA-Z0-9.] > > Neither is [.]. Indeed, nor is [-]. >>> Possibly the expression could be customized by the user or the active >>> region could be passed as the search-string. >> You could try: >> >> (require 'locate) >> (defalias 'locate-word-at-point 'word-at-point) >> (autoload 'word-at-point "thingatpt") >> >> or: >> >> (require 'locate) >> (defalias 'locate-word-at-point >> (lambda () (symbol-name symbol-at-point))) > > Of course I can do that. But if "_" is a proper character in filenames > then why not change the default. I guess I took "word" in the name of the function too literally. But if you want to match any valid file name character, it's simpler to exclude the few invalid characters (NULL, slash, perhaps colon, etc. depending on the platform). -- Kevin Rodgers Denver, Colorado, USA