~juliob

Recent activity

Re: [PATCH aerc v3 2/2] notmuch: add completions for :cf, :filter and :search 2 months ago

From Julio B to ~rjarry/aerc-devel

Works as expected for all of :{query,cf,filter,search} commands.
The 'tag:' completion is really useful!

The only thing i found interesting is this:
If you type for example  folder:Inbox/<TAB> then aerc completes
  folder:Inbox/{cur,tmp,new}
but the notmuch command in bash shell completes just
  folder:Inbox/
so cur,tmp and new are not expanded. But i don't think that this is an
issue at all.

Tested-by: Julio B <julio.bacel@gmail.com>

[PATCH aerc] notmuch: fix disappearing messages 2 months ago

From Julio B to ~rjarry/aerc-devel

The current implementation assumes that 'root[0].FirstChild' is nil, but
this is not always the case. Instead of overwriting the FirstChild,
detect and link the messages to the LastChild of root[0].

Fixes: 672b4edca7af2303cfcb1d69a676556d12476b5f
Fixes: https://lists.sr.ht/~rjarry/aerc-devel/%3C20240305231305.44287-4-julio.bacel%40gmail.com%3E
Signed-off-by: Julio B <julio.bacel@gmail.com>
---
 worker/notmuch/lib/database.go | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/worker/notmuch/lib/database.go b/worker/notmuch/lib/database.go
index 7216274a..9a8a9a60 100644
--- a/worker/notmuch/lib/database.go
[message trimmed]

Re: [PATCH aerc 0/2] Implement dummy threads for notmuch 2 months ago

From Julio B to ~rjarry/aerc-devel

On Mon Mar 25, 2024 at 7:38 PM EET, inwit wrote:
> It works fine for level-1 siblings, but if you mix them with level-2,
> you get disappearing messages (which is way worse than unthreaded
> messages). As discussed over on irc, fixing the root to the first
> message doesn't seem like the best solution. Probably, creating a fake
> ancestor would be better.
>
> Tested-By: inwit <inwit@sindominio.net> 

Thank you inwit for testing this out! That's correct, some edge cases
are not handled properly with this patch. The solution seems to be much
more complex and requires changes deep down in the threading logic of
aerc. Unfortunately, I haven't achieved much with this yet. I'm not
familiar with the whole codebase and i couldn't fix this without

[PATCH aerc 2/2] ui: use a custom prefix for dummy root 3 months ago

From Julio B to ~rjarry/aerc-devel

These messages are not really the root of the thread, and should not be
displayed as such. Add a new special prefix to make them appear like
the first child of a rootless thread.

Signed-off-by: Julio B <julio.bacel@gmail.com>
---

Notes:
    Before:         After:
    -------------------------------
    Re: subject     ┬─>Re: subject
    ├─>             ├─>
    └─>             └─>
[message trimmed]

[PATCH aerc 1/2] notmuch: draw incomplete threads 3 months ago

From Julio B to ~rjarry/aerc-devel

Create a "pseudo thread" with the first message as root. This is a
temporary solution, until we have a more generic implementation of dummy
messages that works for all backends.

Signed-off-by: Julio B <julio.bacel@gmail.com>
---
 worker/notmuch/lib/database.go | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/worker/notmuch/lib/database.go b/worker/notmuch/lib/database.go
index 4d853642..beddb38d 100644
--- a/worker/notmuch/lib/database.go
+++ b/worker/notmuch/lib/database.go
@@ -137,11 +137,17 @@ func (db *DB) ThreadsFromQuery(ctx context.Context, q string, entireThread bool)
[message trimmed]

[PATCH aerc 0/2] Implement dummy threads for notmuch 3 months ago

From Julio B to ~rjarry/aerc-devel

Currently, threads that are incomplete are not drawn properly by aerc.
For example:

	Sender A	Re: test msg		01 Jan 01
	Sender B	Re: test msg		02 Jan 01
	Sender C	Re: test msg		03 Jan 01

Use the first message as a "dummy" root, and link the rest of the
messages to it. The above example becomes:

	Sender A	┬─>Re: test msg		01 Jan 01
	Sender B	├─>            		02 Jan 01
	Sender C	└─>            		03 Jan 01

Re: [PATCH aerc v2] ui: update vaxis 3 months ago

From Julio B to ~rjarry/aerc-devel

Tested-by: Julio B <julio.bacel@gmail.com>

Re: [PATCH aerc] terminal: draw even if underlying command has died 8 months ago

From Julio B to ~rjarry/aerc-devel

Thank you so much for fixing this! I can confirm that it is working
without problems.

Tested-by: Julio B <julio.bacel@gmail.com>

[PATCH v2] Accept proxy protocol on unix sockets 1 year, 7 months ago

From Julio B to ~emersion/soju-dev

---
Now soju accepts PROXY only on specified unix sockets.

Below are some testing commands that i used.

Example soju configuration
...
listen unix:///tmp/sojuaccept.socket
listen unix:///tmp/soju.socket
accept-proxy-from unix:///tmp/sojuaccept.socket
...

Quick testing
[message trimmed]

Re: displaying images within aerc 1 year, 8 months ago

From Julio B to ~rjarry/aerc-discuss

I had the same issues when using viu with kitty.
What i ended up using is this long filter:

image/*=kitty +kitten icat --stdin=yes --silent --transfer-mode stream --hold --place=120x120@0x7 && kitty +kitten icat --silent --transfer-mode stream --clear

I know that it looks awful, but its good enough for a quick view i guess.
Now icat waits for a key press before exiting and then it clears the image.
Also i had to reposition the image after the top headers and before the
statusline, otherwise the UI becomes a little messy.