Package: emacs24 Version: 24.3+1-1.1 Severity: important I am not sure if this is one or several bugs, but all these features are either new or newly turned on by default and they all seem to be related to a single feature, so I believe there is just one bug somewhere.
Steps to reproduce: start emacs, visit a file, switch to another program and change the file you just visited (touch will do, but it really has to be a different program, running M-x shell or similar won't do). Nothing happens, just as supposed. Now switch back to emacs and it pops up an annoying dialog window about an altered file it is visiting almost immediately. Here is the first bug: *almost* immediately: if you are quick, you can alter the buffer before the window steals focus. Suppose you were not that fast, so the buffer is unaltered, and you answer "no" to the dialog. Here is the second bug: emacs shows another, identical, dialog. If you keep answering "no", emacs shows 3-15 identical dialogs, asking the very same question. (It's possible it only shows 3 if you were not fast enough, I got too angry to test more, but it's quite possible the number of dialogs equals 3+number of changes you made before the dialog appeared.) Close emacs. Start is again, visit the file again, but this time alter the buffer before switching away and touching the file in a terminal (or whatever you like to do to make emacs think it has been altered) and then go back to emacs again. Answer "no" to the dialog as many times as emacs asks you and then save the buffer. Emacs now asks you the usual question about a file changed on disk, to which you should answer to save the buffer anyway. Here is the third bug: now emacs asks you whether you want to revert the buffer or overwrite the changed file with your buffer, but then immediately (you might be fast enough to answer that first, please be slow) asks the new question about discaring edits because the file your buffer is visiting has changed. At this point, emacs is unusable: the first question has apparently removed all keybindings since there is no way of making the second question go away. Any key I press causes the same message to be displayed: "<key> is undefined". I cannot save the file, revert the buffer, or even C-g or Esc, because every key I can think of is undefined. Likewise mouse. (Menu works, but does not help.) Expected outcome: Bug 1: nothing. No questions, no dialogs, nothing. Or at least an option to turn this annoying new feature off. Bug 2: Just one question per buffer. Bug 3: Buffer saved according to my wish. Cheers, Juha -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages emacs24 depends on: ii emacs24-bin-common 24.3+1-1.1 ii gconf-service 3.2.6-1 ii libasound2 1.0.27.2-1 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-93 ii libcairo-gobject2 1.12.16-2 ii libcairo2 1.12.14-4 ii libdbus-1-3 1.6.14-1 ii libfontconfig1 2.10.2-2 ii libfreetype6 2.4.9-1.1 ii libgconf-2-4 3.2.6-1 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgif4 4.1.6-10 ii libglib2.0-0 2.36.4-1 ii libgnutls26 2.12.23-7 ii libgomp1 4.8.1-10 ii libgpm2 1.20.4-6.1 ii libgtk-3-0 3.8.4-1 ii libice6 2:1.0.8-2 ii libjpeg8 8d-1 ii libm17n-0 1.6.4-2 ii libmagickcore5 8:6.7.7.10-6 ii libmagickwand5 8:6.7.7.10-6 ii libotf0 0.9.13-1 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpng12-0 1.2.49-4 ii librsvg2-2 2.36.4-2 ii libselinux1 2.1.13-2 ii libsm6 2:1.2.1-2 ii libtiff4 3.9.7-2 ii libtinfo5 5.9+20130608-1 ii libx11-6 2:1.6.1-1 ii libxft2 2.3.1-1 ii libxml2 2.9.1+dfsg1-3 ii libxpm4 1:3.5.10-1 ii libxrender1 1:0.9.8-1 ii zlib1g 1:1.2.8.dfsg-1 emacs24 recommends no packages. Versions of packages emacs24 suggests: pn emacs24-common-non-dfsg <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org