ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Philipp A." <flying-sheep@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context command line interface documentation?
Date: Mon, 18 Nov 2019 23:11:25 +0100	[thread overview]
Message-ID: <CAN8d9g=18Q4ZUdGhniVMuj1wYtzmzEyH0jgb_L5gLdusRkseRQ@mail.gmail.com> (raw)
In-Reply-To: <dd467163-e868-0eae-da27-7a8f78d4c477@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2667 bytes --]

Hi Hans,

Very sorry that it was phrased so negatively. I like ConTeXt enough that I
wrote my master’s thesis in it, and am now writing my doctor’s thesis in it.
I had a long day that day and didn’t expect to have to dive so deep to find
out what I want is impossible. I think my language mostly reflected my
thought process going through it, not lack of respect towards your work.
I hope my bug report here is still helpful and provides all information
necessary to improve ConTeXt, and would like to help if there’s an easy way
to contribute (Pull requests?)

context --silent -nostatistics
>

Thank you! I see it’s in the “experts” section in mtx-context.xml. I added
it to the wiki, as it seems the most immediately useful (and non-experty)
among those options.
I think it would be best if the help would just be generated from that file
to reduce the sources of truth in existence.


> context quits at the first error as recovering is (1) seldom useful, (2)
> can interfere badly with tex/mp/lua and make things worse), (3) context
> tries to show a bit more precise location where the erro comes from (not
> always easy in tex) ... some of these modes originate in paper terminal
> times and it's very unlikely that context will change it's current way of
> doing things
>

What you’re describing is the behavior I’m trying to achieve. The error
location reporting works for me, but context will still continue after an
error for me:
If I don’t specify --nonstopmode or so it’ll try to recover, and even when
I specify it, there will be other output after the error.

>  What’s a “list”? comma separated? Do I need string delimiters?
>
> comma separated and only quoted when spaces (as usual with spaces)
>

You mean quoted as in “to prevent my terminal from interpreting it wrong”,
right?
Not that the script actually expects quotes in argv?

grepping for stats will bring you to nostats and nostatistics and "context
> --help --expert" shows that flag too
>

All of which is undocumented. I’d like to help here, so I added it to the
wiki, but it would be useful to mention this in --help, too!

remarks like the last one are very unlikely to trigger people to write
> additional documentation (a manual or wiki page) ... context comes for
> free, support comes for free ... there is not much one can demand i guess
>
> Hans
>

Again, I’m really sorry! I’d like to help, but I don’t have the time
currently for more than drive-by pull requests and wiki edits. I’m doing
the latter and if the former is possible, I’ll try my hand. Is it?

Best, Philipp

[-- Attachment #1.2: Type: text/html, Size: 3698 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2019-11-18 22:11 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. [this message]
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

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='CAN8d9g=18Q4ZUdGhniVMuj1wYtzmzEyH0jgb_L5gLdusRkseRQ@mail.gmail.com' \
    --to=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).