ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: space before/after colored framed text
Date: Thu, 18 Aug 2016 20:58:32 +0200	[thread overview]
Message-ID: <ad2f1533-262e-518a-d9a3-033e02e6fe0d@gmx.es> (raw)
In-Reply-To: <d2e21ea6-8970-6033-2dc5-089fd9789aff@free.fr>

On 08/17/2016 11:59 PM, Jean-Pierre Delange wrote:
> Thank you very much Pablo !
> 
> As a beginner I don't understand very well the complete meaning of 
> "minimal" working sample, perhaps because my own code is full of 
> mistakes and compiles sometimes with somes issues.

Hi Jean-Pierre,

a minimal sample is the code that contains only the commands with
arguments and text required to reproduce the issue you experience.

It is also a working sample, which means anyone should be able to
compile it only by copying and pasting your code in a text file and
hitting the compilation button (keystroke or simply the compilation
command).

Compilation should run automatically, with no compilation error (unless
you hit a bug in ConTeXt).

But the way of doing minimal working samples is to copy your source in
another file. Ask yourself what do you want to achieve or show to other
users in the mailing list. And remove what isn’t required for that.

Start thinking that you may be doing it wrong if it takes more than 20
lines. Be sure that it should be another way with a sample of more than
50 lines. (Well, it isn’t a immutable law, but in ConTeXt “small is
beautiful” :-).)

My own experience is that elaborating minimal working samples takes
time. Especially when (you think) you found a bug in ConTeXt. Since we
use ConTeXt for books (or larger projects than papers), the issue is
always to remove all unnecessary code and text.

As you know far better than myself: we all learn to do things by doing
them («ἃ γὰρ δεῖ μαθόντας ποιεῖν, ταῦτα ποιοῦντες μανθάνομεν»). Don’t
worry, just start doing ;-).

> The way of making space before and after the frame is now very clear to 
> me, as well as the way to resize the font size inside a frame.

Sometimes, setting a bit smaller interline space solves the problem.
Especially, when the frame contains many lines of text.

> For my own text between \starttext and \stoptext is not an automatic 
> false text, I didn't understand why the code provides this huge blank 
> space before the frame. Either didn't I understand why sometimes a frame 
> completely disappears when I supprime a footnote previously written 
> inside the frame (but it is another topic...).

But now it is clear that frames aren’t split across pages, isn’t it?

The issue with the frame disappearance after a footnote removal seems
weird. Are you sure that only the footnote has been removed? (But start
a new thread for that [a brand new message]).

I hope it helps,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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:[~2016-08-18 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 12:20 \startalign \stopalign equation number placement seems wrong Mikael P. Sundqvist
2016-08-17 13:23 ` Otared Kavian
2016-08-17 14:36   ` space before/after colored framed text Jean-Pierre Delange
2016-08-17 15:14     ` Thomas A. Schmitz
2016-08-17 15:57       ` Jean-Pierre Delange
2016-08-17 17:02         ` Pablo Rodriguez
2016-08-17 21:59           ` Jean-Pierre Delange
2016-08-18 18:58             ` Pablo Rodriguez [this message]
2016-08-28 15:08   ` \startalign \stopalign equation number placement seems wrong Mikael P. Sundqvist

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=ad2f1533-262e-518a-d9a3-033e02e6fe0d@gmx.es \
    --to=oinos@gmx.es \
    --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).