| Summary: | xemacs 21.4 dired fails to open files and directories: No file on this line | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | August Hörandl <hoea> |
| Component: | Current packages | Assignee: | XEmacs team <xemacs> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | bornland, graaff, hoea, paul |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Ebuild for xemacs dired 1.17 | ||
|
Description
August Hörandl
2006-03-23 14:15:33 UTC
xemacs is app-editors/xemacs-21.4.17 dired.el (/usr/lib/xemacs/xemacs-packages/lisp/dired/dired.el) is app-xemacs/dired-1.13 app-xemacs/xemacs-packages-sumo-2003.11.13 I have the same problems on one system (it runs since 2004.1, with upgrades). A other system (it runs since 2005.1) doesn't have the Problems. I think it is a depences problem, when the new version updates an older one. (In reply to comment #2) > I have the same problems on one system (it runs since 2004.1, with upgrades). A > other system (it runs since 2005.1) doesn't have the Problems. > > I think it is a depences problem, when the new version updates an older one. > I have stranger problems too. 'xemacs xxx &' xemacs starts, but it tells me "xxx is a directory" and didn't open it :( with the openfunction I also can't open directories... I forgot: $ emerge --info Portage 2.1_pre7-r5 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.4-r1, 2.6.15-gentoo-r7 i686) ================================================================= System uname: 2.6.15-gentoo-r7 i686 AMD Athlon(TM) XP 2700+ Gentoo Base System version 1.12.0_pre17 dev-lang/python: 2.4.2-r1 sys-apps/sandbox: 1.2.17 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 -march=athlon-xp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo.inode.at/source/ ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo ftp://ftp.nyx.hu/gentoo ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ http://213.186.33.37/gentoo-distfiles/" LANG="de_DE.ISO-8859-1" LC_ALL="de_DE.ISO-8859-1" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa apm arts asf avi berkdb bitmap-fonts cdparanoia cdr cli crypt cups dri dv dvd dvdr eds emacs emboss encode esd foomaticdb fortran gd gdbm gif gpm gstreamer gtk gtk2 icq imlib ipv6 isdnlog java jpeg kde kdeenablefinal libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls nptl nptlonly nvidia ogg opengl oss pam pcre pdflib perl png pppd python qt quicktime readline reflection scanner sdl session spell spl sse ssl svg tcpd tetex truetype truetype-fonts type1-fonts udev usb vorbis win32codecs xine xml xmms xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_de userland_GNU video_cards_nv video_cards_vga video_cards_nvidia video_cards_vesa video_cards_fbdev" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTDIR_OVERLAY (In reply to comment #3) > (In reply to comment #2) > > I have the same problems on one system (it runs since 2004.1, with upgrades). A > > other system (it runs since 2005.1) doesn't have the Problems. > > > > I think it is a depences problem, when the new version updates an older one. > > > > I have stranger problems too. > 'xemacs xxx &' > xemacs starts, but it tells me "xxx is a directory" and didn't open it :( > with the openfunction I also can't open directories... > ok, i re-emerge all xemacs packages (base, xemacs, ispell, sump-packages) now it open directories, but the problem within the bug report is reproducing by me. I'm getting this too. It suddenly appeared today a couple of days after upgrading to GCC 3.4 which involved a lot of re-building of packages so I'm wondering if the underlying cause is elsewhere, perhaps in X itself. The symptom I first spotted is that middle mousing a file no longer open it. Instead Xemacs tries to paste any text in the cut/paste buffer into the directory buffer (i.e. ignoring dired mode) so it fails as the buffer is read only. Right mouse button still works, for updating permission for example. And all three buttons are fine while editing real files. Tis very odd. Now here's a curious thing which may be connected. It's certainly appeared at the same time. This is a screen shot of a dired buffer: http://the-hug.org/paul/files/dired.png I got to this state by opening this directory. I then manually opened 1067.dml (as I couldn't middle mouse click it) and edited it. I then closed 1067.dml so I was back at the dired buffer and found the dired buffer was now in this state. Note the last two entries. These are the full paths of 1067.dml and 1067.dml~ I've never seen it do that before. On the off chance it might solve the problem (can you see a man clutching at straws?) I've just tried xemacs 21.4.17 which is currently masked for testing but it didn't make any difference. Having spent some time Googling about on this one I think I may have fixed it. It's a locale problem. See FAQ 83 (!) on this page http://www.faqs.org/faqs/GNU-Emacs-FAQ/part3/ for some discussion of it. Essentially if LC_TIME is set to something other than "POSIX" (it was set to "en_gb" for me) then 'ls -l' outputs dates in a format other than the one dired expects (ISO in my case). I note I got a new 'ls' recently in coreutils at about the time Xemacs started playing up, so I suspect that 'ls' has been updated for the "en_gb" locale, certainly an older version of 'ls' on another PC doesn't exhibit this behaviour. Anyway the "fix", such as it is, is to prefix your invocation of 'xemacs' by setting LC_TIME to "POSIX". I've set an alias to do this. I'm sure the maintainers can come up with something better however. Looking at the ChangeLogs for dired this *may* have been fixed in a version of dired > 1.13. It's not clear to me because the dired ChangeLog does not include XEmacs package version info so that it is not clear in which XEmacs package this change got included. Could you try with dired 1.17? You can find it (along with many other updated packages) in my xemacs overlay: http://moving-innovations.com/svn/xemacs/ I'm also including it with this bug. Created attachment 92537 [details]
Ebuild for xemacs dired 1.17
app-xemacs/dired-1.17 is now in portage. Please let me know if the problem still occurs with this version of dired and re-open the bug if that is the case. |
