ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in math arrows
Date: Wed, 10 Jan 2018 12:46:13 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.20.1801101245360.1680@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <5A564292.4080503@gmail.com>

On Wed, 10 Jan 2018, Wolfgang Schuster wrote:

>
>>  Aditya Mahajan <mailto:adityam@umich.edu>
>>  10. Januar 2018 um 17:27
>>  Hi,
>>
>>  There is a bug in extensible arrows. The syntax of extensible arrows is:
>>
>>  \xleftarrow{below}{top}
>>
>>  but when the optional argument is used
>>
>>  \xleftarrow[small]{A}{B}
>>
>>  then A ends up on the top and B on the bottom.
>
> The "x" commands change the position of both texts and when you change
> the instance for the command the reversed order is overwritten (search for
> the order key in math-stc.mkvi).
>
> \starttext
>
> $\xleftarrow{A}{B}$
>
> $\mleftarrow{A}{B}$
>
> \stoptext

I would still consider it a bug :-) Either order is fine but it should be 
used consistently.

Aditya
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2018-01-10 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 16:27 Aditya Mahajan
2018-01-10 16:42 ` Wolfgang Schuster
2018-01-10 17:46   ` Aditya Mahajan [this message]

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=alpine.LNX.2.20.1801101245360.1680@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).