On Mon May 9, 2022 at 3:53 PM CEST, Tim Culverhouse wrote:
> If the Cc header isn't showing up by default, you can enter command mode
> <C-x>, and then type:
>
> header Cc
>
> This will add a Cc editor.
This is exactly what I was looking for.
Thanks a lot!

On Mon May 9, 2022 at 1:00 PM CEST, Jens Grassel wrote:
> There are key bindings defined in `binds.conf` which should look
> something like this:
>
> ```
> [compose]
> $ex = <C-x>
> <C-k> = :prev-field<Enter>
> <C-j> = :next-field<Enter>
>
> [compose::editor]
> $noinherit = true
> $ex = <C-x>
> <C-k> = :prev-field<Enter>

Sorry for these very basic question, but after reading all the manual I
don't find how add an address on CC, or modify contacts already
filled in To.

Thanks,
--
Antoine — antoine@quaternum.net

On Thu May 5, 2022 at 6:05 PM CEST, Robin Jarry wrote:
> Hi,
>
> I assume you are referring to this:
>
> https://lists.sr.ht/~rjarry/aerc-devel/%3C3C0445YFB4K4X.33HV0Q07DOX4R%40venera%3E
>
> I will not accept such a patch. If there is a bug, it should be fixed.
> A README file is not a place for such things, a bug tracker is.
>
> In the meantime, Omar, can you create a ticket with all details that you
> included in your email? https://todo.sr.ht/~rjarry/aerc
>
> Thanks!

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 06db966..1d51465 100644
--- a/README.md
+++ b/README.md
@@ -100,6 +100,8 @@ This will install templates and other config files to `/custom/location/share/ae
 and man pages to `/custom/location/share/man`. This extra location will have lower
 priority than the XDG locations but higher than the fixed paths.
 
+Be careful, during the setup aerc will crash if the terminal window is not large enough.
+
[message trimmed]

---
 content/blog/Announcing-Hare.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/Announcing-Hare.md b/content/blog/Announcing-Hare.md
index 9615e80..7180e4a 100644
--- a/content/blog/Announcing-Hare.md
+++ b/content/blog/Announcing-Hare.md
@@ -1,5 +1,5 @@
 ---
-title: Announcing the Hare programming langauge
+title: Announcing the Hare programming language
 date: 2022-04-25
 ---
[message trimmed]

> If you're doing it with a smaller window like 80x24, does it still crash
> if you try at a larger size, like full-screen or something like 120x40?

Ok that was the problem, the setup finished wiht a larger size, thanks a
lot.
I'm definitively not good for reading/understanding a crash log.
I don't know if it's relevant but I will perhaps add a line in the
installation instructions.

PS: this message has been written and sent with aerc!

Yes of course:

1. git clone aerc repository
2. cd aerc
3. sudo make
4. sudo make install
5. aerc
6. first page of setup: no problem
7. second page of setup (server adress, etc.): "aerc has encountered a 
critical error and has terminated. Please help us fixing
this by sending this log and the steps to reproduce the crash to:
~rjarry/aerc-devel@lists.sr.ht"

Do you need more information?

Hi,
I want to try aerc on Linux (Ubuntu 20.04), but when I set up aerc the 
application crash. Perhaps I miss something, here is the log:

```
################################################################################
                                   PANIC CAUGHT!
                         2022-04-13T13:36:07.734783-0400
################################################################################

aerc has encountered a critical error and has terminated. Please help us 
fixing
this by sending this log and the steps to reproduce the crash to:
~rjarry/aerc-devel@lists.sr.ht

Thank you for pointing out that "normal" is not appropriate here. I just 
discover why `git log` is not what I thought it was: perhaps Git 
platform/service like GitLab, Gitea or GitHub are confusing the issue 
with a _history option_ that is very different than a `git log`. Also 
Sourcehut respects the fondamental principles of Git, it makes sense.

And it's very interesting (for me) to learn how much Git is content 
oriented and not files oriented. Thank you for helping me to understand 
better Git (I will try some solutions from the SO post).
-- 
Antoine
antoine@quaternum.net
www.quaternum.net