zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: .zsh_history
Date: Fri, 14 Apr 2023 08:27:58 -0700	[thread overview]
Message-ID: <9a1f77ea-ee4e-95ff-a571-5cd3ddce6cb2@eastlink.ca> (raw)
In-Reply-To: <CAMP44s1dYQ=YWufkDYRcwtWvpuo0PV=M4hSZQ8gmMfF45DRfMQ@mail.gmail.com>


On 2023-04-14 07:36, Felipe Contreras wrote:

> I do remember that one's control of history is essentially perfect, you
>> can get just about anything you want.  History is one of those features
>> of zsh that is tractable and understandable without too much head
>> scratching and without any weird gotchas.
> I couldn't disagree more.
>
It could very well be that a closer examination than I've made would 
reveal various mysteries and gotchas.  All I can say is that I've never 
wanted something from history that it couldn't provide.  One exception: 
"$ echo one; echo two; echo three" ... you can't, AFAICT, break up the 
line into it's component commands.  One of the first brick walls I 
crashed into learning zsh was realizing that a command has no access to 
it's own unexpanded, 'raw' tail -- which still strikes me as 
incomprehensible.   Pulling a command back from history comes closest, 
but again there's that 'many commands on one line' issue.  I'd sure love 
to be able to pull just the text of a single command.





  reply	other threads:[~2023-04-14 15:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08 16:16 .zsh_history Perry Smith
2023-04-08 16:53 ` .zsh_history Roman Perepelitsa
2023-04-08 17:23   ` .zsh_history Ray Andrews
2023-04-08 17:27     ` .zsh_history Roman Perepelitsa
2023-04-08 17:35       ` .zsh_history Perry Smith
2023-04-08 17:54       ` .zsh_history Ray Andrews
2023-04-14 14:36         ` .zsh_history Felipe Contreras
2023-04-14 15:27           ` Ray Andrews [this message]
2023-04-15  4:49             ` .zsh_history Felipe Contreras
2023-04-15 15:29               ` .zsh_history Ray Andrews
2023-04-15 19:47                 ` "Pull just the text of a single command" (was Re: .zsh_history) Bart Schaefer
2023-04-15 22:47                   ` Ray Andrews
2023-04-15 23:26                     ` Bart Schaefer
2023-04-16 15:53                       ` Bart Schaefer
2023-04-16 16:37                         ` Ray Andrews
2023-04-16 19:24                         ` Ray Andrews
2023-04-16  7:38                 ` .zsh_history Roman Perepelitsa
2023-04-16 14:53                   ` .zsh_history Ray Andrews
2023-04-16 15:28                     ` .zsh_history Bart Schaefer
2023-04-16 15:29                     ` .zsh_history Roman Perepelitsa
2023-04-14 14:28     ` .zsh_history Felipe Contreras
2023-04-14 15:18       ` .zsh_history Ray Andrews
2023-04-14 14:00   ` .zsh_history Felipe Contreras
2023-04-14 14:51 ` .zsh_history Felipe Contreras

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=9a1f77ea-ee4e-95ff-a571-5cd3ddce6cb2@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).