From: hwitloc@gmail.com
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Standalone Installation Question
Date: Mon, 21 Oct 2013 01:06:25 +0900 [thread overview]
Message-ID: <20131021010625.3284@binki> (raw)
In-Reply-To: Your message of Sun, 20 Oct 2013 16:05:47 +0200 <CAG5iGsA6JcVLOGNAm5QhaT3wyEF0+-Ht4HHOaaUJFaqraWhMcQ@mail.gmail.com>
To: ConTeXt package maintainer for TeXlive distribution:
TeXlive as of 2011 or so is compatible under unix type with cygwin.
I do not want to use the Microsoft version. There is no reason from me to change
code and scripts to work with Microsoft's methods. Also I will not give up the unix developement environment that cygwin delivers to work with ConteXt.
I'd like to know the the Context package that was submitted to TeXlive.
I presume this was in soure format. How can I get that for the beta/current MKIV
and build it myself?
Thanks
luigi scarso <luigi.scarso@gmail.com> wrote:
> On Sun, Oct 20, 2013 at 3:54 PM, <hwitloc@gmail.com> wrote:
>
> Yes I saw the Windows version of Context mentioned and read it,
> but the documentation is,
> in this case, wrong or not fully correct. This is because I am now
> using Context which comes is included in the TexLive distribution,
> selected with Unix like operating systems. No bat files or other
> ancillary code or invokations are necessary.
>
> Texlive's Context program would probably not run directly on
> Microsoft Windows O.S.
> hm, my experience is the opposite: texlive context runs on Windows,
> but I don't use it because the standalone also works under Windows.
> (I use the texlive for all the rest, btw).
>
> I believe that the documentation can be expanded to cover using a
> Context on Cygwin directly and not the Microsoft port which
> requires the usage of strange Microsoft pathnames, with C:\ and \
> seperators.
>
> Using context on cygwin for cygwin may only have been done in
> TexLive for Unix like systems, but I'd like to use and test on the
> bleeding edge MKIV. But, that proves that it can be done. I just
> don't know what was done.
>
> In this case I think it's better to use the standalone directly on
> Windows.
>
> --
> luigi
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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-10-20 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 7:52 hwitloc
2013-10-20 8:58 ` luigi scarso
2013-10-20 9:23 ` d.henman
2013-10-20 9:46 ` luigi scarso
2013-10-20 13:54 ` hwitloc
2013-10-20 14:05 ` luigi scarso
2013-10-20 16:06 ` hwitloc [this message]
2013-10-22 10:04 ` Mojca Miklavec
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=20131021010625.3284@binki \
--to=hwitloc@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).