From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: (backward-)kill-argument
Date: Fri, 15 Mar 2002 15:31:46 +0000 [thread overview]
Message-ID: <1020315153147.ZM2228@candle.brasslantern.com> (raw)
In-Reply-To: <15505.46831.979708.369781@wischnow.berkom.de>
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?
} > * 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.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2002-03-15 15:32 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 ` Bart Schaefer [this message]
2002-03-15 15:49 ` (backward-)kill-argument Bart Schaefer
2002-03-15 15:49 ` (backward-)kill-argument (1/2 thanks 1/2 problem re-statement) Michal Maruška
2002-03-15 16:39 ` 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=1020315153147.ZM2228@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).