zsh-users
 help / color / mirror / code / Atom feed
From: Lewis Butler <lbutler@covisp.net>
To: zsh-users@zsh.org
Subject: Re: Parameter subsitution
Date: Fri, 8 Jan 2021 18:09:12 -0700	[thread overview]
Message-ID: <B97E19AD-FA6D-4E9D-A34C-D58BA1BD44A1@covisp.net> (raw)
In-Reply-To: <3D0FA3B2-20E8-49D1-AECD-A8003AB191DC@larryv.me>

On 08 Jan 2021, at 17:00, Lawrence Velázquez <vq@larryv.me> wrote:
>> On Jan 8, 2021, at 6:46 PM, Lewis Butler <lbutler@covisp.net> wrote:
>> 
>> Ah, yes, I can see where that would be useful. I often (used to)
>> do things in bash like `^string^replace` (I think that's right)
> 
> Note that zsh recognizes ^foo^bar as well,

Yep, but I stopped using it years and years ago, long before I used zsh. Heck, before I used bash4.

> and bash recognizes !?foo.

bash versions greater than 3.x?

But I am not using bash anywhere now other than in some shell scripts that didn't work with zsh and I didn't take the time to figure out why

>> Wonder why my zsh is not behaving as your with the recalling of l
>> in the substation though.
>> 
>> $ zsh --version
>> zsh 5.8 (x86_64-apple-darwin20.0)
>> 
>> Maybe something in oh-m-z?
> 
> Perhaps omz is doing its own history expansions that make using a
> null pattern on your command line untenable.

Probably. I'll test without oh-m-z at some point.

-- 
ɹןʇnqן
<mailto:lbutler@covisp.net>
tel:+1.303.219.0564





      parent reply	other threads:[~2021-01-09  1:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 22:02 Lewis Butler
2021-01-08 22:25 ` Bart Schaefer
2021-01-08 22:31   ` Lewis Butler
2021-01-08 22:53     ` Bart Schaefer
2021-01-08 23:46       ` Lewis Butler
2021-01-09  0:00         ` Lawrence Velázquez
2021-01-09  0:49           ` Bart Schaefer
2021-01-09  1:09           ` Lewis Butler [this message]

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=B97E19AD-FA6D-4E9D-A34C-D58BA1BD44A1@covisp.net \
    --to=lbutler@covisp.net \
    --cc=zsh-users@zsh.org \
    /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).