From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Context-sensitive ZLE
Date: Thu, 22 Jun 2000 09:13:23 +0200 (MET DST) [thread overview]
Message-ID: <200006220713.JAA02135@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 21 Jun 2000 10:05:58 -0700
Bart Schaefer wrote:
> Now that the completion system is able to set up all this wonderful context,
> I'm wondering about being able to use it elsewhere in zle.
>
> For example, I'd like backward-kill-word to stop at dots when I'm editing
> an IP address in an ssh or telnet command, but to delete past dots and stop
> at slashes when I'm editing a file name.
>
> It can almost be done with a completion function that figures out how to
> modify the word and then calls compadd -U, but that doesn't work for e.g.
> transpose-words (or anything else that spans more than one word).
One of my favourite pastimes is currently to think about doing to zle
what we've done to the completion system. I.e. reduce the internals to
the basics (unlike completion, most things are already there for zle)
and then shell functions...
Then we would be able to use as many styles as possible, of course.
(I'm not very happy looking up styles from the C code and have avoided
it until now, because it would defeat functions that define a zstyle
shell function to get at the styles used... and things like that.)
Ideally, we should probably put even more things into C-code
(mailcheck comes to mind). But non of this before 4.0, of course.
Hm, probably not very helpful, this `answer', sorry ;-}
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-22 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-22 7:13 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-22 13:17 Sven Wischnowsky
2000-06-21 17:05 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=200006220713.JAA02135@beta.informatik.hu-berlin.de \
--to=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).