From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: history puzzle
Date: Wed, 5 Jun 2024 09:13:25 -0700 [thread overview]
Message-ID: <d751180a-4b6b-4153-af03-a0113e7694a8@eastlink.ca> (raw)
In-Reply-To: <CAA=-s3yrBmy4LZcA3awCJarLanVoSBCXwnzErkuDoMBMe_NODg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On 2024-06-05 08:53, Mark J. Reed wrote:
>
> History expansion is purely an interactive command-line feature; it
> doesn't work in scripts. If you need to access the history
> programmatically, use the *fc* command (or *history*, which is
> equivalent to *fc -l*).
>
> Anyway, that's what you were reading about. :)
I wish I could kill the whole thread, it was a misunderstanding from the
getgo. Not the first time I've ended up barking up entirely the wrong
tree. And with hindsight it is obvious I wasn't looking at a command --
but I'm so used to being baffled by the manual that I took it as normal ;-)
> --
> Mark J. Reed <markjreed@gmail.com>
[-- Attachment #2: Type: text/html, Size: 2130 bytes --]
next prev parent reply other threads:[~2024-06-05 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 18:00 Ray Andrews
2024-06-04 18:12 ` Mark J. Reed
2024-06-04 19:28 ` Lawrence Velázquez
2024-06-04 19:52 ` Ray Andrews
2024-06-04 20:18 ` Lawrence Velázquez
2024-06-04 19:49 ` Ray Andrews
2024-06-04 20:19 ` Lawrence Velázquez
2024-06-04 20:37 ` Mark J. Reed
2024-06-04 23:51 ` Ray Andrews
2024-06-04 23:48 ` Ray Andrews
2024-06-05 0:33 ` Lawrence Velázquez
2024-06-05 2:00 ` Ray Andrews
2024-06-05 15:53 ` Mark J. Reed
2024-06-05 16:13 ` Ray Andrews [this message]
2024-06-04 18:54 ` Kannan Varadhan
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=d751180a-4b6b-4153-af03-a0113e7694a8@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).