From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: completion features
Date: Sat, 13 Mar 1999 09:59:06 -0800 [thread overview]
Message-ID: <990313095906.ZM756@candle.brasslantern.com> (raw)
In-Reply-To: <14057.16047.992483.728525@localhost.localdomain>
On Mar 12, 8:19am, Bart Schaefer wrote:
} Subject: Re: completion features
}
} Sven Wischnowsky writes:
} >
} > One more question: we could make this user-configurable. E.g.
} > `compconfig[...]=-1' would mean that `line_len - 1' errors would be
} > accepted and so on. Should we...? Any suggestions for the `...'? ;-)
}
} Pardon me if I've missed something, but you aren't really suggesting
} that the number of errors be based on the entire length of the input
} line, are you? The length of the current _word_, surely? For file
} names, it should probably only be the length of the path segment that
} actually contains the cursor.
That last sentence applies to completeinword only, of course. If you're
at the end of a /u/s/l/z/z/s/ path expecting it to expand all the way to
/usr/src/local/zsh/zsh-3.1.5-pws-11/Src/, having the length of the word
determine the number of errors makes sense.
Perhaps the length of the word minus the number of slashes? Argh. I'm
thinking about this too hard.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-03-13 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 13:10 Sven Wischnowsky
1999-03-12 16:19 ` Bart Schaefer
1999-03-13 17:59 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-15 9:59 Sven Wischnowsky
1999-03-12 9:36 Sven Wischnowsky
1999-03-12 9:38 ` Peter Stephenson
1999-03-12 8:55 Sven Wischnowsky
1999-03-11 17:02 Peter Stephenson
1999-03-11 22:06 ` 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=990313095906.ZM756@candle.brasslantern.com \
--to=schaefer@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).