zsh-workers
 help / color / mirror / code / Atom feed
From: Joey Pabalinas <joeypabalinas@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH 2/3] jp: Use `(nil)` for empty identifier strings
Date: Sun, 14 Jan 2018 06:55:53 -1000	[thread overview]
Message-ID: <20180114165553.ufnky2uhchdiczs4@gmail.com> (raw)
In-Reply-To: <1515944588.1617081.1234892696.1AED867B@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

On Sun, Jan 14, 2018 at 03:43:08PM +0000, Daniel Shahaf wrote:
>
> How about inventing an %ls expando that emits the argument quoted, so
> zerr("%ls", foo) would print ${(qq)foo} or ${(q-)foo}.  That seems easier
> than updating all callsites (not just these three).
> 
> (%ls/%s by analogy with %ld/%d.)

If only it were so easy :( All that `zerr()` does is pass the
`va_list` to `zerrmsg()` and i didn't want to touch too many
things.

I like the idea though, actually. So if i messed around with
implementing things in `zerrmsg()` would the "" or '' format
be better than bothering with (nil) at all?

-- 
Joey Pabalinas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-14 16:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14 15:23 [PATCH 0/3] jp: Patchset for parameter expansion segfaults Joey Pabalinas
2018-01-14 15:23 ` [PATCH 1/3] jp: Fix segfaults during parameter expansion Joey Pabalinas
2018-01-14 15:23 ` [PATCH 2/3] jp: Use `(nil)` for empty identifier strings Joey Pabalinas
2018-01-14 15:43   ` Daniel Shahaf
2018-01-14 16:55     ` Joey Pabalinas [this message]
2018-01-14 20:30   ` Bart Schaefer
2018-01-14 15:23 ` [PATCH 3/3] jp: Add `dupstring()` fallback to `zhtricat()` Joey Pabalinas
2018-01-14 15:29   ` Joey Pabalinas
2018-01-21 17:56     ` Bart Schaefer
2018-01-14 20:41 ` [PATCH 0/3] jp: Patchset for parameter expansion segfaults Bart Schaefer
2018-01-18 22:58   ` Joey Pabalinas

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=20180114165553.ufnky2uhchdiczs4@gmail.com \
    --to=joeypabalinas@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --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).