ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Overriding pdfview
Date: Thu, 27 Jun 2013 13:25:06 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1306271320220.24744@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <CAF=dkzy8TtDLuciFK1o-Lgjp2BeE-Az_piTP4KobEuVphVwLDg@mail.gmail.com>

On Thu, 27 Jun 2013, Sietse Brouwer wrote:

> Instead of choosing our own default PDF viewer, we should probably
> invoke the user's default PDF viewer. Every OS has a command-line
> program to open a file with the system default program:
>
> On OS X:
> open myfile.pdf
>
> On Windows:
> start myfile.pdf
>
> On Linux, there separate programmes for KDE, new gnome and old gnome,
> and desktop-agnostic:
> kde-open myfile.pdf || gvfs-open myfile.pdf || gnome-open myfile.pdf
> || xdg-open myfile.pdf

Or, simple read the mailcap preference  or use a program such as 
run-mailcap or see which choose the viewer based on mailcap preferences.

I am half joking here; don't go down this route. One can simply leave it 
to the user to write a wrapper to context that calls the PDF viewer when 
context is finished.

Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2013-06-27 17:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 13:53 Bill Meahan
2013-06-26 14:20 ` luigi scarso
2013-06-26 15:17   ` Bill Meahan
2013-06-26 16:11     ` luigi scarso
2013-06-26 19:29       ` Hans Hagen
2013-06-26 20:22         ` luigi scarso
2013-06-26 20:36           ` Siep Kroonenberg
2013-06-26 21:09             ` luigi scarso
2013-06-26 20:50           ` Philipp Gesang
2013-06-26 20:58             ` Hans Hagen
2013-06-26 21:16               ` luigi scarso
2013-06-26 21:34               ` Philipp Gesang
2013-06-27 15:15             ` Sietse Brouwer
2013-06-27 15:44               ` Mica Semrick
2013-06-27 17:25               ` Aditya Mahajan [this message]
2013-06-27 19:39                 ` Arthur Reutenauer
2013-06-27 18:18               ` Hans Hagen
2013-06-26 21:27         ` Bill Meahan
2013-06-26 22:24           ` Hans Hagen
2013-06-26 23:02             ` Bill Meahan
2013-06-27  7:21               ` luigi scarso
2013-06-27  2:21         ` hwitloc
2013-06-27  7:35           ` luigi scarso
2013-06-27  8:13             ` Hans Hagen
     [not found] <mailman.1497.1372359752.2084.ntg-context@ntg.nl>
2013-06-27 19:43 ` Pavneet Arora
2013-06-27 22:44   ` luigi scarso
2013-06-27 23:46     ` Sietse Brouwer
2013-06-27 23:53       ` Gareth Jones
2013-06-28  8:56         ` Keith J. Schultz
2013-06-28 10:34           ` Hans Hagen
2013-06-28 13:16             ` Keith J. Schultz
2013-07-01  2:31           ` David Rogers
2013-06-28  8:28       ` Hans Hagen
2013-06-28  2:29     ` Arthur Reutenauer
2013-06-28  6:23       ` luigi scarso
2013-06-28  8:29 Keith J. Schultz

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=alpine.LNX.2.02.1306271320220.24744@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --cc=ntg-context@ntg.nl \
    /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).