ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: empty line before typebuffer
Date: Mon, 31 Jul 2023 19:21:59 +0200	[thread overview]
Message-ID: <2f3625f5-1f98-3bc7-9b60-7c630c04a196@fiee.net> (raw)
In-Reply-To: <d3a35479-aa46-7421-2110-9991e3b7f2b3@gmx.es>

Am 31.07.23 um 17:25 schrieb Pablo Rodriguez:
> On 7/30/23 21:50, Henning Hraban Ramm wrote:
>> Am 30.07.23 um 21:22 schrieb Wolfgang Schuster:
>>> Henning Hraban Ramm schrieb am 30.07.2023 um 21:14:
>>>> Yet another issue:
>>>>
>>>> \typebuffer always starts with a blank line.
>>>> Is this a bug, or how can I disable it?
> 
> Sorry for being too late, Hraban.
> 
> \typeinlinebuffer is probably the best option here.

Thank you, but no. I needed it for code examples in a frame.

strut=no did the trick.

Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-07-31 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 19:14 [NTG-context] " Henning Hraban Ramm
2023-07-30 19:22 ` [NTG-context] " Wolfgang Schuster
2023-07-30 19:50   ` Henning Hraban Ramm
2023-07-31 15:25     ` Pablo Rodriguez
2023-07-31 17:21       ` Henning Hraban Ramm [this message]
2023-07-30 19:23 ` Jacob Kauffmann via ntg-context

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=2f3625f5-1f98-3bc7-9b60-7c630c04a196@fiee.net \
    --to=texml@fiee.net \
    --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).