From: mmc@maruska.dyndns.org (Michal Maruška)
To: zsh-workers@sunsite.dk
Subject: Re: (backward-)kill-argument (1/2 thanks 1/2 problem re-statement)
Date: 15 Mar 2002 16:49:41 +0100 [thread overview]
Message-ID: <m2zo1996ga.fsf_-_@linux3.maruska.tin.it> (raw)
In-Reply-To: <1020315153147.ZM2228@candle.brasslantern.com>
"Bart Schaefer" <schaefer@brasslantern.com> writes:
> On Mar 15, 9:55am, Sven Wischnowsky wrote:
> }
> } > i want to: * kill filenames w/ spaces: e.g. this\ is\ file.txt
> } Write yourself a little widget. As a starting point:
> }
> } kill-with-spaces() { local words words="${(z)BUFFER}"
> }BUFFER="${BUFFER%${words[-1]}[ ]#}" }
>
> That's a nice function, Sven, but I think I'd call it something like
> `backward-kill-shell-word', and it ought to test $LBUFFER, not $BUFFER. If you
> throw in `setopt localoptions extendedglob', we could even put it in the
> distribution,
>
> } (There's a space and a TAB inside that [ ].)
>
> You can write that as [[:space:]] now, I think?
>
Thanks to both of you. I am arriving to what i wanted.
> } > * maybe even the bracketed part: find { -name '*.h' }
> } >
> } > Is it possible in Zsh?
> } Using the above you could check if $words[-1] is one of the closing braces
> }and if it is, search back in the array for the matching opening brace. When
> }found, you can delete the end of $BUFFER up to that matching brace by using a
> }pattern of the form:
> }
> } ${words[-n]}[ ]##...[ ]##${words[-1]}[ ]#
>
> Hmm, I think I'd just do a loop killing words until the open-brace was missing
> from $LBUFFER. So, putting it all together,
>
> backward-kill-shell-expression() {
> setopt localoptions extendedglob
> local words
> words="${(z)LBUFFER}"
> LBUFFER="${LBUFFER%${words[-1]}[[:space:]]#}"
> if [[ "$words[-1]" == '}' ]]
> then
> words="${(z)LBUFFER}"
> while [[ "${${(@M)words:#[\{\}]}[-1]}" == '{' ]]
> do
> LBUFFER="${LBUFFER%${words[-1]}[[:space:]]#}"
> words="${(z)LBUFFER}"
> done
> fi
> }
>
> This could be extended to handle `( ... )', `[[ ... ]]', etc., and we could of
> course also write a forward- version.
But here i again explained wrongly what i intended.
[
I must admit, i would like to migrate from Zsh, sh etc. to SCSH (scheme
shell). Just Zsh has these unique and elaborated completion & other systems. But
these remain cryptic to me, and i (still) prefer to improve my understanding of scheme
rather that of Zsh (module system of ?) completion system.
]
I immagine Zsh keeps a database (roughly) like:
[and i am interested in how it works]
commands| minus-arguments|sort-of-type| completion action for the type (widget?)
--------------------------------------------------------------------------
find -name wants 1 text
now these brakets:
find { -name '*.h' }
i used only to delimit what i would like to remove. I have got in
the ZLE buffer (on the line) simply:
find -name '*.h'
And now i want to delete all "-name '*.h' " which is product of some grammar
rule, or simply the minus-argument with its argument(s).
next prev parent reply other threads:[~2002-03-15 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 16:42 (backward-)kill-argument Michal Maruška
2002-03-13 19:09 ` (backward-)kill-argument John Beppu
2002-03-13 20:23 ` (backward-)kill-argument -- reformulation of the problem Michal Maruška
2002-03-15 8:55 ` (backward-)kill-argument Sven Wischnowsky
2002-03-15 15:31 ` (backward-)kill-argument Bart Schaefer
2002-03-15 15:49 ` (backward-)kill-argument Bart Schaefer
2002-03-15 15:49 ` Michal Maruška [this message]
2002-03-15 16:39 ` (backward-)kill-argument (1/2 thanks 1/2 problem re-statement) Bart Schaefer
2002-03-18 8:41 ` Sven Wischnowsky
2002-03-18 8:36 ` (backward-)kill-argument 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=m2zo1996ga.fsf_-_@linux3.maruska.tin.it \
--to=mmc@maruska.dyndns.org \
--cc=zsh-workers@sunsite.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).