ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Rik Kabel <context@rik.users.panix.com>
Subject: Re: How can I remove a blank leading line from a buffer
Date: Mon, 13 Aug 2018 18:04:12 +0200	[thread overview]
Message-ID: <1bcbc82c-b9e3-4055-8e18-4786cdd8cc68@gmail.com> (raw)
In-Reply-To: <c2d5ef02-54c0-c26e-8fd9-7d8b70a51489@rik.users.panix.com>


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



Rik Kabel schrieb am 13.08.18 um 16:28:
> Hans,
>
> That works for the over-simplified case here, but fails in practice. 
> For a \startnarrower[left] paragraph, the mark is still in the main 
> margin, not the 'margin' of the narrowed paragraph. Also, the 
> placement of the text in the margin is wrong and not easily controlled 
> as with \llap and \rlap. The code started out more like:
>
>     \define\Mark{\color[middlegray]{\hskip.6cm\itb¿\ }}
>     \setwidthof{\Mark}\to\MarkWidth
>     ...
>     \starttexdefinition stopBufTest
>       \startluacode
>     buffers.prepend("TestBuffer","\\dontleavehmode\\llap{\\Mark}")
>       \stopluacode
>       \setupnarrower[left=\MarkWidth]
>       \startnarrower[left,right]
>       \startparagraph
>         \inlinebuffer[TestBuffer]
>       \stopparagraph
>       \stopnarrower
>       \egroup
>     \stoptexdefinition
>

Hi Rik,

what do you want to achieve and why do you need a buffer for it?

Wolfgang


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

[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-08-13 16:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13  3:18 Rik Kabel
2018-08-13  3:44 ` Aditya Mahajan
2018-08-13  3:46 ` Henri Menke
2018-08-13  7:02   ` Hans Hagen
2018-08-13  7:01 ` Hans Hagen
2018-08-13 14:28   ` Rik Kabel
2018-08-13 16:04     ` Wolfgang Schuster [this message]
2018-08-13 17:09       ` Rik Kabel
2018-08-13 17:46         ` Wolfgang Schuster
2018-08-13 18:27           ` Rik Kabel
2018-08-13 19:52             ` Wolfgang Schuster
2018-08-13 22:43               ` Rik Kabel
2018-08-14 14:46                 ` Rik Kabel
2018-08-15  3:31                   ` Aditya Mahajan
2018-08-15  7:07                     ` Hans Hagen
2018-08-15 21:46                       ` Rik Kabel
2018-08-16 14:55                         ` Aditya Mahajan
2018-08-16 20:02                           ` Rik
2018-08-13 16:15     ` Rik Kabel
2018-08-13 17:51     ` Rik Kabel

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=1bcbc82c-b9e3-4055-8e18-4786cdd8cc68@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=context@rik.users.panix.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).