Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1016780

Bug#836343: mutt: macro interpretation is really fragile

From Samuel Hym <samuel.hym+bugs@rustyne.lautre.net>
Newsgroups linux.debian.bugs.dist
Subject Bug#836343: mutt: macro interpretation is really fragile
Date 2020-07-06 17:30 +0200
Message-ID <ApBea-5Rx-11@gated-at.bofh.it> (permalink)
References (1 earlier) <scOTL-3xC-5@gated-at.bofh.it> <scRyh-51C-19@gated-at.bofh.it> <Ak61j-3OY-7@gated-at.bofh.it> <scIbD-7ol-27@gated-at.bofh.it> <Ak61j-3OY-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Antonio,

> since many things changed in teh most recent version (including the fact that
> we are not using neomutt anymore), are you still experiencing this issue in
> 1.14.4-2? 

I’ve just tested using mutt package 1.14.5-1 using the small muttrc
from the mail that opened this bug report, the main bug reported is
still there. Namely "<function-name>" in a macro sequence is
interpreted as a call to the function if the function is available in
the current context and but otherwise as a sequence of the keys '<',
'f', etc. So this bug is still present.

I cannot reproduce the other, tiny, bug, about some part of the
sequence not being interpreted after a <shell-escape>, though.

Best regards,
Samuel

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Bug#836343: mutt: macro interpretation is really fragile Antonio Radici <antonio@debian.org> - 2020-06-21 13:10 +0200
  Bug#836343: mutt: macro interpretation is really fragile Samuel Hym <samuel.hym+bugs@rustyne.lautre.net> - 2020-07-06 17:30 +0200

csiph-web