On Sun, May 31, 2026 at 10:40:19PM +0200, Vincent Lefevre wrote:
In edit.c, function mutt_builtin_editor():case 'b': msg->env->bcc = mutt_parse_adrlist(msg->env->bcc, p); msg->env->bcc = mutt_expand_aliases(msg->env->bcc); break; case 'c': msg->env->cc = mutt_parse_adrlist(msg->env->cc, p); msg->env->cc = mutt_expand_aliases(msg->env->cc); break; [...] case 't': msg->env->to = rfc822_parse_adrlist(msg->env->to, p); msg->env->to = mutt_expand_aliases(msg->env->to); break; Why is there a difference between 'b'/'c' and 't'?
No idea. It's been that way forever. It looks to me like 't' should be using the mutt_parse_adrlist() for the most flexibility.
Similarly in the help strings, one has "addresses" for ~b/~c and "users" for ~t: ~b addresses add addresses to the Bcc: field\n\ ~c addresses add addresses to the Cc: field\n\
~t users add users to the To: field\n\
I can't find anything about this in the manual.
Ah, this at least has an explanation. The help for ~b and ~c was changed in 86700b01. I didn't catch the difference with ~t at the time because of the separation between them.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
