9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thedaemon@thedaemon.space
To: 9front@9front.org
Subject: Re: [9front] Patch: snarf paste support for (e)enter, and refactoring
Date: Mon, 09 Sep 2024 21:22:17 -0500	[thread overview]
Message-ID: <FCFF8BD338A7D9B691D71573964AA34C@thedaemon.space> (raw)
In-Reply-To: <92e415df-3594-42fc-8d8a-e9428dd61a68@sirjofri.de>

Quoth sirjofri <sirjofri+ml-9front@sirjofri.de>:
> Hello,
> 
> This patch adds snarf and paste support to the two library functions enter and eenter. It also adds an internal function _genenter to share lots of the code. This does not change the interfaces of (e)enter though, for compatibility reasons.
> 
> In total, this adds 100 lines of code, but removes duplicate code for drawing and interpreting input.
> 
> I did test it with standard ascii, as well as some simple sequences of greek letters, but there could still be bugs. UTF-8 handling code is mostly inspired by/copied from acme.
> 
> More importantly, I can imagine you don't like the structure here and there, as it's more complex than the simple approach we currently have. Just let me know and I'll adjust it accordingly.
> 
> The patch is pretty long, so here's just a link to the file. If needed, I can also paste the data directly, just let me know.
> 
> https://sirjofri.de/oat/patches/eesp.diff
> 
> sirjofri
Thank you!  I
will try this out as soon as I can figure out how to apply this.  One
day I'll use diff enough to memorize the command, that is not today.


  reply	other threads:[~2024-09-10  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07 11:21 sirjofri
2024-09-10  2:22 ` thedaemon [this message]
2024-09-20 17:38   ` sirjofri
2024-09-21 11:24     ` umbraticus

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=FCFF8BD338A7D9B691D71573964AA34C@thedaemon.space \
    --to=thedaemon@thedaemon.space \
    --cc=9front@9front.org \
    /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).