zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: append to history entry?
Date: Tue, 27 Dec 2016 16:57:48 -0800	[thread overview]
Message-ID: <f87d7f79-3529-d832-eed5-83d4130ea128@eastlink.ca> (raw)
In-Reply-To: <161227155552.ZM2385@torch.brasslantern.com>

On 27/12/16 03:55 PM, Bart Schaefer wrote:
> That's what $'...' does, but you can't ask for a C string and for
> variable interpolation at the same time.  Well, you can, but it
> doesn't really help. ;-)
Indeed.  Be careful what you ask for ... I am expecting the variables to 
expand.
It's all  this backslash and 'is it one string or several strings' 
stuff.  Dunno ...
is that really different?  It just seems that the expansion of the 
variables is 'visible'
for lack of a better word -- you expect it, it's not a gotcha the way 
the rest is.
For me, the task is to see the 'naturalness' for lack of a better word 
of the way
that zsh does this:

     print -rS -- "rap ${${(q+)@}}; : ${(q-)HOST}"

... it seems that the backslashes need protecting and reprotecting and 
yet more
protecting and each stage of the protection is different from the last.  
Couldn't we just:

     setopt protect-backslashes-thanks
     print -S "rap $@; : $HOST"

... it's not that the backslashes are presumed special, it's that I'd 
say we should only have to
press one button once to literalise them.  Is it impossible that this 
could be simple and intuitive?
No ordinary mortal would know to do what you guys showed me, one must be 
shown and even
Bart and Daniel didn't get it exactly right the first time.  What hope 
do I have?

>
> Maybe this would be easier (in the "should have thought of this before"
> category):
>
>      print -s -f '%s' rap "$@" ";" ":" "$HOST"
>
> (Note this doesn't work with -S, which currently is silently ignored if
> the -f option is given, but as you already have all the words separated
> here there's no reason to re-parse them.)
>
I'll chew on that.


  reply	other threads:[~2016-12-28  1:27 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 [this message]
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
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=f87d7f79-3529-d832-eed5-83d4130ea128@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).