zsh-users
 help / color / mirror / code / Atom feed
From: zzapper <david@tvis.co.uk>
To: zsh-users@sunsite.dk
Subject: Re: Accidently wrote a command in CAPS LOCK
Date: Thu, 22 Jun 2006 10:36:10 +0000 (UTC)	[thread overview]
Message-ID: <Xns97EA7602A50ECzzappergmailcom@80.91.229.5> (raw)
In-Reply-To: <200606221025.k5MAPD8f010975@news01.csr.com>

Peter Stephenson <pws@csr.com> wrote in
news:200606221025.k5MAPD8f010975@news01.csr.com: 

> zzapper wrote:
>> 
>> Accidently wrote a command in CAPS LOCK
>> 
>> FTX SUCC BOOK
>> 
>> What's the best way to lowercase this?
> 
> Well, going to the start and using down-case-word (ESC l in Emacs
> mode) until you get to the end is the obvious way.
> 
> But it's not hard (after you've worked out the offsets, anyway) to
> write a widget that transforms the region---I hadn't realised there
> wasn't one:
> 
>   down-case-region() {
>     emulate -L zsh
>     integer p1 p2
> 
>     if (( CURSOR < MARK )); then
>       (( p1=CURSOR+1, p2=MARK ))
>     else
>       (( p1=MARK+1, p2=CURSOR ))
>     fi
>     BUFFER[p1,p2]=${(L)BUFFER[p1,p2]}
>   }
>   zle -N down-case-region
> 
> Unfortunately ${(L)...} and parameter indexing don't handle multibyte
> characters yet, so down-case-word, which is implemented internally,
> should be safer.  You could use some kind of hybrid.
> 
I was hoping for a history modifier eg
^^^ or !!:s///
but they don't seem to support wildcards?


-- 
http://successtheory.com/tips/ Vim, Zsh, MySQL Tips


  reply	other threads:[~2006-06-22 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  9:51 zzapper
2006-06-22 10:25 ` Peter Stephenson
2006-06-22 10:36   ` zzapper [this message]
2006-06-22 10:44     ` Peter Stephenson
2006-06-22 10:59       ` zzapper
2006-06-22 11:06         ` zzapper
2006-06-22 10:40 Artur Penttinen

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=Xns97EA7602A50ECzzappergmailcom@80.91.229.5 \
    --to=david@tvis.co.uk \
    --cc=zsh-users@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).