ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to start a \definedescription-defined description's body on a new line, not the same as the description's header?
Date: Fri, 16 Oct 2015 10:13:13 +0200	[thread overview]
Message-ID: <242481DC-1274-462E-B8CD-DBEA83F90B19@gmail.com> (raw)
In-Reply-To: <HE1PR06MB11320607A1F91D8015373364F5340@HE1PR06MB1132.eurprd06.prod.outlook.com>


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

Hi Louis,

II guess what you need is the keyword

	alternative=top

in the setup of your descritiption.

Best regards: OK

> On 09 Oct 2015, at 18:13, Louis Strous <Louis.Strous@intellimagic.com> wrote:
> 
> With
>  
> [start sample]
> \definedescription[cmddescription][headstyle=bold,width=broad,style=normal,align=flushleft,alternative=hanging,margin=1cm]
>  
> ...
>  
> \startcmddescription{mycommand}
>  
> This is a very useful command.  It knows just what to do, and you don't even have to specify any options!
>  
> \stopcmddescription
> [end sample]
>  
> the text "This is a very useful command" begins on the same line as the "mycommand" header.  I want the text to begin on the next line, so that "mycommand" is on a line of its own.  How should I adjust the \definedescription command to achieve this?  I've tried all kinds of things with the 'before', 'inbetween', 'after', 'indentnext', 'command', and 'headcommand' options of the \definedescription command (based on http://wiki.contextgarden.net/Command/setupdescriptions <http://wiki.contextgarden.net/Command/setupdescriptions>), using \par, \crlf, and \vspace, but didn't get the desired results.
>  
> Regards,
> Louis Strous
>  
> IntelliMagic - Availability Intelligence
> T: +31 (0)71-579 6000
> www.intellimagic.com <http://www.intellimagic.com/>
>  
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage  : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / http://tex.aanhet.net <http://tex.aanhet.net/>
> archive  : http://foundry.supelec.fr/projects/contextrev/ <http://foundry.supelec.fr/projects/contextrev/>
> wiki     : http://contextgarden.net <http://contextgarden.net/>
> ___________________________________________________________________________________


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

[-- Attachment #2: Type: text/plain, Size: 485 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:[~2015-10-16  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 16:13 Louis Strous
2015-10-16  8:13 ` Otared Kavian [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=242481DC-1274-462E-B8CD-DBEA83F90B19@gmail.com \
    --to=otared@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).