From: Oliver Buerschaper <oliver.buerschaper@mpq.mpg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug
Date: Tue, 15 Feb 2011 10:09:43 +0100 [thread overview]
Message-ID: <65759749-E672-4F51-A37C-844724F2F694@mpq.mpg.de> (raw)
In-Reply-To: <4D59B00E.40904@wxs.nl>
>>> I was wondering because not too long ago (e.g. 2010.11.12 18:22 MKIV) this
>>> didn't happen… are included files now automatically terminated by an implicit
>>> "\par"? Personally I would find that confusing.
>>
>> No answer to your question, just a workaround:
>>
>> \starttext
>> \section{Paragraph}
>> \input tufte
>> \input tufte
>>
>> \section{No paragraph}
>> {\endlinechar=-1 \input tufte }
>> \input tufte
>>
>> \section{Limitations of this workaround}
>> {\endlinechar=-1 \input knuth }
>> \input knuth
>> \stoptext
>
>
> can you test again?
Fixed. Thanks!
Oliver
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-02-15 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 23:06 Bug Oliver Buerschaper
2011-02-13 23:25 ` Bug Wolfgang Schuster
2011-02-14 11:25 ` Bug Oliver Buerschaper
2011-02-14 17:34 ` Bug Peter Münster
2011-02-14 22:43 ` Bug Hans Hagen
2011-02-15 9:09 ` Oliver Buerschaper [this message]
2011-02-14 18:08 ` Bug Wolfgang Schuster
2011-02-14 18:13 ` Bug Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
1998-09-13 11:03 Bug 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=65759749-E672-4F51-A37C-844724F2F694@mpq.mpg.de \
--to=oliver.buerschaper@mpq.mpg.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).