Thanks for fixing this this Simon. I've applied the patch and included 
it in v4.4.0

Hi Jaime,

I think you may be seeing the effects of the upscaling_method option. It 
affects images are scaled up by imv. 'linear' does smooth interpolation, 
and is the default, 'nearest_neighbour' will pick the value of the 
closest pixel which is what you'd want for pixel art.

Hopefully that helps.

Harry

Hi Johannes,

Thanks for the patch, though this isn't actually a typo. The whitespace 
here is re-inserting the separator between each word after the word has 
been expanded. This does result in an extra whitespace at the end of the 
output, which could be addressed, but we do still need to keep the 
whitespace between words.

Harry

On 2022-01-11 11:54, Johannes Knoll wrote:
> src/imv.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 

 > Looking more closely at Meson now, I see its written in Python. This
 > is an inappropriate implementation language for a build system, and
 > more than enough reason enough for me to never touch it.

For what it's worth you're not the only one to feel that way. There is a 
C implementation of meson on sourcehut that seems to be actively 
developed: https://sr.ht/~lattis/muon/

Obviously that doesn't change the value proposition of why you'd use 
meson instead of make, but it does help cut an unnecessary python 
dependency.

Harry

Thanks! Applied and pushed.

That does sound similar to the previous issue. Are you using wayland or 
x11? Presumably it's an issue with auto-repeat triggering that binding 
multiple times. Either there's an issue with the input handling logic, 
or it's unavoidable in which case perhaps imv should ignore key repeat 
events after some threshold since the previous one.

> Here is the second version of the patch for libgrapheme.

Thanks! I gave it a slight tweak and polish, since I realised the logic I
suggested had a bug in next_char. Changes pushed.

> [PATCH]

Thanks, applied and pushed!

> Sorry for the incorrect format of my previous patch email.

No problem, I hadn't yet figured out how to trigger the CI via email yet
myself either, or documented it.

Hi Cem,

Thanks for the patch. I wasn't aware of libgrapheme before and I like its
smaller profile. icu is overkill for imv.

I've got some suggestions for the patch:

Instead of defining new `grapheme_*` functions to be called by
`next_char` and `prev_char`, I think we should replace the `next_char`
and `prev_char` functions entirely with the #ifdefs depending on
whether imv is using icu or grapheme. I also think you could simplify
the prev/next functions a bit beyond what you have currently. The logic
could be something like...

Signed-off-by: Harry Jeffery <me@harry.pm>
---
 chat.sr.ht/quickstart.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/chat.sr.ht/quickstart.md b/chat.sr.ht/quickstart.md
index 62dca8b..228fbc2 100644
--- a/chat.sr.ht/quickstart.md
+++ b/chat.sr.ht/quickstart.md
@@ -26,11 +26,11 @@ section.
 
 [config]: https://git.sr.ht/~emersion/soju/tree/master/item/contrib/clients.md
 
 To set up your bouncer connection, you will need to generate an OAuth 2.0
[message trimmed]