Hi !
A few days ago, it started making the switch from neomutt to aerc and I'm 
really glad I did.
However, my editors' colors were not working at all for a few days making it 
impossible to use aerc.

I first tracked it down as vaxis using colons as its truecolor delimiter instead of 
semicolons and `st` not supporting those.
I custom patched my st but colors were "off". 
It took me an  embarasingly long time to found out that by default vaxis does 
palette approximation. 
It only uses truecolors if the `COLORTERM` variable is set or if the 
_XTGETTCAP_ response contains "RGB". I never thought of the former and the latter 
made me really confuse as to why `xterm` had the right colors whereas `st`

---
 rc/filetype/gleam.kak | 120 ++++++++++++++++++++++++++++++++++++++++++
 rc/tools/comment.kak  |   2 +-
 2 files changed, 121 insertions(+), 1 deletion(-)
 create mode 100644 rc/filetype/gleam.kak

diff --git a/rc/filetype/gleam.kak b/rc/filetype/gleam.kak
new file mode 100644
index 0000000..bf52a8f
--- /dev/null
+++ b/rc/filetype/gleam.kak
@@ -0,0 +1,120 @@
+# https://gleam.run/
+#
[message trimmed]

  I dedicate any and all copyright interest in this software to the
  public domain.  I make this dedication for the benefit of the public at
  large and to the detriment of my heirs and successors.  I intend this
  dedication to be an overt act of relinquishment in perpetuity of all
  present and future rights to this software under copyright law.
-- 
2.45.2

My copyright waiver is linked as a patch to this mail but I thought I just clear something.

Sadly, truly, eventhough I signed this copyright waiver, all my rights cannot be waive, because of french laws and their view of the public domain.

Quoting this wikipedia page [1]:
> The moral rights are inalienable, perpetual and inviolable. They pass to the
> author's heirs or executor on the author's death, but may not be otherwise
> transferred or sold by the author or legal successors. Any agreement to
> waive an author's moral rights is invalid, although the author cannot be
> forced to protect moral rights to the work, and always has the option to
> refrain from exercising them.

Translating this wikipedia page [2]:
> As opposed to other jurisdictions (like the USA's), it is not technically

---
rc/filetype/gleam.kak | 124 ++++++++++++++++++++++++++++++++++++++++++
 rc/tools/comment.kak  |   2 +-
 2 files changed, 125 insertions(+), 1 deletion(-)
 create mode 100644 rc/filetype/gleam.kak

diff --git a/rc/filetype/gleam.kak b/rc/filetype/gleam.kak
new file mode 100644
index 00000000..afecc684
--- /dev/null
+++ b/rc/filetype/gleam.kak
@@ -0,0 +1,124 @@
+# https://gleam.run/
+#
[message trimmed]

Hi !
Just stumbled accross this repository and clicked on a few links :)
Doing so, i realized the hare-http link points to hare-linux, just wanted
to let you know :)

Hoping that wasn't already reported, and thanks for the link aggregation !
Thomas.

Hi ! Sending this message again since the DKIM signature failed the first time. :)

---

Hi !
I've recently created a blog on your platform and it's been great!
I've been tinkering with settings and seeing stuff come to life is awesome (though I've not posted my first non-draft post yet).

I started writing a few posts, as draft on my machine, using my own note-taking software. 
In the mataroa documentation, endpoints are specified that let a user manage its posts via http request.
My issue arise when working with images; I either have to upload them by hand, copy-paste their URLs and add them to my post.
This process might become a pain in the futur, if I need to handle multiple images in a single post.

Is there any plan to allow users to upload images using a dedicated endpoint ?

Hi !
I've recently created a blog on your platform and it's been great!
I've been tinkering with settings and seeing stuff come to life is awesome (though I've not posted my first non-draft post yet).

I started writing a few posts, as draft on my machine, using my own note-taking software. 
In the mataroa documentation, endpoints are specified that let a user manage its posts via http request.
My issue arise when working with images; I either have to upload them by hand, copy-paste their URLs and add them to my post.
This process might become a pain in the futur, if I need to handle multiple images in a single post.

Is there any plan to allow users to upload images using a dedicated endpoint ?
If that's not the case but you are open to the idea, I could provide a patch.
If that's not the case at all, can one use any other image host services or will some be blocked by the CORS agent ?

Thanks ! :)

---
 doc/azy.txt          |  9 ++++++---
 lua/azy/builtins.lua |  6 ++++--
 lua/azy/sources.lua  | 12 +++++++++---
 teal/azy/builtins.tl |  8 +++++---
 teal/azy/sources.tl  | 16 +++++++++++-----
 5 files changed, 35 insertions(+), 16 deletions(-)

diff --git a/doc/azy.txt b/doc/azy.txt
index 4b44a69..59be750 100644
--- a/doc/azy.txt
+++ b/doc/azy.txt
@@ -26,9 +26,11 @@ Builtins.SelectOptions<T>                      *azy-Builtins.SelectOptions<T>*
 buffers()                                             *azy.builtins.buffers()*
[message trimmed]

As discussed, I'm forwarding the exposed issue and patch from 
[this todo][] to this mailing-list.

Thomas Teixeira (1):
  fix: specify_source -> Sources.FilesConfig.show_source

 doc/azy.txt          |  9 ++++++---
 lua/azy/builtins.lua |  6 ++++--
 lua/azy/sources.lua  | 12 +++++++++---
 teal/azy/builtins.tl |  8 +++++---
 teal/azy/sources.tl  | 16 +++++++++++-----
 5 files changed, 35 insertions(+), 16 deletions(-)

--