ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jacob Peck <gatesphere@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: UWIN?
Date: Fri, 14 Jun 2013 17:51:22 -0400	[thread overview]
Message-ID: <51BB905A.9040407@gmail.com> (raw)
In-Reply-To: <CALBOmsbeU7QiMNW4XRqq1fjKjrP34jSoSP+HpsnaL=amUi4sGw@mail.gmail.com>

On 6/14/2013 4:14 PM, Mojca Miklavec wrote:
> On Fri, Jun 14, 2013 at 9:13 PM, Jacob Peck wrote:
>> On 6/14/2013 3:05 PM, Mojca Miklavec wrote:
>>
>> Now that Jacob mentioned it: I didn't think of the fact that one might
>> not necessarily need special cygwin binaries to run ConTeXt in cygwin.
>> If a simple modification in first-setup.sh and setuptex can do the
>> job, feel free to suggest the change (platform detection).
>>
>> My changes were simple - I used the setuptex file that came with standalone,
>> and tweaked it ever so slightly.
>>
>> https://gist.github.com/gatesphere/0afaf5c2c647430ff653
> So basically all you did was replacing platform detection with
>      platform="mswin"
> and commented out three lines of code that notify about the change?
> (Did you just find those lines annoying or did they actually fail to
> work?)
I just found them annoying - precisely because they worked :p
> Just curious: what does
>      uname -s
>      uname -m
> return on cygwin or what is the best way to detect windows in "shell"?
> (I believe that should be easy enough.)
$ uname -s; uname -m; uname -o
CYGWIN_NT-5.1
i686
Cygwin

You could test if `uname -s` starts with "CYGWIN", or if `uname -o` 
equals "Cygwin"... another way is to check $OSTYPE:

$ echo $OSTYPE
cygwin

>> Save that as .setuptex in ~ (home directory) then add the line
>>
>> source /home/PeckJ/.setuptex /cygdrive/c/context/tex
>> to .bashrc, and you should be good to go.
> In that case I would use
>      export PATH=/cygdrive/c/context/tex/texm-mswin/bin:$PATH
> instead, but of course it's your choice.
Is that all the script does?  I've never read it completely, just 
tweaked it until it worked.

Ah well, my setup works just fine :)

-->Jake
> Mojca
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________


  reply	other threads:[~2013-06-14 21:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  0:46 UWIN? Bill Meahan
2013-06-14  7:07 ` UWIN? luigi scarso
2013-06-14  7:40 ` UWIN? Hans Hagen
2013-06-14 10:58   ` UWIN? Bill Meahan
2013-06-14 12:21     ` UWIN? Jacob Peck
2013-06-14 19:05 ` UWIN? Mojca Miklavec
2013-06-14 19:13   ` UWIN? Jacob Peck
2013-06-14 20:14     ` UWIN? Mojca Miklavec
2013-06-14 21:51       ` Jacob Peck [this message]
2013-06-15 15:48       ` UWIN? Bill Meahan

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=51BB905A.9040407@gmail.com \
    --to=gatesphere@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).