From: Joep van Delft <joepvandelft@xs4all.nl>
To: zsh-workers@zsh.org
Subject: Re: Introducing zsh-hints
Date: Sun, 30 Mar 2014 21:21:00 +0200 [thread overview]
Message-ID: <20140330212100.2bde740c@xs4all.nl> (raw)
In-Reply-To: <53382770.6060008__48065.1685772047$1396191048$gmane$org@eastlink.ca>
Hi Ray,
On Sun, 30 Mar 2014 07:17:20 -0700
Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> > https://github.com/joepvd/zsh-hints
> An interesting looking project. But what is 'the buffer'? Does this
> work at CLI?
The purpose is to get a bunch of information when in the middle of
composing a command (AKA editing the buffer). Here, pressing
<CTRL-X><f> displays parameter expansion flags.
% for i in *; do print ${(on<CTRL-X><f>
@ ▶ array elements
c ▶ count elements of array/string
k,v ▶ returns keys, values of associative array
u ▶ unique, deduplicate entries
A(A) ▶ create (associative) array, useful with
${(A)...=...}
s:string: ▶ field splitting at string
f ▶ split at newlines (ps:\\n:)
z ▶ (Z:opt:) split result into shell words
0 ▶ split with 0-bytes: ps:\\0:
j:string: ▶ join words of array with string as separator
F ▶ join words of array with newlines (pj:\\n:)
w ▶ count words, use s to define word delimiter
W ▶ count words, double delimiters count doubly
i ▶ sort case insensitive. Combine with n, O
n ▶ sort numerically
o ▶ sort in ascending order
O ▶ reverse sort order
a ▶ sort in array index order (with O reversed)
U ▶ convert to uppercase
L ▶ convert to lowercase
V ▶ make special characters visible
...14 hints omitted.
Note that this is on a rather small terminal, some hints needed to be
omitted, and there is a line wrapping at A(A). It is really easy to
change the hints files, so you can just make a list of things you are
currently learning.
I hope it is clearer now.
Kind regards,
Joep
parent reply other threads:[~2014-03-30 19:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53382770.6060008__48065.1685772047$1396191048$gmane$org@eastlink.ca>]
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=20140330212100.2bde740c@xs4all.nl \
--to=joepvandelft@xs4all.nl \
--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).