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: listings.sty
Date: Thu, 10 Jul 2008 08:29:29 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.00.0807100025530.25751@nqv-yncgbc> (raw)
In-Reply-To: <loom.20080710T002625-996@post.gmane.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1148 bytes --]

On Thu, 10 Jul 2008, Mohamed Bana wrote:

> Peter Münster <pmlists <at> free.fr> writes:
>
>>
>> Hello,
>> I suggested to the author of the very feature rich LaTeX-Listings package,
>> Carsten Heinz, to port this package to ConTeXt, and it seems, that he is
>> interested. But before doing it, there are some questions:
>>
>> * What do Hans and other people thing about that?
>> * listings.sty uses keyval.sty, how is the proper ConTeXt-way to do the
>>   same things as keyval, or should listings stay with keyval?
>>
>> Greetings, Peter
>>
>
>
> Hi,
>
> I anyone got any status on the port?  Here's the link for the package;
> http://www.ctan.org/tex-archive/macros/latex/contrib/listings/.

I don't know the status of this port. However, Carsten Heinz no longer 
maintains listings, currently Brooks Moses does. Brooks used to be active 
in both ConTeXt and LaTeX communities and had started a project of 
converting core LaTeX functionality into ConTeXt. As such he is an ideal 
person to evaluate the feasibility of porting listings to ConTeXt. I would 
suggest writing to him to see his opinion on this.

Aditya

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2008-07-10 12:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 17:23 listings.sty Peter Münster
2004-06-28  7:38 ` listings.sty Patrick Gundlach
2004-06-28  8:03   ` listings.sty Hans Hagen
2004-06-28  8:18     ` Morten Høgholm
2004-06-28  8:39     ` Holger Schöner
2004-06-28  9:26     ` Peter Münster
2004-06-28 14:39       ` Hans Hagen
2004-06-28 17:46         ` Peter Münster
2004-06-28 21:51           ` Nikolai Weibull
2004-07-10  9:44           ` Peter Münster
2008-07-10  0:27 ` listings.sty Mohamed Bana
2008-07-10 12:29   ` Aditya Mahajan [this message]
2008-07-10 18:26   ` listings.sty nico
2008-07-10 20:34     ` listings.sty Mohamed Bana
2008-07-10 22:02       ` listings.sty Aditya Mahajan
2008-07-10 21:31     ` listings.sty Hans Hagen
2008-07-11 21:51       ` listings.sty Mohamed Bana
2008-07-11 22:53         ` listings.sty Hans Hagen
2008-07-11 22:54         ` listings.sty Aditya Mahajan

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.DEB.1.00.0807100025530.25751@nqv-yncgbc \
    --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).