GNU bug report logs - #12824
24.2.50; Strange default string brought by M-n after `C-x C-v'

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 12824 in the body.
You can then email your comments to 12824 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.2.50; Strange default string brought by M-n after `C-x C-v'
Date: Wed, 7 Nov 2012 17:17:07 +0100

Recipe from "emacs -Q":

  C-x b h i <RET> / * h e l l o C-x C-v M-n

I observe that `M-n' writes in the minibuffer a default argument "c:/*hello".

If I repeat the experiment changing "/*hello" with, for example,
"hello" or "/*hello/", no default argument is brought by `M-n'.

Is this a bug no?  If not, what is the rule here for getting a default argument?

TIA.


In GNU Emacs 24.2.50.1 (i386-mingw-nt6.1.7601)
 of 2012-10-29 on DANI-PC
Bzr revision: 110729 dancol <at> dancol.org-20121029172429-z2gio8grvel4rzrv
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
 -I../../libs/libxpm-3.5.8/include -I../../libs/libxpm-3.5.8/src
 -I../../libs/libpng-1.4.10 -I../../libs/zlib-1.2.6
 -I../../libs/giflib-4.1.4-1/include -I../../libs/jpeg-6b-4/include
 -I../../libs/tiff-3.8.2-1/include
 -I../../libs/libxml2-2.7.8-w32-bin/include/libxml2
 -I../../libs/gnutls-3.0.16/include
 -I../../libs/libiconv-1.14-2-mingw32-dev/include'

Important settings:
  value of $LANG: ESN
  locale-coding-system: cp1252
  default enable-multibyte-characters: t

-- 
Dani Moncayo

Message #8 received at 12824 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: 12824 <at> debbugs.gnu.org
Subject: Re: bug#12824: 24.2.50;
	Strange default string brought by M-n after `C-x C-v'
Date: Thu, 08 Nov 2012 02:43:06 -0500

Dani Moncayo wrote:

> Is this a bug no? If not, what is the rule here for getting a default
> argument?

It's just a guess, supplied by ffap-file-at-point.

Message #11 received at 12824 <at> debbugs.gnu.org (full text, mbox):

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 12824 <at> debbugs.gnu.org
Subject: Re: bug#12824: 24.2.50; Strange default string brought by M-n after
	`C-x C-v'
Date: Thu, 8 Nov 2012 09:07:19 +0100

>> Is this a bug no? If not, what is the rule here for getting a default
>> argument?
>
> It's just a guess, supplied by ffap-file-at-point.

Well, I don't know how that function works, but I find the current
behavior annoying.

This is how I hit this bug: sometimes I open a C file, which begins
with a comment header at the very beginning of the file, like this:

/*******************
* blah blah blah...
**********************/

and when I open the file, I realize that that is not the file I want
to visit, and then intuitively I do "C-x C-v M-n".  Then I found quite
strange the "X:/*******************" I see in the minibuffer.


-- 
Dani Moncayo

Message #14 received at 12824 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Dani Moncayo <dmoncayo <at> gmail.com>
Cc: 12824 <at> debbugs.gnu.org
Subject: Re: bug#12824: 24.2.50;
	Strange default string brought by M-n after `C-x C-v'
Date: Thu, 08 Nov 2012 03:18:22 -0500

Dani Moncayo wrote:

> Well, I don't know how that function works, but I find the current
> behavior annoying.

Probably you can set file-name-at-point-functions to nil to disable it.

Message #19 received at 12824-done <at> debbugs.gnu.org (full text, mbox):

From: Dani Moncayo <dmoncayo <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 12824-done <at> debbugs.gnu.org
Subject: Re: bug#12824: 24.2.50; Strange default string brought by M-n after
	`C-x C-v'
Date: Thu, 8 Nov 2012 17:50:22 +0100

>> Well, I don't know how that function works, but I find the current
>> behavior annoying.
>
> Probably you can set file-name-at-point-functions to nil to disable it.

Ok, so my case is is a false positive.

Let's close this bug, then.  Thank you.

-- 
Dani Moncayo

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.