ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Werner Hintze" <w.hintze@posteo.eu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Intsalling modules - once more
Date: Tue, 19 Aug 2014 09:11:19 +0200	[thread overview]
Message-ID: <45025ECF-D1BD-48A4-A978-24059C1A8056@posteo.eu> (raw)
In-Reply-To: <98F28D87-ACBF-41E6-BD44-F5E7BC050471@gmail.com>

I made a new step: I found out how to change the script in Texnicle. It 
was for MKII, now I changed it to MKIV. It works well now. The problem 
is just the module fancybreak. When I try to use it, I get the message 
»Undefined control sequence«. Some lines before I find: »resolvers    
    > modules > 'fancybreak' is already loaded«.

This doesn’t happen with the stand alone. What is wrong here?

On 18 Aug 2014, at 19:40, Wolfgang Schuster wrote:

> Am 18.08.2014 um 19:03 schrieb Werner Hintze <w.hintze@posteo.eu>:
>
>> On 18 Aug 2014, at 18:17, Aditya Mahajan wrote:
>>
>>> MkIV will not load .mkii files. What is the exact command that you 
>>> use to run context?
>>
>> Aha! You found the point! I use Texnicle as editor and the context 
>> engine Texnicle provides. It calls texexec... But it’s not enough 
>> to put here context. The problem remains, that I get the message, 
>> that fancy break is undefined.
>
> What happens when you process this example with Texnicle:
>
> \usemodule[fancybreak]
>
> \starttext
>
> \input knuth
>
> \fancybreak{$***$}
>
> \input ward
>
> \stoptext
>
> Wolfgang
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2014-08-19  7:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18  8:55 Akira Kakuto
2014-08-18 13:17 ` Werner Hintze
2014-08-18 13:31   ` Aditya Mahajan
2014-08-18 14:41     ` Werner Hintze
2014-08-18 14:56       ` Wolfgang Schuster
2014-08-18 16:04         ` Werner Hintze
2014-08-18 15:05       ` Aditya Mahajan
2014-08-18 16:04         ` Werner Hintze
2014-08-18 16:17           ` Aditya Mahajan
2014-08-18 17:03             ` Werner Hintze
2014-08-18 17:40               ` Wolfgang Schuster
2014-08-19  7:11                 ` Werner Hintze [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-18  8:15 Werner Hintze
2014-08-18 13:42 ` Wolfgang Schuster
2014-08-18 15:55   ` Werner Hintze

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=45025ECF-D1BD-48A4-A978-24059C1A8056@posteo.eu \
    --to=w.hintze@posteo.eu \
    --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).