ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: roadmap
Date: Thu, 17 May 2018 17:47:48 +0200	[thread overview]
Message-ID: <2FF60B27-DF01-42B9-8D3C-54CD2531CA2A@gmail.com> (raw)
In-Reply-To: <CAMHZ1daCeQTK3itUx-NCTFL9e9=Dmu8p=OsSFaQcJTCiShmXOQ@mail.gmail.com>

Hi Mohammad Hossein,

Thanks for your work regarding the RawSteps! 
However I tried just now the examples you have on github, but it seems that it does not work out of the box: ConTeXt reports an error at line 114 of p-rsteps.tex, complaining about an « Undefined control sequence » which points to
\catcode`\^^M=\active

Maybe you have fixed the issue now, but regarding the feature request put forward by Fabrice, I agree with him that such a stepping feature would be nice to have in mkiv, since the steps commands which exist now cannot be used in all circumstances.

Best regards: OK

> On 17 May 2018, at 16:24, Mohammad Hossein Bateni <bateni@gmail.com> wrote:
> 
> Fabrice,
> 
> Accepting the caveats Hans pointed out for problematic spacing and some issues with references, you might find [https://github.com/bateni/rawsteps-mkiv] useful.  I ported RawSteps to MkIV and have used it in a few presentations.  The version on github might be buggy, but a good start if you really insist on using RawSteps.

___________________________________________________________________________________
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:[~2018-05-17 15:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 15:17 roadmap Hans Hagen
2018-05-14 19:36 ` roadmap Henning Hraban Ramm
2018-05-14 21:26   ` roadmap Hans Hagen
2018-05-15  9:01     ` roadmap MF
2018-05-14 22:52 ` roadmap Henri Menke
2018-05-14 23:34   ` roadmap Hans Hagen
2018-05-16  5:38     ` roadmap Henri Menke
2018-05-16  6:24       ` roadmap Joseph Canedo
2018-05-16  7:28       ` roadmap Hans Hagen
2018-05-14 23:41   ` roadmap luigi scarso
2018-05-15 19:17 ` roadmap Pablo Rodriguez
2018-05-15 21:26   ` roadmap Hans Hagen
2018-05-16 15:18     ` roadmap Pablo Rodriguez
2018-05-16 19:14 ` roadmap Fabrice L
2018-05-17 13:06   ` roadmap Hans Hagen
2018-05-17 14:24     ` roadmap Mohammad Hossein Bateni
2018-05-17 15:47       ` Otared Kavian [this message]
2018-05-17 16:50         ` roadmap Hans Hagen
2018-05-15  6:15 roadmap Christoph Reller
2018-05-15  6:23 ` roadmap luigi scarso
2018-05-15  6:36 ` roadmap Hans Hagen
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` roadmap luigi scarso
2018-05-18  9:54 roadmap Christoph Reller

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=2FF60B27-DF01-42B9-8D3C-54CD2531CA2A@gmail.com \
    --to=otared@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).