Different key pare for e-mail and signing code

[john doe]

Hello all,

Following my thread at (1), unless I'm missing something, it became
apparent that Enigmail/Tunderbird does not fit the bill anymore.


My plan is to use something like the following:

-----------------------------
sec   rsa4096 2020-01-03 [C] [expires: 2020-01-04]
      3C5CFD620005347A62052A6B596CB80D30E8829D
uid           [ultimate] Firstname Lastname <test at example.com>
ssb   rsa4096 2020-01-03 [S] [expires: 2020-01-04]
ssb   rsa4096 2020-01-03 [S] [expires: 2020-01-04]
ssb   rsa4096 2020-01-03 [E] [expires: 2020-01-04]

With mabey more signing subkeys.


My goal is to sign code and sign/encrypt e-mail but I'm not sure what's
the best way forward:
- One key pare for e-mail (sign/encrypt) and an other key pare for
signing code
- Finding a way to do what I want with only one key pare (multiple
signing subkeys and one encryption subkey)
- Am I missing something/better approach

For now I'm considering notmuch/sup to get what I want, it looks like
Mutt uses 'ncurses' which is not an option for me.

Any input is welcome

1)
https://admin.hostpoint.ch/pipermail/enigmail-users_enigmail.net/2020-January/005562.html


P.S.

By key pare, I mean private/public key.

--
John Doe