ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Salil Sayed <salilsay@yahoo.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: streams! atleast the left||right synchronization mechanism
Date: Fri, 9 Apr 2010 01:18:03 -0700 (PDT)	[thread overview]
Message-ID: <20150.17202.qm@web57507.mail.re1.yahoo.com> (raw)
In-Reply-To: <4BBEDCEF.3000001@googlemail.com>


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

Thanks Wolfgang, this works. I knew this from a previous discussion but I was trying the line in m-streams.tex

regards,

Salil




________________________________
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Sent: Fri, April 9, 2010 10:53:19 AM
Subject: Re: [NTG-context] streams! atleast the left||right synchronization mechanism

 Am 09.04.10 09:45, schrieb Salil Sayed: 
> 
>Hi,
>
>>As I am moving from mkII to mkIV with my thesis manuscript, I need to
>make the 'left||right synchronization mechanism' to work. I worked
>beautifully in mkII. I looked in the source of the module but could not
>make out where the issue is. I errors I get today begin like this.
>
Remove the \endinput at the begin of the file (line 28) in page-str.mkiv
and remake the format.

what
>is this (  \v!  ) thing? where can I get the clues? Does it come from
>Tex or LuaTex programming?
>http://wiki.contextgarden.net/System_Macros/Scratch_Variables

Wolfgang


      

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

[-- Attachment #2: Type: text/plain, Size: 486 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2010-04-09  8:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 13:00 minimal example of some problems Michael Saunders
2010-04-08 16:45 ` libertine otf file not recognised Salil Sayed
2010-04-08 18:23   ` Taco Hoekwater
2010-04-08 20:58     ` Wolfgang Schuster
2010-04-09  7:18       ` Salil Sayed
2010-04-09  7:45       ` streams! atleast the left||right synchronization mechanism Salil Sayed
2010-04-09  7:53         ` Wolfgang Schuster
2010-04-09  8:18           ` Salil Sayed [this message]
2010-07-04  9:54       ` libertine otf file not recognised Vnpenguin
2010-07-04 11:10         ` Wolfgang Schuster
2010-07-04 11:27           ` luigi scarso
2010-07-04 16:57           ` Vnpenguin
2010-07-04 17:00             ` Wolfgang Schuster
2010-07-04 17:44               ` Vnpenguin
2010-07-04 17:51                 ` Wolfgang Schuster
2010-07-04 17:56                   ` Vnpenguin
2010-07-04 18:03                     ` Wolfgang Schuster
2010-07-04 18:07                       ` Vnpenguin
2010-07-04 21:07                       ` 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=20150.17202.qm@web57507.mail.re1.yahoo.com \
    --to=salilsay@yahoo.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).