ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonathan Barchi <barchij@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: etexshow and generation of cont-en.xlm (cont-XX.xml)?
Date: Wed, 20 Mar 2013 12:22:55 -0400	[thread overview]
Message-ID: <CAFBQp-tU0SnkxNgyPY2U7g2Z0-9UFMy_9c1VA3km7BMcY8f5EA@mail.gmail.com> (raw)
In-Reply-To: <5147A05B.7000406@wxs.nl>

On Mon, Mar 18, 2013 at 7:16 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 3/18/2013 11:35 PM, Jonathan Barchi wrote:
>>
>> Hi all,
>>
>> I'm using the emacs package etexshow to provide a quick ConTeXt
>> command reference in EMACS. This utility parses the interface file
>> cont-en.xml (for english, in my case) and uses the contents to provide
>> a basic dictionary of available commands.
>>
>> In the documentation for etexshow, there is a reference to being able
>> to generate a complete interface description (the aforementioned xml
>> file) like so:
>>
>> ";; There is still an xml-file shipped with this code. Usually you would
>> ;; generate the xml-file with 'texexec'ing the file setupe.tex. Then you
>> ;; will get the cont-en.xml file that can (could) be used as an input for
>> ;; this etexshow. But for now, this won't work. It will work rsn."
>>
>> It is not clear whether that file (setupe.tex or setup.tex) is/was
>> supposed to be shipped with etexshow or was supposed to be a part of
>> context. I've searched and found a few references to this problem, but
>> never a definitive answer, so if anyone knows the answer to these
>> questions I would love to know!!
>>
>> 1. Is the referenced setup(e).tex a file that was previously shipped
>> with ConTeXt - presumably mkii since the author refers to texexec - or
>> would this be something the author would have included with etexshow
>> itself?
>>
>> 2. Is the interface file, e.g. cont-en.xml, auto-generated from all of
>> the defined macros in ConTeXt, or is that file hand-written as
>> metadata to accompany the source-code definitions?
>
>
> the xml file is the master file (but I admit that it's a bit behind)
>
> if you only need the commands then the mult-def.lua files are better, also
> because they contain low level commands and primitives (it's what I use to
> generate files for scite where we have a rather advanced lexer)

I'll take a look at those files, thanks!

Is that scite code free software? I'd love to take a look at how you generate
the files for it, and/or how its lexer is implemented.

>> 3. Since self-documentation is a goal of the project, is it possible
>> to generate something akin to the interface file that presents a
>> snapshot of all commands known to context at a given time, for use in
>> things like etexshow or other tools? If so, is it possible to do this
>> with modules loaded to see what they additionally define?
>
>
> we can add a --emacs to mtx-interfaces.lua if something other than xml is
> needed .. so, what does emacs need?

I'm still figuring this part out.  Emacs is quite modular, so I'm not
sure what the
best approach is yet. AUCTEX implements syntax highlighting internally, in
a sub-package called font-latex (that does work reasonably well for ConTeXt
too), but there is also more sophisticated support for LaTeX that doesn't cross
over to context.

There are more general solutions for lexing, like semantic, which might be
the better way to go. Semantic has an internal port of bison that can use BNF
grammar descriptions, but some reading suggests that this can't be done for
*TeX. It can also be fed tags by a regexp parser or an external
utility like ctags.

I'm quite new to all this, so if anyone out on the mailing list with more
experience wants to jump in with advice or corrections I'm all ears! I'm also
working on my dissertation, so time is limited (at least for the next couple
months).

- Jon

>> Thanks in advance for any help! I'm hoping to use any information I
>> get to update etexshow, if possible, and maybe update the ConTeXt
>> support in AUCTEX as well. I think it would be really cool if AUCTEX
>> could reach out at compile or run time and pull in macro definitions
>> from the installed environment, for example.
>
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>                                              | www.pragma-pod.nl
> -----------------------------------------------------------------
___________________________________________________________________________________
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-03-20 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 22:35 Jonathan Barchi
2013-03-18 23:16 ` Hans Hagen
2013-03-20 16:22   ` Jonathan Barchi [this message]
2013-03-20 16:54     ` Marcin Borkowski
2013-03-20 20:32     ` Hans Hagen
2013-03-19  4:06 ` hwitloc

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=CAFBQp-tU0SnkxNgyPY2U7g2Z0-9UFMy_9c1VA3km7BMcY8f5EA@mail.gmail.com \
    --to=barchij@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).