ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: rene hassel <rene0hassel@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: ntg-context Digest, Vol 63, Issue 7
Date: Sun, 6 Sep 2009 09:29:09 +0200	[thread overview]
Message-ID: <e93ff7b70909060029lb166322y5c4377dd3863427@mail.gmail.com> (raw)
In-Reply-To: <mailman.1606.1252109439.3069.ntg-context@ntg.nl>


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

Hello Everybody,


this "innerproduct" goes well:


# begin:

\define[2]\innerprod{\langle#1,#2\rangle}


 \starttext

\innerprod{\,x}{y} + z

\stoptext

# end.


best regards,


Rene'




>
> ------------------------------
>
> Message: 6
> Date: Fri, 4 Sep 2009 17:10:29 -0700
> From: "Guilherme P. de Freitas" <guilherme@gpfreitas.com>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: [NTG-context] Problems with inner products
> Message-ID:
>        <a193bbb50909041710v274ba490odbe40413cf851def@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi everybody,
>
> I am trying to define a command for inner products. I would like to
> type $\innerprod{x, y}$ and obtain in the output <x, y>. Now, I
> defined
>
> \define[2]\innerprod
>  {\langle #1, #2 \rangle}
>
> but then, when I used the command, I got some weird behavior: the next
> character after "y" would "jump in" the inner product. For example,
> when writing
>
> $\innerprod{x, y} + z$
>
> I was hoping to obtain as an output
>
> <x, y> + z
>
> But I got as an output
>
> <x, y +> z
>
> I am using the ConTeXt that came with MacTeX 2008 (I downloaded it a
> few days ago).
>
> Best,
>
> Guilherme
>
> --
> Guilherme P. de Freitas
> http://www.gpfreitas.com
>
>
> ------------------------------
>
>
> ___________________________________________________________________________________
> 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  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
>
> ___________________________________________________________________________________
>
>
> End of ntg-context Digest, Vol 63, Issue 7
> ******************************************
>

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

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

           reply	other threads:[~2009-09-06  7:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.1606.1252109439.3069.ntg-context@ntg.nl>]

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=e93ff7b70909060029lb166322y5c4377dd3863427@mail.gmail.com \
    --to=rene0hassel@gmail.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).