ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: James Fisher <jameshfisher@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setbreakpoints
Date: Thu, 4 Mar 2010 14:40:54 +0000	[thread overview]
Message-ID: <771da05a1003040640j62c1b544sb392946631a6f2d6@mail.gmail.com> (raw)
In-Reply-To: <4B8EEC34.9010405@gmail.com>


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

*tumbleweed*

On Wed, Mar 3, 2010 at 11:09 PM, Vyatcheslav Yatskovsky <
yatskovsky@gmail.com> wrote:

> Hi Wolfgang,
>
> To be serious, what  \setbreakpoints[] do? I want to wikify this command.
>
> Vyatcheslav
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 1385 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-03-04 14:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.607.1267648881.26807.ntg-context@ntg.nl>
2010-03-03 21:47 ` Occasional words sticking out from flush-right Vyatcheslav Yatskovsky
2010-03-03 21:53   ` Arthur Reutenauer
2010-03-03 23:19     ` James Fisher
2010-03-04  0:08       ` Aditya Mahajan
2010-03-04  2:35         ` James Fisher
2010-03-04  4:06           ` Aditya Mahajan
2010-03-04 14:39             ` James Fisher
2010-03-04 17:11               ` Aditya Mahajan
2010-03-04 17:15                 ` luigi scarso
2010-03-04 17:30                   ` Aditya Mahajan
2010-03-04 18:43                     ` luigi scarso
2010-03-04 17:50                 ` James Fisher
2010-03-04  7:10           ` luigi scarso
2010-03-04 14:25             ` James Fisher
2010-03-04 18:42               ` luigi scarso
2010-03-04 19:44                 ` James Fisher
2010-03-04 20:04                   ` Aditya Mahajan
2010-03-04 20:47                   ` luigi scarso
2010-03-04 23:31                     ` James Fisher
2010-03-04 23:36                       ` Aditya Mahajan
2010-03-04 23:47                         ` James Fisher
2010-03-05  9:30                   ` luigi scarso
2010-03-03 23:09 ` setbreakpoints Vyatcheslav Yatskovsky
2010-03-04 14:40   ` James Fisher [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=771da05a1003040640j62c1b544sb392946631a6f2d6@mail.gmail.com \
    --to=jameshfisher@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).