From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: More intellegent suffix removing?
Date: Mon, 7 Jun 1999 15:21:46 +0400 [thread overview]
Message-ID: <000901beb0d7$edec34d0$21c9ca95@mow.siemens.ru> (raw)
Consider:
bor@itsrm2:~%> l /S<TAB>
bor@itsrm2:~%> l /SInus/ now I press ``;''
bor@itsrm2:~%> l /SInus/;
note, that ``/'' is not removed, but in this case `;' can not be a part of
current word (but \; or ';' or ";" can). Is it possible (does it make
sense?) do make suffix removing follow Zsh grammar more closely?
/andrej
next reply other threads:[~1999-06-07 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-07 11:21 Andrej Borsenkow [this message]
1999-06-07 11:41 Sven Wischnowsky
1999-06-07 12:09 ` Andrej Borsenkow
1999-06-10 13:55 ` Andrej Borsenkow
1999-06-10 14:02 ` Sven Wischnowsky
1999-06-10 16:31 ` Bart Schaefer
1999-06-10 16:40 ` Andrej Borsenkow
1999-06-07 12:44 Sven Wischnowsky
1999-06-11 7:03 Sven Wischnowsky
1999-06-11 8:18 Sven Wischnowsky
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='000901beb0d7$edec34d0$21c9ca95@mow.siemens.ru' \
--to=borsenkow.msk@sni.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).