zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Improved _mailboxes
Date: Mon, 21 Feb 2000 16:41:01 +0000	[thread overview]
Message-ID: <1000221164101.ZM21266@candle.brasslantern.com> (raw)
In-Reply-To: <200002211230.NAA13030@beta.informatik.hu-berlin.de>

On Feb 21,  1:30pm, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Improved _mailboxes
}
} > (1) The default style should be to make the all-files group be alternate
} >     completions, i.e., not shown unless the -default- group is empty.
} 
} No. We should use tags so the user can decide what he wants to see.

Ah; that is of course what I meant, thank you for doing it.
 
} > (3) I'm sometimes offered a blank completion -- an empty slot at the top
} >     of the list of all completions.  I don't know where that comes from;
} >     it shouldn't be there.  Quoting problem somewhere?
} 
} Almost. There was no test for $MAIL and in _multi_parts a missing ()
} at an assignment. And some more of these in _mailboxes.

Hmm, I thought `typeset -U' would deal with that, but of course it also
applies to colon-separated lists.  Could have used `typeset -Ua' though,
nowadays, instead of all those empty initializations you added.

} > And of course, I haven't yet written any actual completion functions to
} > call this one; it's used only from _mutt, so far.
} 
} I think we should make the caching somewhat cleverer. I.e. only build
} the caches for the commands really used (tried completion upon).

The problem is that mutt uses _maildir_cache, pine uses _mbox_cache, and
zmail uses _mh_cache.  (Actually now that I think about it, pine can use
_mh_cache too.)  How do you deal with the crossover without caching them
all?  I'd rather not duplicate the knowledge of which programs can read
which other programs' mailboxes in both caching and tag-testing sections.

} Oh, and I could not apply 9812 and 9815 automatically, I hope this
} patch here applies without problems. Dunno how that happened.

That could be my trouble, as I was playing with _mailboxes before.  Did
anyone else have a problem?  I can re-diff against -dev-19 if needed.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~2000-02-21 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-21 12:30 Sven Wischnowsky
2000-02-21 16:41 ` Bart Schaefer [this message]
2000-02-21 17:25   ` PATCH: " Bart Schaefer
2000-02-21 20:06   ` Peter Stephenson
2000-02-21 21:59     ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-02-22  8:52 Sven Wischnowsky
2000-02-22 17:55 ` Peter Stephenson
2000-02-21 10:34 Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1000221164101.ZM21266@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).