GNU bug report logs - #14002
24.3.50; buffer-file-coding-system is undecided-dos, everywhere

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 14002 in the body.
You can then email your comments to 14002 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: Dmitry Gutov <dgutov <at> yandex.ru>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50; buffer-file-coding-system is undecided-dos, everywhere
Date: Wed, 20 Mar 2013 06:26:34 +0400

1. emacs -Q
2. find-file .../emacs-bzr/trunk/README
3. eval `buffer-file-coding-system' => undecided-dos
4. make a change, save the buffer
5. run vc-diff => the whole buffer is marked as changed
6. eval `buffer-file-coding-system' again => still undecided-dos

Same with src/w32fns.c, for example. Or any other files with Unix line
endings (in other repositories).

In GNU Emacs 24.3.50.1 (i386-mingw-nt6.1.7601)
 of 2013-03-20 on SOL
Bzr revision: 112094 dgutov <at> yandex.ru-20130319151240-zn0ty0o5g047tzvs
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --with-gcc (3.4) --cflags -IJ:/apps/system/gnuwin32/include'

Important settings:
  value of $EMACSDATA: C:/Users/gutov/vc/emacs-bzr/trunk/etc
  value of $EMACSDOC: C:/Users/gutov/vc/emacs-bzr/trunk/etc
  value of $EMACSLOADPATH: C:/Users/gutov/vc/emacs-bzr/trunk/site-lisp;C:/Users/gutov/vc/emacs-bzr/trunk/../site-lisp;C:/Users/gutov/vc/emacs-bzr/trunk/lisp;C:/Users/gutov/vc/emacs-bzr/trunk/leim
  value of $EMACSPATH: C:/Users/gutov/vc/emacs-bzr/trunk/bin
  value of $LANG: RUS
  locale-coding-system: cp1251
  default enable-multibyte-characters: t

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

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: 14002 <at> debbugs.gnu.org
Subject: Re: bug#14002: Acknowledgement (24.3.50; buffer-file-coding-system
	is undecided-dos, everywhere)
Date: Wed, 20 Mar 2013 06:39:08 +0400

Some more info:

With emacs -Q, the coding system is undecided-dos during opening, 
modification and saving. If I then do vc-revert, it becomes 
undecided-unix, and the subsequent editing of the file works as expected.

In my usual setup, I have

(set-language-environment 'Cyrillic-CP1251) ; defined previously
(set-file-name-coding-system 'cp1251)
(prefer-coding-system 'utf-8)

and the coding system in this scenario goes from utf-8 to utf-8-dos 
(after saving) to undecided-unix (after reverting), and then editing 
similarly works fine.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 14002 <at> debbugs.gnu.org
Subject: Re: bug#14002: 24.3.50;
	buffer-file-coding-system is undecided-dos, everywhere
Date: Wed, 20 Mar 2013 06:05:26 +0200

> From: Dmitry Gutov <dgutov <at> yandex.ru>
> Date: Wed, 20 Mar 2013 06:26:34 +0400
> 
> 1. emacs -Q
> 2. find-file .../emacs-bzr/trunk/README
> 3. eval `buffer-file-coding-system' => undecided-dos
> 4. make a change, save the buffer
> 5. run vc-diff => the whole buffer is marked as changed
> 6. eval `buffer-file-coding-system' again => still undecided-dos
> 
> Same with src/w32fns.c, for example. Or any other files with Unix line
> endings (in other repositories).

This is a duplicate if 13977.

(Why don't people try to look for similar bug reports before they do?)

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

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 14002 <at> debbugs.gnu.org,
	GNU bug tracker automated control server <control <at> debbugs.gnu.org>
Subject: Re: bug#14002: 24.3.50;	buffer-file-coding-system is undecided-dos,
	everywhere
Date: Wed, 20 Mar 2013 08:18:23 +0400

merge 14002 13977
thanks

On 20.03.2013 8:05, Eli Zaretskii wrote:
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> Date: Wed, 20 Mar 2013 06:26:34 +0400
>>
>> 1. emacs -Q
>> 2. find-file .../emacs-bzr/trunk/README
>> 3. eval `buffer-file-coding-system' => undecided-dos
>> 4. make a change, save the buffer
>> 5. run vc-diff => the whole buffer is marked as changed
>> 6. eval `buffer-file-coding-system' again => still undecided-dos
>>
>> Same with src/w32fns.c, for example. Or any other files with Unix line
>> endings (in other repositories).
>
> This is a duplicate if 13977.

Indeed. Sorry.

> (Why don't people try to look for similar bug reports before they do?)

Obviously, you only notice the cases when they don't.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 14002 <at> debbugs.gnu.org
Subject: Re: bug#14002: 24.3.50;
	buffer-file-coding-system is undecided-dos, everywhere
Date: Wed, 20 Mar 2013 18:54:44 +0200

> Date: Wed, 20 Mar 2013 08:18:23 +0400
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> CC: 14002 <at> debbugs.gnu.org, 
>  GNU bug tracker automated control server <control <at> debbugs.gnu.org>
> 
> > (Why don't people try to look for similar bug reports before they do?)
> 
> Obviously, you only notice the cases when they don't.

Obviously.  But the point is, there are too many of those duplicates.

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

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 14002 <at> debbugs.gnu.org
Subject: Re: bug#14002: 24.3.50;	buffer-file-coding-system is undecided-dos,
	everywhere
Date: Thu, 21 Mar 2013 00:40:44 +0400

On 20.03.2013 20:54, Eli Zaretskii wrote:
>> Date: Wed, 20 Mar 2013 08:18:23 +0400
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> CC: 14002 <at> debbugs.gnu.org,
>>   GNU bug tracker automated control server <control <at> debbugs.gnu.org>
>>
>>> (Why don't people try to look for similar bug reports before they do?)
>>
>> Obviously, you only notice the cases when they don't.
>
> Obviously.  But the point is, there are too many of those duplicates.

Given the size of Emacs user community, I'd rather expect more bug 
reports, including duplicate, nonsensical, etc, than currently.

In this specific case, I though I'm aware of the current bugs (I'm 
subscribed to gmane.emacs.bugs in Gnus), and I also thought that this 
kind of bug wouldn't stay unfixed for more than a day, much less 5 days 
that went since 13977 was filed. I was wrong on both counts.

Speaking of bug reports, the recent font-lock breakage was similar in 
that it was obvious and stayed unfixed for a while. It just affected a 
bigger audience.

Previous Next

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