From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Overriding pdfview
Date: Thu, 27 Jun 2013 09:21:15 +0200 [thread overview]
Message-ID: <CAG5iGsAKqfVCpv41Weg5R9J_MtwYQX0mY-3+Hnf8NABOdncNCw@mail.gmail.com> (raw)
In-Reply-To: <51CB731F.8020400@meahan.net>
[-- Attachment #1.1: Type: text/plain, Size: 1087 bytes --]
On Thu, Jun 27, 2013 at 1:02 AM, Bill Meahan <subscribed_lists@meahan.net>wrote:
> On 6/26/2013 6:24 PM, Hans Hagen wrote:
> ........................[snip].........................
>
> If there is one thing I have learned in developing software since 1965
> (not a typo), it is to never depend on *any *third-party application
> being present. If it is not part of the base system install, it probably
> won't be there. I've even met Unix systems without *make*. Requiring the
> user to use some flag or other seldom flies and results in many nastygrams
> and late-night phone calls. If you need it, include it.
>
> yes , this is how currently the standalone core context --- and in the
end, also the texlive -- works, with the constrain that
it has to work with the same results on several different platforms.
This means that the viewer cannot be part of the core -- it's the same
situation of inkscape for svg.
But instead of give no support at all sometime is better to give some
support, if possibile -- for example if it's easy to install a pdf viewer
or inkscape.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1710 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-06-27 7:21 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
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 [this message]
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=CAG5iGsAKqfVCpv41Weg5R9J_MtwYQX0mY-3+Hnf8NABOdncNCw@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--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).