zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Workers <zsh-workers@zsh.org>
Subject: Re: !!$ unitialized at first prompt
Date: Fri, 24 Sep 2010 23:53:32 -0700	[thread overview]
Message-ID: <100924235332.ZM5186@torch.brasslantern.com> (raw)
In-Reply-To: <20100924211247.626449fb@pws-pc>

On Sep 24,  9:12pm, Peter Stephenson wrote:
}
} The mechanism for word splitting in the manner of the (z) flag is a
} bit iffy. I've picked up that newlines get turned into semicolons ---
} there was a discussion about this recently --- and also that &! turns
} into &|, which I didn't know about.

Now that you mention it, I'll bet >! also turns into >| ... but it
appears your test is generic enough to handle that.

Another history oddity that this brings to mind is that "print -s"
puts each of its arguments into the history as a separate word, but
on reload those will be re-parsed and are likely to end up with new
word boundaries.

It's unlikely there's anything useful to be done about this, but now
that we have the zshaddhistory hook and people are manipulating what
gets stored by calling "print -s", it may be worth pointing out.


  reply	other threads:[~2010-09-25  6:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  4:36 Benjamin R. Haskell
2010-09-24  4:43 ` Benjamin R. Haskell
2010-09-24 11:48   ` Mikael Magnusson
2010-09-24 12:39     ` Peter Stephenson
2010-09-24 14:18       ` Benjamin R. Haskell
2010-09-24 14:26         ` Peter Stephenson
2010-09-24 15:30           ` Bart Schaefer
2010-09-24 15:10       ` Bart Schaefer
2010-09-24 15:20         ` Mikael Magnusson
2010-09-24 20:12         ` Peter Stephenson
2010-09-25  6:53           ` Bart Schaefer [this message]
2010-09-25 17:26             ` Wayne Davison
2010-09-25 18:49               ` Peter Stephenson
2010-09-26  1:14                 ` Bart Schaefer

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=100924235332.ZM5186@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).