emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Cc: nicholas.dokos@hp.com
Subject: Re: setting default pdf viewer
Date: Tue, 13 Mar 2012 23:42:00 +0800	[thread overview]
Message-ID: <87vcm833uf.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 13237.1331648207@alphaville

On Tue, Mar 13 2012, Nick Dokos wrote:

> [OT warning: no org content here, just gnome/mailcap.]
>
> Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> > Next question: since xpdf is available and /etc/mailcap prefers it, why
>> > is nautilus using evince? Doesn't it use mailcap? I guess not, although
>> > I don't know for sure[fn:1], but it wouldn't surprise me if it did its
>> > own thing: there are way too many cooks in this kitchen.
>> 
>> I think most linux desktop environments use something like xdg-open or
>> gnome-open to determine defaults applications, all my defaults seem to
>> live in /usr/local/share/applications, which can be overridden in the
>> home directory. Nautilus ought to use gnome-open. I've tweaked most of
>> my "open-in-external-blah" functions (in dired and gnus, for example) to
>> use xdg-open, so the same defaults are used in all my applications,
>> including emacs.
>> 
>
> Thanks! That was useful.
>
> Part of my frustration with these things (gnome things in particular) is
> the sparse-to-non-existent documentation, so I really appreciate these
> pointers. Or maybe I've given up too easily: is there good documentation
> somewhere on the web e.g. of gconftool? Not just the syntax but an
> enumeration of possibilities. My impression is that things like this are
> hidden, (and in some cases, as time goes on, even if they exist, they
> are taken away, so there is some motivation to keep them hidden,
> although I'm not thinking conspiracy: it's just that documenting things
> is hard.)  I've usually fumbled in the dark with things under ~/.gconf
> (or .gnome2 or .gnome) until I've found something plausible. Just to
> make my problem concrete: what is the invocation of gconftool that would
> change the default pdf viewer to xpdf?

I don't use gnome anymore, but back when I did the gconf stuff was
absolutely its most obscure aspect. I get the feeling that gnome is
still trying to be the Linux Desktop for Dummies, and while gconftool is
there if you need it, no one is trying to make it any easier to use. I
don't think I ever once invoked gconftool, so I'm afraid I don't know…

> The other way that I eventually figured out to do that is to open some
> application, e.g. nautilus, select some PDF file, click on Properties
> and change the default application: I find that counterintuitive,
> changing the properties of a class through a single instance (and to all
> applications that use the mechanism, even though I'm just using
> nautilus: I can't help but find this method somewhat distasteful.) And I
> like editing files rather than clicking buttons, but that's me.

One of the nice things with the Mac is that it gives you two options in
the contextual menu: you can open a file with a specific application, or
you can tell it "use this application for all files of this type". That
at least made it clearer what was going on.

> To get back to your post: my problem with xdg-open with its switch
> blades (kde-open, gnome-open, etc) is that each of those has its own
> customization methods. So if I ever want to switch from kde to gnome, I
> have to redo the customizations (and I have to find out how to do all
> that for the new environment).
>
> I'd rather have them all use mailcap for preferred application choice.
> And if mailcap does not provide all the capabilities needed by them, I'd
> rather they cooperated and came up with a common mechanism that would
> serve *all* their needs (plus provide thorough documentation!) But
> that's a fight that's been fought and lost many times - many more times
> than it's been won.

Since moving from Ubuntu to a home-rolled Arch/XFCE/Stumpwm mix, I've
definitely become aware that, of all the aspects of a Linux
installation, the functionality that falls under the "desktop
environment" category is at once the most underdocumented, and also most
key to user experience. This seems to be the dark under-plumbing of the
Linux GUI experience, the unlovely tangle that no one wants to expose to
the user. When I went spelunking, I got the impression that mailcap
predates all this XXX-open malarkey, but that most of the apps I use
prefer that over mailcap. Like you, I would be very, very surprised if
anyone ever put any thought into helping user customizations survive a
transition from one DE to another. I still think you'll have most luck
messing with files under ~/.local/share/applications, though it probably
won't be as simple as that.

Sorry, that's not helpful at all!

> Enough venting: I've veered off-topic quite a bit here. Apologies for
> the length of the (possibly uninformed) rant. If I've got things wrong,
> I'd love to be corrected, but I don't want to exercise the patience of
> the regulars too much. But I hope that the discussion, however
> tangential, is useful.
>
> Thanks,
> Nick
>
>

-- 
GNU Emacs 24.0.94.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
 of 2012-03-06 on pellet
Org-mode version 7.8.03 (release_7.8.03.581.g5cb80)

  reply	other threads:[~2012-03-13 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 14:16 setting default pdf viewer Nick Dokos
2012-03-13 15:42 ` Eric Abrahamsen [this message]
2012-03-13 15:47   ` Nick Dokos
2012-03-13 21:32 ` Achim Gratz
2012-03-15  2:33 ` François Pinard
  -- strict thread matches above, loose matches on Subject: below --
2012-03-11  8:01 prad
2012-03-11  8:17 ` Puneeth Chaganti
2012-03-11 17:15   ` prad
2012-03-11 22:25     ` brian powell
2012-03-12  0:50 ` Nick Dokos
2012-03-12  1:58   ` prad
2012-03-12  2:50     ` Nick Dokos
2012-03-12  5:06       ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vcm833uf.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).