Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160819223513.ZM1670@torch.brasslantern.com>
Date: Fri, 19 Aug 2016 22:35:13 -0700
In-Reply-To: <20160819155651.GA9598@fujitsu.shahaf.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
        "umount /f/b<TAB> -> /foo/bar" (Aug 19,  3:56pm)
References: <20160819155651.GA9598@fujitsu.shahaf.local2>
To: zsh-workers@zsh.org
Subject: Re: umount /f/b<TAB> -> /foo/bar
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Aug 19,  3:56pm, Daniel Shahaf wrote:
}
} +    # This codepath honours any -M matchspec parameters.
} +    () {
} +      local -a tmp_buffer
} +      compadd -A tmp_buffer "$__gopts[@]" -a files
} +      matches+=( "${(@)tmp_buffer/$canpref/$origpref}" )
} +    }
} +  else
} +    # ### Ideally, this codepath would do what the 'if' above does,
} +    # ### but telling compadd to pretend the "word on the command line"
} +    # ### is ${"the word on the command line"/$origpref/$canpref}.
} +    matches+=(${${(M)files:#$canpref*}/$canpref/$origpref})
} +  fi

Perhaps some variation on

    compadd -M "B:${(b)origpref}=${(b)canpref}" -a files

??  Some cases of mount point names containing unusual characters might
be a little weird.