From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: subsitutions and beginning of lines.
Date: Mon, 12 Oct 2015 19:29:08 -0700 [thread overview]
Message-ID: <151012192908.ZM15508@torch.brasslantern.com> (raw)
In-Reply-To: <561BE8DC.7060506@eastlink.ca>
On Oct 12, 10:07am, Ray Andrews wrote:
}
} ... Each search parameter is colorized incrementally. (I add the minus
} sign automatically) It now strips off the leading stuff as we've
} discussed. Code as I have it now is:
}
} OLDIFS=$IFS
} IFS=$'\n' var=($(eval history $nnumber $sstring))
}
} echo "${(F)var[@]//#???????/}"
} IFS=$OLDIFS
}
} So, the 'eval'ed expression ends up like:
}
} 'history -100 | grep --color=always to | grep --color=always 'a date' | ... '
If you're using "grep" to do the colorizing, there's no point in using
the $history variable to get the history entries, because you need them
to end up on stdout for passing through grep anyway.
(Generic advice to anyone reading this: Asking about one small piece of
a larger problem is quite likely to get you an inappropriate solution.
Context is important.)
} the outputno longer lines up because double spaces become single
} spaces whereas double spaces are needed for the brutal ' //#???????/'
} substitution to work properly.
Why not simply use "history -n" so the numbers are omitted in the first
place? Then you don't need to assign to var=(...) and apply //#.../.
That whole chunk of code just reduces to
eval history -n $nnumber $sstring
and you're done.
next prev parent reply other threads:[~2015-10-13 2:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 19:12 Ray Andrews
2015-10-11 20:09 ` Peter Stephenson
2015-10-11 23:05 ` Ray Andrews
2015-10-12 9:34 ` Peter Stephenson
2015-10-12 15:44 ` Ray Andrews
2015-10-12 17:07 ` Ray Andrews
2015-10-13 2:29 ` Bart Schaefer [this message]
2015-10-13 2:50 ` Ray Andrews
2015-10-13 5:03 ` Bart Schaefer
2015-10-13 5:24 ` Ray Andrews
2015-10-13 19:58 ` Bart Schaefer
2015-10-13 21:42 ` Ray Andrews
2015-10-14 0:23 ` Bart Schaefer
2015-10-14 5:03 ` Ray Andrews
2015-10-12 2:26 ` Daniel Shahaf
2015-10-12 15:53 ` Ray Andrews
2015-10-12 16:42 ` Peter Stephenson
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=151012192908.ZM15508@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).