Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Accidently wrote a command in CAPS LOCK

X-seq: zsh-users 10411
From: Peter Stephenson <pws@xxxxxxx>
To: zsh-users@xxxxxxxxxx (Zsh users list)
Subject: Re: Accidently wrote a command in CAPS LOCK
Date: Thu, 22 Jun 2006 11:44:18 +0100
In-reply-to: <Xns97EA7602A50ECzzappergmailcom@xxxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <Xns97EA6E7D249FAzzappergmailcom@xxxxxxxxxxx> <200606221025.k5MAPD8f010975@xxxxxxxxxxxxxx> <Xns97EA7602A50ECzzappergmailcom@xxxxxxxxxxx>

zzapper wrote:
> I was hoping for a history modifier eg
> ^^^ or !!:s///
> but they don't seem to support wildcards?

You should have said that earlier...

!!:l

will turn the whole previous line into lower case.  Do you only want a
certain range of words?  You can do tricks like:

% ECHO THIS NEXT WORD IS UPPERCASE
zsh: command not found: ECHO
% !!:-:l !!:$
% echo this next word is UPPERCASE

The word selector - is short for 1- which is short for 1 to the word
before the last.  The word selector $ is the last word.  So you get all
but the last word in lower case, then the next word as it was.

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070

To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

Follow-Ups:
- Re: Accidently wrote a command in CAPS LOCK
  - From: zzapper

References:
- Accidently wrote a command in CAPS LOCK
  - From: zzapper
- Re: Accidently wrote a command in CAPS LOCK
  - From: Peter Stephenson
- Re: Accidently wrote a command in CAPS LOCK
  - From: zzapper

Messages sorted by: Reverse Date, Date, Thread, Author