![](https://secure.gravatar.com/avatar/5955e8e90611e77ccbfc7721b6112027.jpg?s=120&d=mm&r=g)
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