zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: set -A and stat -A vs. typeset -A and stat -H
Date: Fri, 29 Jan 1999 22:22:17 -0800	[thread overview]
Message-ID: <990129222217.ZM10257@candle.brasslantern.com> (raw)
In-Reply-To: <19990128175016.A24442@fysh.org>

On Jan 28,  5:50pm, Phil Pennock wrote:
} Subject: Re: set -A and stat -A vs. typeset -A and stat -H
}
} Generally, I have no objections whatsoever to changing [stat -H].  I
} was just gratified to see someone modify the examples to make use of my
} addition.  A nice warm fuzzy feeling inside... :^)

Here's an idea ... simply use `stat -A' for both, and have stat examine
the type of the parameter to which it's assigning to choose the behavior.
For that to work cleanly, though, stat would have to refuse to create a
parameter that didn't already exist.

`set -A' could do the same, for that matter, though it's been around a
lot longer so it probably couldn't get away with refusing to create new
parameters.

} Erm, Bart, is that the first time that you've used a smiley on the
} zsh-workers list?  :^)  *ducks*

No, it isn't the first time, but a while back someone I worked with used
smileys so often that they became meaningless/annoying to everyone else,
and consequently I pretty much stopped using them unless my meaning might
be completely misconstrued without one.

} Anyway, back on topic.  Given all this overloading in typeset and set,
} how feasible is it to do a split-out, similar to the completion stuff
} recently?

One can do almost anything with modules, except modify the lexer/parser.

} Ie, carefully examine the functionality requirements, add (I
} suspect) three new builtins, organise the options consistenly for those.

What three are you thinking of?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1999-01-30  6:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-28  9:47 Bart Schaefer
1999-01-28 13:23 ` Phil Pennock
1999-01-28 17:33   ` Bart Schaefer
1999-01-28 17:43     ` Bruce Stephens
1999-01-28 17:50     ` Phil Pennock
1999-01-30  6:22       ` Bart Schaefer [this message]

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=990129222217.ZM10257@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).