zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Index of element after width of characters
Date: Wed, 28 Oct 2015 08:54:54 +0100	[thread overview]
Message-ID: <CAKc7PVD=H+e9tyrVSM-TbwzFjKs=cAygNC0yzkO=uuNFEH7PjQ@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVCGFJSZbiHDpJHivFco8J3SfHDesdjJoTzAY-sR4K5++w@mail.gmail.com>

On 28 October 2015 at 08:46, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> I've counted actual flags, there are 42 of them, so there seems to be
> room for 10 of them (2*26 letters of English alphabet), 8 with my two
> patches. That might be not much. Plus symbols it's more, maybe this
> helps. I could use "-" and "," for the patches, it's quite mnemonic –
> it would look like ${(-:10:)a}, ${(,:9:)a} - the number is a limit,
> "-" is before limit, "," is after limit. Thought about "," and ".",
> but "." feels more like "at limit", while "," as "after limit". Minus
> feels like "before limit" so "-", "," it's quite fine, even better
> than "x", "y".

Could also code '.' as "at limit". It would be empty when the limit
doesn't divide any char into half, and return the char (as index) in
other case. This would be a full support of any string operations
where width counts. I'm heating up the already hard to grasp intuition
of the flags, hoping for better end effect.

Best regards,
Sebastian Gniazdowski


  reply	other threads:[~2015-10-28  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 17:18 Sebastian Gniazdowski
2015-10-27 19:41 ` Mikael Magnusson
2015-10-27 19:55 ` Sebastian Gniazdowski
2015-10-27 21:20 ` Bart Schaefer
2015-10-28  7:46   ` Sebastian Gniazdowski
2015-10-28  7:54     ` Sebastian Gniazdowski [this message]
2015-10-28 11:38       ` Sebastian Gniazdowski
2015-10-28 13:31         ` Mikael Magnusson
2015-10-28 15:46           ` Sebastian Gniazdowski
2015-10-28 15:59             ` Peter Stephenson
2015-10-28 16:37               ` Sebastian Gniazdowski
2015-10-28 23:07               ` Bart Schaefer
2015-10-29  9: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='CAKc7PVD=H+e9tyrVSM-TbwzFjKs=cAygNC0yzkO=uuNFEH7PjQ@mail.gmail.com' \
    --to=sgniazdowski@gmail.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).