ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \definedescription[...][hang=fit] broken in latest beta?
Date: Sat, 11 Feb 2012 15:12:19 +0100	[thread overview]
Message-ID: <4F367743.3090100@web.de> (raw)
In-Reply-To: <4D38E820-827E-40A7-8ADF-F85F00A8A439@googlemail.com>

On 02/11/2012 01:46 PM, Wolfgang Schuster wrote:
> 
> Am 11.02.2012 um 13:27 schrieb Pablo Rodríguez:
> 
>> On 02/11/2012 06:48 AM, Wolfgang Schuster wrote:
>>>
>>> Am 10.02.2012 um 19:28 schrieb Pablo Rodríguez:
>>>
>>>> Hi there,
>>>>
>>>> I'm not able to compile this code using the latest beta:
>>>>
>>>> \definedescription[optionlisting][hang=fit]
>>>> \starttext
>>>> \optionlisting{range} especifica espectro
>>>> \stoptext
>>>>
>>>> Just in case it helps,
>>>
>>> 1. You need a empty line or \par at the end of the description (or use \startoptionlisting … \stopoptionlisting)
>>>
>>> 2. Change this in strc-con.mkvi
>>
>> Many thanks for your help, Wolfgang.
>>
>> I'm afraid it doesn't work here (log below). Do I have to rebuild the
>> MKIV format?
> 
> Yes because the when you run “context --make …” tex reads all source files
> and save them as memory dump with the name cont-xx.fmt on the disk which
> which is faster to read than then each file one by one. There are a few files
> which aren’t included in the format like typescripts (type-xx.mkiv) where
> you can make changes without regenerating the format.

Thanks for your help and the explanation, Wolfgang.

I'm afraid that it doesn't work even after regenerating the format
(mtxrun --selfupdate && mtxrun --generate && luatools --generate &&
context --make, as suggested by the wiki).

The error message is the following:

! Incomplete \ifx; all text was ignored after line 3.
system          > tex > error on line 0 in file : Incomplete \ifx; all
text was ignored after line 3 ...
<empty file>
<inserted text>
                \fi
<*> ./a.tex
            \stoptext
?
! Emergency stop.
system          > tex > error on line 0 in file : Emergency stop ...
<empty file>
<inserted text>
                \fi
<*> ./a.tex
            \stoptext
!  ==> Fatal error occurred, no output PDF file produced!
mtx-context     | fatal error: return code: 1
Compilation failed.

Thanks for your help,


Pablo
-- 
http://www.oudeis.tk
___________________________________________________________________________________
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:[~2012-02-11 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 18:28 Pablo Rodríguez
2012-02-11  5:48 ` Wolfgang Schuster
2012-02-11 12:27   ` Pablo Rodríguez
2012-02-11 12:46     ` Wolfgang Schuster
2012-02-11 14:12       ` Pablo Rodríguez [this message]
2012-02-11 14:20         ` Wolfgang Schuster
2012-02-11 14:34           ` Pablo Rodríguez

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=4F367743.3090100@web.de \
    --to=oinos@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).