ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Geeze, I might try Linux after all... (not too off-tpic I hope)
Date: Fri, 13 Jun 2008 14:09:34 +0200	[thread overview]
Message-ID: <fe8d59da0806130509j39c491ferb2c9b2b27564ccc6@mail.gmail.com> (raw)
In-Reply-To: <48524f3a.0c92100a.08c9.fffff43f@mx.google.com>

On Fri, Jun 13, 2008 at 12:42 PM, Alan Stone
<software.list.1es9s@gmail.com> wrote:
> ( Oops, pushed inadvertedly some key on my keyboard and the
> message was away while in GMail - here's the sequel... )
>
> Having heard Linux is, amongst other things, far more stable
> I might be tempted to play with it and progressively build some
> experience with it, master the beast and then switch some
> applications, amongst which ConTeXt, to it.
>
> As I presently don't know a thing about Linux, which distribution
> do you recommend ?
I have played with fedora /red-hat, opensuse/suse, debian, ubuntu, slackware .
All goods, actually I'm using ubuntu.
Maybe fedora/opensuse with kde can be confortable for you .

BTW, I don't use tex from these distro, I always put all files under
/opt/luatex , compiling when necessary ;
it's in a someway distro-independent.





-- 
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-06-13 12:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 10:28 Alan Stone
     [not found] ` <326847810806130328k73f9ed0bw4ec3ede296a29d55@mail.gmail.co m>
2008-06-13 10:42   ` Alan Stone
2008-06-13 12:09     ` luigi scarso [this message]
2008-06-13 12:38     ` Michael Hallgren
2008-06-13 13:07       ` Diego Depaoli
2008-06-13 12:53     ` Olivier Guéry
2008-06-13 13:37     ` Charles P. Schaum
2008-06-13 14:53       ` John Devereux
2008-06-14  6:20         ` Alan Stone
2008-06-14  7:29           ` Alan Stone
2008-06-14  7:40             ` Taco Hoekwater
2008-06-14  9:07               ` luigi scarso
2008-06-14  9:38                 ` Matija Šuklje
2008-06-14 11:25               ` John Culleton
2008-06-19 19:40                 ` Alan Stone
2008-06-20  6:37                   ` Wolfgang Schuster
2008-06-20  6:45                     ` Alan Stone
2008-06-20  7:03                   ` Mojca Miklavec
2008-06-20  8:17                     ` Alan Stone
2008-06-20 12:21                       ` Alan Stone
2008-06-20 12:27                         ` Wolfgang Schuster
2008-06-20 13:39                           ` Alan Stone
2008-06-20 14:31                             ` Mojca Miklavec
2008-06-20 16:21                               ` Alan Stone
2008-06-20 21:05                                 ` Aditya Mahajan
2008-06-21  7:44                                   ` Alan Stone

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=fe8d59da0806130509j39c491ferb2c9b2b27564ccc6@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).