From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: append to history entry?
Date: Wed, 28 Dec 2016 23:34:01 +0000 [thread overview]
Message-ID: <20161228233401.GA5901@fujitsu.shahaf.local2> (raw)
In-Reply-To: <3b8fe027-d7fb-25fb-bc05-9ecd3a91b08f__38422.8622112007$1482960347$gmane$org@eastlink.ca>
Ray Andrews wrote on Wed, Dec 28, 2016 at 13:24:25 -0800:
> On 28/12/16 11:20 AM, Ray Andrews wrote:
> >Ok, I'll see what I can figure out.
>
> Needless to say this is exploratory:
>
>
> function zshaddhistory ()
> {
> LITERAL=( "${(@s/;/)1}" )
⋮:
> ... but it seems to do exactly what I want the only thing lacking is
> to associate each member of the array to the appropriate command, if
> there are several on the same line. I can think of a few hacks that
> might do it, but is there a robust way? Would precmd() be able to
> keep count? Something of that nature? This is going to come out
> right.
You can easily convert the string "$1" to a token stream, however, there
is no fully robust way to translate that token stream into a list of
commands without reimplementing the parser.
Just consider the following cases (there are more, but you should get
the gist):
# quoted semicolon
echo lorem\;ipsum
# non-top-level semicolon
(foo; bar); baz
() { foo; bar } baz
for 1 in foo bar; baz $1
# non-semicolon
foo& bar&
case foo in (bar) : ;; esac
# INTERACTIVE_COMMENTS
echo foo # bar ;
What are you trying to do now? This is no longer your original
question about recording the hostname in history.
Is this about 'rap' being called in the middle of a command line…?
Cheers,
Daniel
next prev parent reply other threads:[~2016-12-28 23:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 23:16 Ray Andrews
2016-12-27 1:28 ` Ray Andrews
2016-12-27 4:47 ` Bart Schaefer
[not found] ` <5288b537-f06a-d18a-60ea-1f962856c80c__41345.3811700039$1482803962$gmane$org@eastlink.ca>
2016-12-27 12:55 ` Daniel Shahaf
2016-12-27 16:00 ` Bart Schaefer
2016-12-27 18:23 ` Ray Andrews
2016-12-27 19:09 ` Bart Schaefer
2016-12-27 23:16 ` Ray Andrews
2016-12-27 23:55 ` Bart Schaefer
2016-12-28 0:57 ` Ray Andrews
2016-12-28 6:04 ` Bart Schaefer
2016-12-28 17:39 ` Ray Andrews
2016-12-28 18:22 ` Bart Schaefer
2016-12-28 19:20 ` Ray Andrews
2016-12-28 21:24 ` Ray Andrews
[not found] ` <3b8fe027-d7fb-25fb-bc05-9ecd3a91b08f__38422.8622112007$1482960347$gmane$org@eastlink.ca>
2016-12-28 23:34 ` Daniel Shahaf [this message]
2016-12-29 0:51 ` Bart Schaefer
2016-12-29 3:27 ` Ray Andrews
[not found] ` <f87d7f79-3529-d832-eed5-83d4130ea128__16005.139592062$1482888562$gmane$org@eastlink.ca>
2016-12-28 5:28 ` Daniel Shahaf
2016-12-28 6:31 ` Bart Schaefer
2016-12-28 16:33 ` Ray Andrews
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=20161228233401.GA5901@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=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).