I just realised I inadvertantly replied directly to the sender instead
of to the list. My apologies.
On Mon, Aug 17, 2009 at 11:41:18AM +1000, Jaime Tarrant wrote:
>
> This sounds to me like you have a postponed message - in this case, when
> you go to compose a new message again, mutt brings bac
Hi,
* Robert Holtzman wrote:
> Any ideas appreciated.
Well, for the postpone issue, see the $postpone setting in your
local copy of the manual or online. The bindings: mutt is not
disabling them (why should it), you probably didn't specify them for
the postponed menu. For all available menus, pl
* Robert Holtzman (hol...@cox.net) wrote:
> On Fri, 14 Aug 2009, Jason Helfman wrote:
>
> >Have you tried issuing a "?" to see what mutt thinks "m" it is mapped to?
>
> That was the first thing I did. It said "compose a new mail message"
> just like it always did. The only difference is that it u
On Fri, 14 Aug 2009, Jason Helfman wrote:
Have you tried issuing a "?" to see what mutt thinks "m" it is mapped to?
That was the first thing I did. It said "compose a new mail message"
just like it always did. The only difference is that it used to work as
advertised.
Thanks for the reply.
Have you tried issuing a "?" to see what mutt thinks "m" it is mapped to?
-j
On Fri, Aug 14, 2009 at 01:04:35PM -0700, Robert Holtzman thus spake:
After Mutt working well for a week or so, issuing "m" to compose a new
message now results in opening the postponed-msgs mailbox. It also
disables s
After Mutt working well for a week or so, issuing "m" to compose a new
message now results in opening the postponed-msgs mailbox. It also
disables scrolling in the side pane using ^p and ^n. The only change to
~.muttrc I've made was to add some mailboxes. Don't recall if
postponed-msgs was one.
