ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: breakpoints in verbatim text
Date: Fri, 18 Aug 2023 13:19:20 +0200	[thread overview]
Message-ID: <e59809c3-414a-561e-9f78-e30ba59d79a0@xs4all.nl> (raw)
In-Reply-To: <54f222a3-fbf7-e5dc-4dc7-71c4ddfc7d1d@gmail.com>

On 8/18/2023 1:02 PM, Wolfgang Schuster wrote:
> Alex Leray schrieb am 18.08.2023 um 12:19:
>> Hello Wolfgang,
>>
>> Le 17/08/23 à 18:56, Wolfgang Schuster a écrit :
>>> Is it correct all your listing are HTML code and you need line breaks 
>>> for the entries of the href attributes?
>>
>> The content is from a dutch net-artist artist from the early days of 
>> the public web, and is often (volontary) mixing different natural nd 
>> machine langages. Not all snippets are HTML, but most of them are some 
>> sort of HTML pidgin.
> 
> 
> I see, the typing environment is in this case the safest option to 
> ensure special characters like % remain i the output.
> 
> For simple text without special characters you could have switched to 
> the lines environment and use a monospaced but
> I wouldn't trust it here (even when you enable \asciimode).
> 
> 
>>> Syntax highlighting of the code listing isn't needed in your case.
>>
>> No, I don't need syntax highlighting
>>
>> My problem is solved using manual zero width spaces at the moment but 
>> I'd be interested to find a more structural solution.
>>
>> Checking at the Context source code I would have thought that 
>> breakpoints were possible withing typing env. See
>>
>> https://source.contextgarden.net/tex/context/base/mkiv/buff-ver.mkiv?search=typing#l51
>>
>> It would be interesting to document on the wiki that behavior, which I 
>> can do later when my understanding is better.
> 
> The typing environment disables the breakpoint (and a few other) 
> mechanism because they can lead to undesired
> side effects but Hans suggestion to provide a hook which can be used to 
> re-enable the feature, e.g.
> 
>      \startsetups [typing:mine]
>          \setbreakpoints[compound]
>      \stopsetups
> 
>      \setuptyping [CUSTOM] [setups=typing:mine]
> 
> The only flaw I can see in the suggestion is the use of the 
> \everyinitializeverbatim register because it is used for
> inline and display verbatim. A better place to add the option is 
> \buff_verbatim_initialize_typing_two for \starttyping
> and \buff_verbatim_initialize_type_two for \type.

ok

-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------

___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2023-08-18 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 12:41 [NTG-context] " Alex Leray
2023-08-17 14:32 ` [NTG-context] " Hans Hagen
2023-08-17 14:47   ` Alex Leray
2023-08-17 15:22 ` Wolfgang Schuster
2023-08-17 15:59   ` Alex Leray
2023-08-17 16:23     ` Wolfgang Schuster
     [not found]       ` <7f05a67b-2e44-a590-0768-3c6dc23f5349@stdin.fr>
     [not found]         ` <58e3cc9b-9614-79e0-4a5f-6f72a4cf7fcf@gmail.com>
     [not found]           ` <aa70b518-c14f-ab41-681c-0fe4de737a81@stdin.fr>
     [not found]             ` <54f222a3-fbf7-e5dc-4dc7-71c4ddfc7d1d@gmail.com>
2023-08-18 11:19               ` Hans Hagen [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=e59809c3-414a-561e-9f78-e30ba59d79a0@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@gmail.com \
    /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).