When the composer window opens, an user might want to start writing
the email body before adding a subject and recipients. Setting the
focus-body option to true achieves that by setting the focus to the
editor.

Signed-off-by: Markus Unkel <markus@unkel.io>
---
This simplifies v3 by removing the focusBody field from composer.

 app/compose.go        | 2 +-
 config/aerc.conf      | 6 ++++++
 config/compose.go     | 1 +
 doc/aerc-config.5.scd | 5 +++++
 4 files changed, 13 insertions(+), 1 deletion(-)
[message trimmed]

When the composer window opens, an user might want to start writing
the email body before adding a subject and recipients. Setting the
focus-body option to true achieves that by setting the focus to the
editor.

Signed-off-by: Markus Unkel <markus@unkel.io>
---
Thanks for reviewing the design of the [compose].focus-body option to
Koni and Robin by agreeing on not introducing focusBody flags on message
commands.

 app/aerc.go                 | 4 ++--
 app/compose.go              | 9 ++++++---
 commands/account/compose.go | 3 ++-
[message trimmed]

On Sat Nov 9, 2024 at 11:10 AM CET, Koni Marti wrote:
> Alternatively and to avoid adding an additional flag to every command
> that invokes the composer, maybe your approach from v1 to set focusBody
> := (true | false) explicitly might be better? However, I would then make
> it opt-in, i.e.  only change the default behavior when the user sets
> [composer].focus-body=true.
>
> What do you think?

Personally I would prefer setting the focus-body option in config file
only, because I see that just as an UX-related option "Where to set the
focus when entering a new compose window" that I don't want to change
during my aerc session via flags.

When the composer window opens, an user might want to start writing
the email body before adding a subject and recipients. Setting the
focus-body option to true achieves that by setting the focus to the
editor.

The compose options edit-headers and focus-body are mutually exclusive,
because the focus-body option implies the focus to the editor and
not the focus to the line in editor, where the email body starts,
in case of having the edit-headers option set, where also the headers
are directly editable in editor.

Signed-off-by: Markus Unkel <markus@unkel.io>
---
This adds the mutual exclusivity of both compose options edit-headers
[message trimmed]

When the composer window opens, an user might want to start writing
the email body before adding a subject and recipients. Setting the
focus-body option to true achieves that by setting the focus to the
terminal.

Signed-off-by: Markus Unkel <markus@unkel.io>
---
 app/aerc.go                 |  4 ++--
 app/compose.go              |  9 ++++++---
 commands/account/compose.go | 14 ++++++++------
 commands/account/recover.go |  3 ++-
 commands/msg/forward.go     |  4 +++-
 commands/msg/invite.go      |  3 ++-
 commands/msg/recall.go      |  3 ++-
[message trimmed]

Dear Aerc Team,

is there an option or a workaround to auto-focus into the editor after
the compose window opened. In my workflow I first write the body and 
then I add the subject/recipients.

Thanks in advance, you are doing a great job on lowering the barrier
working in the email-driven git workflow.

Best regards,
Markus

---
 your-name | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 your-name

diff --git a/your-name b/your-name
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/your-name
@@ -0,0 +1 @@
+I'm about to try git send-email
-- 
2.25.1
[message trimmed]

---
 your-name | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 your-name

diff --git a/your-name b/your-name
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/your-name
@@ -0,0 +1 @@
+I'm about to try git send-email
-- 
2.25.1
[message trimmed]