[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problems with optimset option name completion in 3.8.0
|
From: |
Olaf Till |
|
Subject: |
Re: problems with optimset option name completion in 3.8.0 |
|
Date: |
Mon, 6 Jan 2014 19:31:22 +0100 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Jan 03, 2014 at 11:34:46PM +0100, Olaf Till wrote:
> ...
> 1) consider it illegitimate to have option names whose first
> characters are equal to a different full option name (means I have
> to change the option names in the said functions of the optim
> package!),
>
> 2) change optimset so that it always matches an option name if it is
> given in full, even if there is a longer option name which starts
> with the same characters,
>
> 3) drop option name completion in optimset.
> ...
No response means I have to go ahead with 1).
--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net
signature.asc
Description: Digital signature