zsh-workers
 help / color / mirror / code / Atom feed
From: Andy Spiegl <zsh.Andy@spiegl.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: bug in _mutt ?
Date: Mon, 26 Jun 2000 21:43:02 +0200	[thread overview]
Message-ID: <20000626214302.A28182@br-online.de> (raw)
In-Reply-To: <1000621152106.ZM31139@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Wed, Jun 21, 2000 at 03:21:06PM +0000

Sorry, I was out of reach for a few days...

Most of the issues are fixed by Clints patches.  Thanks!

> Yes.  That's the whole point of _multi_parts: it works like _path_files,
> but on strings that aren't necessarily file names.  So you should find
> that if you type
> 
> % mutt -f =sub<TAB>
> 
> it'll append the slash, and offer completions of
> 
> cus  mutt  zsh  zsh-workers  linux  kira  akte

Hm, it does append the slash, but then I only get a beep. :-(

> } It would sound more logical to me if the full paths were kept.
> 
> Why?  (Some people have very wide and deep mailbox hierarchies ...)
I fully agree with you, if completion after sub/.. still works.  But
actually in that case I would expect zsh to offer me _all_ the files in
that directory.  Hm, that's probably the same issue as whether completion
after = or + should only list the .muttrc-defined mailboxes or whether it
should list all files under ~/Mail.  I'd prefer both...in separate groups.

> mailbox.  This is imprecise, as it means that if you happen to have a
> directory named "cur" it'll guess that the parent is a qmail mailbox.
> You have a directory named "cus" ... do you also have a "cur"?
Nope, "cus" is short for "cusanus" and is just a name. :-)

Thanks,
 Andy.

-- 
 E-Mail: Andy@spiegl.de     URL: http://andy.spiegl.de
 PGP/GPG: see headers
                                o      _     _         _
  --------- __o       __o      /\_   _ \\o  (_)\__/o  (_)
  ------- _`\<,_    _`\<,_    _>(_) (_)/<_    \_| \   _|/' \/
  ------ (_)/ (_)  (_)/ (_)  (_)        (_)   (_)    (_)'  _\o_
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 cat /dev/boiler/water | tea | sieve > /cup
 mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp


  parent reply	other threads:[~2000-06-26 19:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000619211650.A5701@br-online.de>
2000-06-19 20:18 ` Bart Schaefer
2000-06-20 11:28   ` Andy Spiegl
2000-06-20 11:53     ` Peter Stephenson
2000-06-20 13:33       ` Bart Schaefer
2000-06-21 15:24       ` Bart Schaefer
2000-06-22  1:56         ` Clint Adams
2000-06-22  3:55         ` Geoff Wing
2000-06-22  3:59           ` Clint Adams
2000-06-20 14:02     ` Clint Adams
2000-06-20 15:18       ` Andy Spiegl
2000-06-21  7:55         ` Andy Spiegl
2000-06-21 15:21           ` Bart Schaefer
2000-06-21 15:30             ` Bart Schaefer
2000-06-22  1:50             ` Clint Adams
2000-06-22  2:27             ` PATCH: multiple mailbox lines in muttrc Clint Adams
2000-06-22  4:07               ` PATCH: multiple mailbox lines in muttrc and more Clint Adams
2000-06-26 19:43             ` Andy Spiegl [this message]
2000-06-27  0:51               ` bug in _mutt ? Bart Schaefer
2000-06-20  8:01 Sven Wischnowsky
2000-06-20 12:21 Sven Wischnowsky
2000-06-20 12:28 Sven Wischnowsky
2000-06-22  8:36 Sven Wischnowsky
2000-06-22  9:48 ` Bart Schaefer
2000-06-22 13:43   ` Clint Adams

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=20000626214302.A28182@br-online.de \
    --to=zsh.andy@spiegl.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).