Re: FVWM: chromium under fvwm and opening pdf files
On 02/14/2010 03:12 AM, des...@verizon.net wrote: Thomas Adam tho...@xteddy.org writes: On Sat, Feb 13, 2010 at 06:45:03PM -0500, des...@verizon.net wrote: Thomas Adam tho...@xteddy.org writes: On Sun, Feb 14, 2010 at 12:09:25AM +0100, Nathan Huesken wrote: Hi, When I use chromium under Xfce4, it opens pdf files using evince. When I use chromium under fvwm, it opens pdfs using firefox (which opens pdfs using evince, but is started and takes long to start). I am not sure, if this is really a fvwm thing, but it is my only guess. Maybe someone in the list knows ... Read up on how mailcap entries work. Nothing to do with FVWM. Desktop environments are messing up what used to be a well defined boundary between the window manager and X. On my Fedora system, /etc/mailcap contains: audio/*; /usr/bin/xdg-open %s image/*; /usr/bin/xdg-open %s application/msword; /usr/bin/xdg-open %s application/pdf; /usr/bin/xdg-open %s application/postscript ; /usr/bin/xdg-open %s text/html; /usr/bin/xdg-open %s ; copiousoutput So, from this system's point of view, mailcap is just a thin layer on top of xdg-open. Ah yes. I'd forgotten about that. I thought this only affected applications running under GNOME or KDE, where those frameworks offer a means of defining known applications. For instance, unless I run gnome-settings-daemon, I get to use .mailcap just fine. I can understand what the XDG are trying to do, but this seems completely bogus, when they should be completely dependant on mailcap entries entirely, rather than reinventing the wheel. Still, not a lot we can do about it. We could ask the xdg folks to try the kde, gnome, or xfce tools BEFORE they resort to mailcap, etc. Then Fvwm users would be okay as long as they had one of the desktop environments installed. Given the way most linux distros are packaged, that would work better almost always. The only problem I can think of is if some of the opens are based on some non-standard part of the DE's WM. This reminds me of the discussion we had a while back about xdg_menu. At first I downloaded and built xdg_menu, now it's a standard part of FC11. Hi, After all your helpfull answers, I discovered that chromium (xdg-open) respects all my file association when I set DE=xfce (which makes sense since I am using thunar and specify my file associations there). Thanks! Nathan
FVWM: chromium under fvwm and opening pdf files
Hi, When I use chromium under Xfce4, it opens pdf files using evince. When I use chromium under fvwm, it opens pdfs using firefox (which opens pdfs using evince, but is started and takes long to start). I am not sure, if this is really a fvwm thing, but it is my only guess. Maybe someone in the list knows ... Could it be that this is because fvwm is not a DE? Can I somehow solve this? Thanks! Nathan -- _ / He expanded his chest to make it \ | totally clear that here was the sort of | | man you only dared to cross if you had | \ a team of Sherpas with you./ - \ ,__, \ (oo) (__))\ ||--|| *
Re: FVWM: chromium under fvwm and opening pdf files
On Sun, Feb 14, 2010 at 12:09:25AM +0100, Nathan Huesken wrote: Hi, When I use chromium under Xfce4, it opens pdf files using evince. When I use chromium under fvwm, it opens pdfs using firefox (which opens pdfs using evince, but is started and takes long to start). I am not sure, if this is really a fvwm thing, but it is my only guess. Maybe someone in the list knows ... Read up on how mailcap entries work. Nothing to do with FVWM. -- Thomas Adam -- It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
Re: FVWM: chromium under fvwm and opening pdf files
On Sat, Feb 13, 2010 at 06:45:03PM -0500, des...@verizon.net wrote: Thomas Adam tho...@xteddy.org writes: On Sun, Feb 14, 2010 at 12:09:25AM +0100, Nathan Huesken wrote: Hi, When I use chromium under Xfce4, it opens pdf files using evince. When I use chromium under fvwm, it opens pdfs using firefox (which opens pdfs using evince, but is started and takes long to start). I am not sure, if this is really a fvwm thing, but it is my only guess. Maybe someone in the list knows ... Read up on how mailcap entries work. Nothing to do with FVWM. Desktop environments are messing up what used to be a well defined boundary between the window manager and X. On my Fedora system, /etc/mailcap contains: audio/*; /usr/bin/xdg-open %s image/*; /usr/bin/xdg-open %s application/msword; /usr/bin/xdg-open %s application/pdf; /usr/bin/xdg-open %s application/postscript ; /usr/bin/xdg-open %s text/html; /usr/bin/xdg-open %s ; copiousoutput So, from this system's point of view, mailcap is just a thin layer on top of xdg-open. Ah yes. I'd forgotten about that. I thought this only affected applications running under GNOME or KDE, where those frameworks offer a means of defining known applications. For instance, unless I run gnome-settings-daemon, I get to use .mailcap just fine. I can understand what the XDG are trying to do, but this seems completely bogus, when they should be completely dependant on mailcap entries entirely, rather than reinventing the wheel. Still, not a lot we can do about it. -- Thomas Adam -- It was the cruelest game I've ever played and it's played inside my head. -- Hush The Warmth, Gorky's Zygotic Mynci.
Re: FVWM: chromium under fvwm and opening pdf files
des...@verizon.net writes: Thomas Adam tho...@xteddy.org writes: On Sun, Feb 14, 2010 at 12:09:25AM +0100, Nathan Huesken wrote: Hi, When I use chromium under Xfce4, it opens pdf files using evince. When I use chromium under fvwm, it opens pdfs using firefox (which opens pdfs using evince, but is started and takes long to start). I am not sure, if this is really a fvwm thing, but it is my only guess. Maybe someone in the list knows ... Read up on how mailcap entries work. Nothing to do with FVWM. Desktop environments are messing up what used to be a well defined boundary between the window manager and X. On my Fedora system, /etc/mailcap contains: audio/*; /usr/bin/xdg-open %s image/*; /usr/bin/xdg-open %s application/msword; /usr/bin/xdg-open %s application/pdf; /usr/bin/xdg-open %s application/postscript ; /usr/bin/xdg-open %s text/html; /usr/bin/xdg-open %s ; copiousoutput So, from this system's point of view, mailcap is just a thin layer on top of xdg-open. xdg-open on my system only knows to use firefox. I see that xdg-open uses a file named defaults.list. I have 3 of those: /usr/local/share/applications/defaults.list /usr/share/applications/defaults.list /usr/share/kde-settings/kde-profile/default/share/applications/defaults.list I think the trick is to convince xdg-open to use one or more of those files... Following up my own post. xdg-open is a shell script that tries to figure out the desktop environment that is running and then uses a script provided by the desktop environment to open the file. You can take a look yourself. For environments it doesn't recognize it tries to use the following programs: mimeopen, run-mailcap, $BROWSER, htmlview, firefox, mozilla, netscape, links, lynx. (In that order). For kde it uses kde_open. For Gnome it uses gvfs-open or gnome-open. For XFCE it uses exo-open. I tried using kde_open under fvwm, it was too slow. exo-open, gnome-open and gvfs-open seemed ok. So I think hacking up xdg-open to use exo-open is the default might be a good solution for the OP.
Re: FVWM: chromium under fvwm and opening pdf files
Thomas Adam tho...@xteddy.org writes: On Sat, Feb 13, 2010 at 06:45:03PM -0500, des...@verizon.net wrote: Thomas Adam tho...@xteddy.org writes: On Sun, Feb 14, 2010 at 12:09:25AM +0100, Nathan Huesken wrote: Hi, When I use chromium under Xfce4, it opens pdf files using evince. When I use chromium under fvwm, it opens pdfs using firefox (which opens pdfs using evince, but is started and takes long to start). I am not sure, if this is really a fvwm thing, but it is my only guess. Maybe someone in the list knows ... Read up on how mailcap entries work. Nothing to do with FVWM. Desktop environments are messing up what used to be a well defined boundary between the window manager and X. On my Fedora system, /etc/mailcap contains: audio/*; /usr/bin/xdg-open %s image/*; /usr/bin/xdg-open %s application/msword; /usr/bin/xdg-open %s application/pdf; /usr/bin/xdg-open %s application/postscript ; /usr/bin/xdg-open %s text/html; /usr/bin/xdg-open %s ; copiousoutput So, from this system's point of view, mailcap is just a thin layer on top of xdg-open. Ah yes. I'd forgotten about that. I thought this only affected applications running under GNOME or KDE, where those frameworks offer a means of defining known applications. For instance, unless I run gnome-settings-daemon, I get to use .mailcap just fine. I can understand what the XDG are trying to do, but this seems completely bogus, when they should be completely dependant on mailcap entries entirely, rather than reinventing the wheel. Still, not a lot we can do about it. We could ask the xdg folks to try the kde, gnome, or xfce tools BEFORE they resort to mailcap, etc. Then Fvwm users would be okay as long as they had one of the desktop environments installed. Given the way most linux distros are packaged, that would work better almost always. The only problem I can think of is if some of the opens are based on some non-standard part of the DE's WM. This reminds me of the discussion we had a while back about xdg_menu. At first I downloaded and built xdg_menu, now it's a standard part of FC11.
