Re: [Mutt] #3197: annoying error when <last-entry> is used in an
#3197: annoying error when <last-entry> is used in an empty mailbox
-----------------------+----------------------------------------------------
Reporter: mszudzik | Owner: pdmef
Type: defect | Status: assigned
Priority: minor | Milestone:
Component: mutt | Version: 1.5.18
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment(by pdmef):
Both tickets are unrelated. #2134 is about command-line exit codes and
#3187 is about an error message to be improved.
For case (1), I mutt applies patterns to visible messages not folders. The
~A pattern together with untagging and tag-prefix-cond should do the
trick, no?
For case (2), I don't think this is quite the right way to go. Macros (as
I understand them) don't provide a macro language to automate mutt. They
provide a way to bind a longer sequence of key strokes to a shorter one to
save typing for frequently used operations. Function names are allowed for
readability and portability. That's why in #3187 it reports the key is not
bound and not function name unknown.
Other than ~A, I don't see anything simple to do about this.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3197#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent