Bug 970987 - emacs file change sometimes does not wotk
Summary: emacs file change sometimes does not wotk
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-05 11:50 UTC by Need Real Name
Modified: 2015-12-02 16:04 UTC (History)
2 users (show)

Fixed In Version: emacs-24.5-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 02:47:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2013-06-05 11:50:47 UTC
In some situations emacs does not catch the case that edited file changed on disk.

Typical example:

1. create some file under cvs, edit it in emacs, save to disk
2. in shell (not in emacs) do cvs commit command, the file is changed ($Id$ expanded to current version)
3. Try to continue editing the file in emacs,  emacs say "the file was changed on disk, ..."
and this is the correct behaviour.

The problem: quite seldom (typically in 1 out of 100 tries) 
instead of correct #3 emacs allows editing changed file without any warning.
This looks like some kind a race, which is hard for me to reproduce deterministically.

The described problem do exists in emacs-24.1-7, emacs-23, emacs-22 and probably emacs-21.

Comment 1 Need Real Name 2013-06-05 11:54:08 UTC
Also, when the race occur, the emacs continue to show old CVS version.
example:
I edited version 1.21 , emacs show 1.21
in shell (not in emacs) I did commit , the version became 1.22
emacs, when the race occurred, still show the version is 1.21 and allows editing the file without warning and suggestion to re-read.

Comment 2 Fedora End Of Life 2015-01-09 18:20:18 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Petr Hracek 2015-04-22 07:52:59 UTC
This should be solved in next emacs version 24.5.
If not please reopen bug again.

Comment 4 Need Real Name 2015-04-22 16:30:02 UTC
I just tried emacs-24.5-1 from Rawhide, recompiled on F17.
emacs-24.5-1.fc17.x86_64
Same thing when using CVS commit from shell.
In one out of 5-6 times it fails to notice file change.

Comment 5 Fedora End Of Life 2015-11-04 15:35:40 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 02:48:00 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.