ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [***SPAM***] Re:  howto define MyRule ?
Date: Tue, 20 Mar 2012 18:59:01 +0100	[thread overview]
Message-ID: <A8A259DF-EF9B-4794-B57A-1277896BFBE9@st.estfiles.de> (raw)
In-Reply-To: <6BE309AB-420D-466C-9920-2CDA8AA1CE8C@googlemail.com>


Am 20.03.2012 um 17:45 schrieb Wolfgang Schuster:

> 
> Am 20.03.2012 um 17:35 schrieb Steffen Wolfrum:
> 
>> 
>> Am 20.03.2012 um 14:42 schrieb Wolfgang Schuster:
>> 
>>> You have to enable you own command with “rule=command” but then you have to set rulecolor and rule thickness in your own definition (best us \blackrule for this).
>> 
>> 
>> rule=command,rulecommand=\MyRule
>> 
>> instead of
>> 
>> rulecommand=\MyRule
>> 
>> hm ... this logic I didn't not yet internalize.
> 
> You have to tell context it should use your own rule instead of the default rule, it’s like “alternative=command” for other setups.


Sure, I know what you mean.
But nevertheless, isn't that already implied if I use "rulecommand=\MyRule"?
To me this already means exactly this: "tell context it should use my rule".

Steffen
___________________________________________________________________________________
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-03-20 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  9:10 Steffen Wolfrum
2012-03-20 13:42 ` Wolfgang Schuster
2012-03-20 16:35   ` Steffen Wolfrum
2012-03-20 16:45     ` Wolfgang Schuster
2012-03-20 17:59       ` Steffen Wolfrum [this message]
2012-03-20 18:49         ` [***SPAM***] " Hans Hagen
2012-03-20 19:28           ` Steffen Wolfrum

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=A8A259DF-EF9B-4794-B57A-1277896BFBE9@st.estfiles.de \
    --to=context@st.estfiles.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).