Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
When a vim process has crashed and didn't delete its .swp file, the following screen is shown, when the same file is to be edited again: E325: ACHTUNG Auslagerungsdatei mit folgendem Namen gefunden: ".cpio-aufruf.txt.NIU.swp" Eigentum von: alexander vom: Thu May 25 09:49:09 2006 Dateiname: ~alexander/cpio-aufruf.txt.NIU ver
When a vim process has crashed and didn't delete its .swp file, the following screen is shown, when the same file is to be edited again: E325: ACHTUNG Auslagerungsdatei mit folgendem Namen gefunden: ".cpio-aufruf.txt.NIU.swp" Eigentum von: alexander vom: Thu May 25 09:49:09 2006 Dateiname: ~alexander/cpio-aufruf.txt.NIU verändert: nein Benutzer-Name: alexander Host-Name: blatt Process-ID: 21260 Beim Öffnen der Datei "cpio-aufruf.txt.NIU" vom: Thu May 25 09:46:50 2006 (1) Ein anderes Programm editiert möglicherweise diese Datei. Wenn dies der Fall ist, sollten Sie vorsichtig sein, damit es nicht zu Überschneidungen kommt. Ende, oder Fortsetzung mit Vorsicht. (2) Eine Editiersitzung für diese Datei ist abgestürzt. Wenn dies der Fall ist, so verwenden Sie ":recover" oder "vim -r cpio-aufruf.txt.NIU" um die Änderungen wiederherzustellen (siehe ":help recovery"). Wenn dies bereits geschehen ist, löschen Sie die Auslagerungsdatei ".cpio-aufruf.txt.NIU.swp" um diese Nachricht zu vermeiden. Auslagerungsdatei ".cpio-aufruf.txt.NIU.swp" ist bereits vorhanden! Öffnen nur zum [L]esen, Trotzdem (e)ditieren, (W)iederherstellen, (L)öschen, (B)eenden, (A)bbrechen: That's the recovery screen. In the last line, the options "Open Read-Only" ("Öffnen nur zum [L]esen") and also "Delete it" ("(L)öschen") are shown (among others). Both have the short cut "L". As they've got the same shortcut, it's not possible to select "(L)öschen". Pressing the "l" or "L" key will select "Öffnen nur zum [L]esen" ("Open Read-Only"). For reference, here's the recovery screen in english: E325: ATTENTION Found a swap file by the name ".cpio-aufruf.txt.NIU.swp" owned by: alexander dated: Thu May 25 09:49:09 2006 file name: ~alexander/cpio-aufruf.txt.NIU modified: no user name: alexander host name: blatt process ID: 21260 While opening file "cpio-aufruf.txt.NIU" dated: Thu May 25 09:46:50 2006 (1) Another program may be editing the same file. If this is the case, be careful not to end up with two different instances of the same file when making changes. Quit, or continue with caution. (2) An edit session for this file crashed. If this is the case, use ":recover" or "vim -r cpio-aufruf.txt.NIU" to recover the changes (see ":help recovery"). If you did this already, delete the swap file ".cpio-aufruf.txt.NIU.swp" to avoid this message. Swap file ".cpio-aufruf.txt.NIU.swp" already exists! [O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort: In English, it's possible to enter "D" to delete the .swp file. I reported this upstream via email to bugs@vim.org, but haven't got a response yet. alexander@blatt /var/log/portage/elog $ emerge --info Portage 2.1_rc2-r3 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.16-suspend2-r6.043.security-models i686) ================================================================= System uname: 2.6.16-suspend2-r6.043.security-models i686 Intel(R) Celeron(R) M processor 1.50GHz Gentoo Base System version 1.12.0 ccache version 2.4 [enabled] dev-lang/python: 2.3.4-r1, 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r1 dev-util/confcache: 0.4.2-r1 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -mtune=pentium-m -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -mtune=pentium-m -pipe -fomit-frame-pointer" DISTDIR="/Gentoo/Portage/distfiles" EMERGE_DEFAULT_OPTS="--alphabetical" FEATURES="autoconfig buildpkg ccache collision-protect confcache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS=" http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ ftp://distro.ibiblio.org/pub/linux/distributions/gentoo http://distfiles.gentoo.org/ " LANG="de_DE.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="de" PKGDIR="/Gentoo/Portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/Gentoo/Portage/build" PORTDIR="/Gentoo/Portage/tree" PORTDIR_OVERLAY="/Gentoo/Portage/local-tree/misc /usr/portage/local/layman/vmware /usr/portage/local/layman/nx /usr/portage/local/layman/gentoo-de" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 GAPING_SECURITY_HOLE X acpi alsa amd apache2 apm arts artswrappersuid async avi bash-completion bdf berkdb bitmap-fonts bluetooth bootsplash cairo caps cardbus ccache cdda cddb cdio cdparanoia cdr cdrom cle266 cli crypt css curlwrappers dbus devmap dillo divx4linux dlloader dri dvd dvdread emoticon esd exif fam fbcon fbdev firefox fping freetype gdbm gif gnokii gnome gstreamer gtk gtk2 hal hpn icc id3 idn imap imlib imlib2 insecure-drivers insecure-savers isdnlog javascript jikes jpeg kde kdeenablefinal kdehiddenvisibility libedit libwww linuxthreads-tls logrotate lynxkeymap mad madwifi maildir matroska mbox mmx mmxext mozilla moznoirc mozsvg mp3 mpeg mpeg2 mpeg4 mplayer multicall ncurses netboot network new-login nfs nis nls no-old-linux no-suexec noantlr nobcel nobeanutils nobsf nobsh nocd nocommonslogging nocommonsnet nodrm nogg nogulm nojsch nojython nolog4j nomac nooro nopri norhino noxalan noxerces nozaptel nptl nsplugin offensive ogg opengl openssh pam_console pam_timestamp passfile password patented pccts pcmcia pcre perl perlsuid pic player png pnp pppd qt quicktime rar readline real recode reflection reiserfs sdl sendfile sensord session sftp sms spell spf spl sse sse2 ssl startup-notification stream subp subtitles suid symlink sysfs syslog tiff transcode truetype truetype-fonts trusted type1-fonts udev underscores unichrome unicode unsafe usb utf8 uudeview vim vim-pager vlm vorbis wifi win32codecs wma123 x11vnc xinetd xml xmms xorg xpm xprint xscreensaver xv xvid xvmc zlib elibc_glibc input_devices_evdev input_devices_keyboard input_devices_mouse input_devices_-synaptics kernel_linux linguas_de userland_GNU video_cards_fbdev video_cards_vesa video_cards_vga video_cards_via" Unset: CTARGET, INSTALL_MASK, LC_ALL, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Created an attachment (id=87586) [details] bugreport file generated by running ":so $VIMRUNTIME/bugreport.vim"
Hi, have you heard anything yet from bugs@vim.org?
Hmm, what do you think would make a better letter to press to do this? "
Hmm, what do you think would make a better letter to press to do this? "Ö"? All that I need to do is change the location of an & character in vim7/src/po/de.po at around line 3519. So, just tell me what you think would make the best choices for keys to press, and I can make it so.
Created an attachment (id=100072) [details] de.diff Hi! Yes, I heard back from upstream. Sorry for not keeping this bug up-to-date :( I'll copy-paste the (short) mail conversation here. I also attachd the patch, upstream supplied. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From: Bram Moolenar Georg - Can you fix this translation problem? - Bram Alexander Skwar wrote: > > When a vim process has crashed and didn't delete its .swp > > file, the following screen is shown, when the same file is > > to be edited again: > > > > E325: ACHTUNG > > Auslagerungsdatei mit folgendem Namen gefunden: ".cpio-aufruf.txt.NIU.swp" > > Eigentum von: alexander vom: Thu May 25 09:49:09 2006 > > Dateiname: ~alexander/cpio-aufruf.txt.NIU > > ver
Created an attachment (id=100072) [details] de.diff Hi! Yes, I heard back from upstream. Sorry for not keeping this bug up-to-date :( I'll copy-paste the (short) mail conversation here. I also attachd the patch, upstream supplied. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From: Bram Moolenar Georg - Can you fix this translation problem? - Bram Alexander Skwar wrote: > > When a vim process has crashed and didn't delete its .swp > > file, the following screen is shown, when the same file is > > to be edited again: > > > > E325: ACHTUNG > > Auslagerungsdatei mit folgendem Namen gefunden: ".cpio-aufruf.txt.NIU.swp" > > Eigentum von: alexander vom: Thu May 25 09:49:09 2006 > > Dateiname: ~alexander/cpio-aufruf.txt.NIU > > verändert: nein > > Benutzer-Name: alexander Host-Name: blatt > > Process-ID: 21260 > > Beim Öffnen der Datei "cpio-aufruf.txt.NIU" > > vom: Thu May 25 09:46:50 2006 > > > > (1) Ein anderes Programm editiert möglicherweise diese Datei. > > Wenn dies der Fall ist, sollten Sie vorsichtig sein, damit > > es nicht zu Überschneidungen kommt. > > Ende, oder Fortsetzung mit Vorsicht. > > > > (2) Eine Editiersitzung für diese Datei ist abgestürzt. > > Wenn dies der Fall ist, so verwenden Sie ":recover" oder "vim -r cpio-aufruf.txt.NIU" > > um die Änderungen wiederherzustellen (siehe ":help recovery"). > > Wenn dies bereits geschehen ist, löschen Sie die Auslagerungsdatei ".cpio-aufruf.txt.NIU.swp" > > um diese Nachricht zu vermeiden. > > > > Auslagerungsdatei ".cpio-aufruf.txt.NIU.swp" ist bereits vorhanden! > > Öffnen nur zum [L]esen, Trotzdem (e)ditieren, (W)iederherstellen, (L)öschen, (B)eenden, (A)bbrechen: > > > > That's the recovery screen. > > > > In the last line, the options "Open Read-Only" ("Öffnen nur zum [L]esen") > > and also "Delete it" ("(L)öschen") are shown (among others). Both have > > the short cut "L". > > > > As they've got the same shortcut, it's not possible to select > > "(L)öschen". Pressing the "l" or "L" key will select "Öffnen > > nur zum [L]esen" ("Open Read-Only"). > > > > For reference, here's the recovery screen in english: > > > > E325: ATTENTION > > Found a swap file by the name ".cpio-aufruf.txt.NIU.swp" > > owned by: alexander dated: Thu May 25 09:49:09 2006 > > file name: ~alexander/cpio-aufruf.txt.NIU > > modified: no > > user name: alexander host name: blatt > > process ID: 21260 > > While opening file "cpio-aufruf.txt.NIU" > > dated: Thu May 25 09:46:50 2006 > > > > (1) Another program may be editing the same file. > > If this is the case, be careful not to end up with two > > different instances of the same file when making changes. > > Quit, or continue with caution. > > > > (2) An edit session for this file crashed. > > If this is the case, use ":recover" or "vim -r cpio-aufruf.txt.NIU" > > to recover the changes (see ":help recovery"). > > If you did this already, delete the swap file ".cpio-aufruf.txt.NIU.swp" > > to avoid this message. > > > > Swap file ".cpio-aufruf.txt.NIU.swp" already exists! > > [O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort: > > > > In English, it's possible to enter "D" to delete the .swp file. > > > > Alexander Skwar > > -- > > "So.. humans have easily injured knees. My race will find this > > information very useful indeed. Mwahwahahahaha!" > > --Morbo -- You were lucky to have a LAKE! There were a hundred and sixty of us living in a small shoebox in the middle of the road. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
************************************************************************************************************************ From: Georg Dahn Hi Bram! Sorry for that. I have fixed it, changed a similar message, and added a missing translation (see the attached patch). Best wishes, Georg Bram Moolenaar wrote: > > Georg - > > > > Can you fix this translation problem? > > > > - Bram > > > > Alexander Skwar wrote: > > >> >> When a vim process has crashed and didn't delete its .swp >> >> file, the following screen is shown, when the same file is >> >> to be edited again: >> >> >> >> E325: ACHTUNG >> >> Auslagerungsdatei mit folgendem Namen gefunden: ".cpio-aufruf.txt.NIU.swp" >> >> Eigentum von: alexander vom: Thu May 25 09:49:09 2006 >> >> Dateiname: ~alexander/cpio-aufruf.txt.NIU >> >> ver
************************************************************************************************************************ From: Georg Dahn Hi Bram! Sorry for that. I have fixed it, changed a similar message, and added a missing translation (see the attached patch). Best wishes, Georg Bram Moolenaar wrote: > > Georg - > > > > Can you fix this translation problem? > > > > - Bram > > > > Alexander Skwar wrote: > > >> >> When a vim process has crashed and didn't delete its .swp >> >> file, the following screen is shown, when the same file is >> >> to be edited again: >> >> >> >> E325: ACHTUNG >> >> Auslagerungsdatei mit folgendem Namen gefunden: ".cpio-aufruf.txt.NIU.swp" >> >> Eigentum von: alexander vom: Thu May 25 09:49:09 2006 >> >> Dateiname: ~alexander/cpio-aufruf.txt.NIU >> >> verändert: nein >> >> Benutzer-Name: alexander Host-Name: blatt >> >> Process-ID: 21260 >> >> Beim Öffnen der Datei "cpio-aufruf.txt.NIU" >> >> vom: Thu May 25 09:46:50 2006 >> >> >> >> (1) Ein anderes Programm editiert möglicherweise diese Datei. >> >> Wenn dies der Fall ist, sollten Sie vorsichtig sein, damit >> >> es nicht zu Überschneidungen kommt. >> >> Ende, oder Fortsetzung mit Vorsicht. >> >> >> >> (2) Eine Editiersitzung für diese Datei ist abgestürzt. >> >> Wenn dies der Fall ist, so verwenden Sie ":recover" oder "vim -r cpio-aufruf.txt.NIU" >> >> um die Änderungen wiederherzustellen (siehe ":help recovery"). >> >> Wenn dies bereits geschehen ist, löschen Sie die Auslagerungsdatei ".cpio-aufruf.txt.NIU.swp" >> >> um diese Nachricht zu vermeiden. >> >> >> >> Auslagerungsdatei ".cpio-aufruf.txt.NIU.swp" ist bereits vorhanden! >> >> Öffnen nur zum [L]esen, Trotzdem (e)ditieren, (W)iederherstellen, (L)öschen, (B)eenden, (A)bbrechen: >> >> >> >> That's the recovery screen. >> >> >> >> In the last line, the options "Open Read-Only" ("Öffnen nur zum [L]esen") >> >> and also "Delete it" ("(L)öschen") are shown (among others). Both have >> >> the short cut "L". >> >> >> >> As they've got the same shortcut, it's not possible to select >> >> "(L)öschen". Pressing the "l" or "L" key will select "Öffnen >> >> nur zum [L]esen" ("Open Read-Only"). >> >> >> >> For reference, here's the recovery screen in english: >> >> >> >> E325: ATTENTION >> >> Found a swap file by the name ".cpio-aufruf.txt.NIU.swp" >> >> owned by: alexander dated: Thu May 25 09:49:09 2006 >> >> file name: ~alexander/cpio-aufruf.txt.NIU >> >> modified: no >> >> user name: alexander host name: blatt >> >> process ID: 21260 >> >> While opening file "cpio-aufruf.txt.NIU" >> >> dated: Thu May 25 09:46:50 2006 >> >> >> >> (1) Another program may be editing the same file. >> >> If this is the case, be careful not to end up with two >> >> different instances of the same file when making changes. >> >> Quit, or continue with caution. >> >> >> >> (2) An edit session for this file crashed. >> >> If this is the case, use ":recover" or "vim -r cpio-aufruf.txt.NIU" >> >> to recover the changes (see ":help recovery"). >> >> If you did this already, delete the swap file ".cpio-aufruf.txt.NIU.swp" >> >> to avoid this message. >> >> >> >> Swap file ".cpio-aufruf.txt.NIU.swp" already exists! >> >> [O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort: >> >> >> >> In English, it's possible to enter "D" to delete the .swp file. >> >> >> >> Alexander Skwar >> >> -- >> >> "So.. humans have easily injured knees. My race will find this >> >> information very useful indeed. Mwahwahahahaha!" >> >> --Morbo > > *** src/po/de.po 2006-06-18 07:49:22.000000000 +0200 --- ../messages/de.po 2006-06-18 07:31:56.000000000 +0200 *************** *** 3502,3508 **** "&Quit\n" "&Abort" msgstr "" ! "Öffnen nur zum &Lesen\n" "Trotzdem &editieren\n" "&Wiederherstellen\n" "&Beenden\n" --- 3502,3508 ---- "&Quit\n" "&Abort" msgstr "" ! "Nur zum &Lesen öffnen\n" "Trotzdem &editieren\n" "&Wiederherstellen\n" "&Beenden\n" *************** *** 3516,3525 **** "&Quit\n" "&Abort" msgstr "" ! "Öffnen nur zum &Lesen\n" "Trotzdem &editieren\n" "&Wiederherstellen\n" ! "&Löschen\n" "&Beenden\n" "&Abbrechen" --- 3516,3525 ---- "&Quit\n" "&Abort" msgstr "" ! "Nur zum &Lesen öffnen\n" "Trotzdem &editieren\n" "&Wiederherstellen\n" ! "&Datei Löschen\n" "&Beenden\n" "&Abbrechen" *************** *** 6131,6133 **** --- 6131,6135 ---- "Die Definition von COMPOUNDPERMITFLAG nach dem PFX Element kann falsches Ergebnis in Zeile %s ergeben " "%d" + msgid "E116: Invalid arguments for function %s" + msgstr "E116: Ungültige Argumente für die Funktion %s" ========================================================================================================================= Georg - > > Sorry for that. I have fixed it, changed a similar message, and added a > > missing translation (see the attached patch). Thanks, I'll include it. The updated messages files are available at ftp://ftp.vim.org/pub/vim/messages - Bram -- Not too long ago, cut and paste was done with scissors and glue... /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
Cool. This will appear in the next version of vim in portage, which should be unmasked in a week or so. Thanks for the report!
This is fixed in vim-7.0.146, which is now unmasked in the tree. Thanks for the report!
Sorry, reopening this until bug #152620 is resolved.
Okay, now it's /really/ fixed. Thanks for your patience.
