ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	"Philipp A." <flying-sheep@web.de>
Subject: Re: context command line interface documentation?
Date: Wed, 20 Nov 2019 09:29:09 +0100	[thread overview]
Message-ID: <64d0929c-064d-5608-4da6-b6b17f21668a@xs4all.nl> (raw)
In-Reply-To: <CAN8d9gm5r1y3qan8qx=HGxVa7h2qMG6-MZTOk96Em3bxAD4aNA@mail.gmail.com>

On 11/19/2019 8:10 PM, Philipp A. wrote:
> That’s pretty cool, overriding that hook allows to build a ConTeXt 
> language server for editors like VS Code! 
> https://microsoft.github.io/language-server-protocol/

i looked at that a while ago but imo the whole server model is pretty 
complex (maintaince and compatibility hell) for something as simple as 
an edit-run-cycle .. i wait till vscode has a simple filetype related 
hit-this-key-and-run feature (last time i checked it was global for all 
file types)

> Sadly I’m still a bit lost: When calling `context file_with_error.tex`, 
> I see “This is LuaTeX, Version 1.10 … tex error on line … ?” and it 
> waits for input.
> You said that context stops when encountering an error which isn’t the 
> case for me. Any ideas why?

i'm talking lmtx

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2019-11-20  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 11:14 Philipp A.
2019-11-12 12:21 ` Hans Hagen
2019-11-12 17:35   ` Henning Hraban Ramm
2019-11-18 22:11   ` Philipp A.
2019-11-19  9:16     ` Hans Hagen
2019-11-19  9:31     ` Hans Hagen
2019-11-19 19:10       ` Philipp A.
2019-11-20  8:29         ` Hans Hagen [this message]

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=64d0929c-064d-5608-4da6-b6b17f21668a@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=flying-sheep@web.de \
    --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).