From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: using gnome-open with mailcap data
Date: Mon, 13 Jun 2011 11:39:55 -0500 [thread overview]
Message-ID: <87hb7t65yc.fsf@lifelogs.com> (raw)
In-Reply-To: <87zklqw167.fsf@fastmail.fm>
On Fri, 10 Jun 2011 10:17:20 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote:
TH> And this bug report indicates that gnome-open is deprecated in favour of
TH> gvfs-open:
TH> https://bugzilla.gnome.org/show_bug.cgi?id=556305
TH> But sadly, that has the same behavior...
TH> I've filed a new bug report at
TH> https://bugzilla.gnome.org/show_bug.cgi?id=652262
Thanks for that.
On Wed, 08 Jun 2011 12:05:18 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
EA> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
EA> [...]
>> 2. Can I use gnome-open for this sort of thing? It's basically its own
>> little mime parser, and knows all the system defaults, and if I'm
>> going to pass a file to something outside of gnus/emacs, gnome-open
>> knows best what to do with it. Setting gnome-open in my .mailcap file
>> just gives me "Displaying /usr/bin/gnome-open
>> /tmp/emm.5971frN/IMG_3368.JPG...done" in the minibuffer, and then
>> nothing happens.
EA> In fact, what I'd really like to do is short-circuit all the "view
EA> externally" commands so they go straight to gnome-open…
Agreed, that would make it less important to fix the sync bug above. I
don't know all the Gnus magic around handling attachments, but IMO this
would be very nice.
Ted
next prev parent reply other threads:[~2011-06-13 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 19:01 Eric Abrahamsen
2011-06-08 19:05 ` Eric Abrahamsen
2011-06-08 20:36 ` Dan Christensen
2011-06-10 1:39 ` Eric Abrahamsen
2011-06-10 8:17 ` Tassilo Horn
2011-06-13 16:39 ` Ted Zlatanov [this message]
2011-06-10 1:40 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hb7t65yc.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).