Does status_format get evaluated every time the viewing window changes? I was
hoping to use it with this pushed fmtpipe patch to get the xtitle functionality
I use to see the number of new messages in the status bar.
But when I set status_format thus:
set status_format="/home/ckillian/hg/mutt/con
On Wednesday, 14 March 2007 at 01:33, David Champion wrote:
> * On 2007.03.13, in <[EMAIL PROTECTED]>,
> * "Brendan Cully" <[EMAIL PROTECTED]> wrote:
> >
> > On further reflection, I think your fmtpipe.3 patch should work well
> > enough -- people will just have to get used to putting their st
* On 2007.03.13, in <[EMAIL PROTECTED]>,
* "Brendan Cully" <[EMAIL PROTECTED]> wrote:
>
> On further reflection, I think your fmtpipe.3 patch should work well
> enough -- people will just have to get used to putting their string in
> extra quoting. But the one you submitted seems to have som
I caught your second followup where you okayed fmtpipe.3 just as I was
about to send this reply to your first. I've trimmed away most of my
reply, but there's a further idea I had that might be attractive.
> That doesn't sound quite right. If the arguments are unquoted, mutt
> will no longer do i
On Tuesday, 13 March 2007 at 13:45, Brendan Cully wrote:
> I can't figure out the right syntax for this. Both approaches seem to
> have defects. There are comments in line below.
On further reflection, I think your fmtpipe.3 patch should work well
enough -- people will just have to get used to put
I can't figure out the right syntax for this. Both approaches seem to
have defects. There are comments in line below.
On Sunday, 11 March 2007 at 23:02, David Champion wrote:
> * On 2007.03.11, in <[EMAIL PROTECTED]>,
> * "Brendan Cully" <[EMAIL PROTECTED]> wrote:
> >
> > I think I prefer for
* On 2007.03.11, in <[EMAIL PROTECTED]>,
* "Brendan Cully" <[EMAIL PROTECTED]> wrote:
>
> I think I prefer force-quoting or sending the input via stdin. It
> means the receiver has to be a little smarter about parsing, I know,
> but there isn't a different quoting scheme for piped vs non-pi
On Wednesday, 07 March 2007 at 15:00, David Champion wrote:
> I've attached two patches, fmtpipe.2 and fmtpipe.3. These are
> mutually-exclusive alternatives to current problems. Fmtpipe.3 takes
> a somewhat new approach to the whole thing, for reasons I'll outline
> below. Fmtpipe.2 addresses p
* On 2007.03.05, in <[EMAIL PROTECTED]>,
* "Brendan Cully" <[EMAIL PROTECTED]> wrote:
>
> I think I may have mentioned in the $xtitle thread, your patch doesn't
> handle things like %> which cause recursive invocations of
> mutt_FormatString. I think this would be easy to fix by having
OK,
