zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: alias hygiene
Date: Sat, 17 Feb 2018 16:17:12 -0800	[thread overview]
Message-ID: <05e4360b-4989-af2b-70b6-79c2aef06f95@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7YnA=gCth1wjWyB4CnLV0oURozaDFjTRtKiXzkfFEJq7A@mail.gmail.com>

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

On 17/02/18 02:04 PM, Bart Schaefer wrote:
> On Sat, Feb 17, 2018 at 7:42 AM, Ray Andrews <rayandrews@eastlink.ca> wrote:
>> Ok, that at least is good to know.  Now I have to figure out from your
>> example what a widget is, I've heard the term but so far I have no clue what
>> sort of critter they might be.
> A "widget" is just an arbitrary thing that you've built.  It's like
> using the word "foo" as a placeholder for an abstract value.  As far
> back as I remember, a "widget" was used in economics to refer to an
> unspecified object, such as a consumer good or a machine part, that
> was manufactured by a hypothetical factory or sold by a hypothetical
> wholesaler or retailer, but you can probably find earlier meanings
> with an etymology search.  When windowing UIs became a thing back in
> the 80s it got retconned into a portmanteau of "window gadget" and
> used to describe components of the desktop.  Zsh borrowed the term to
> refer to the chunk of programming, whether C or shell function, that
> implements a named and therefore bindable operation in the ZLE editor.
>
That doesn't sound too terrible, not some actualnew construction? So a 
function can be a widget? Show me one that I can understand and then 
I'll stop imagining that it's some new horror.  When would I call 
something a widget, not a function? When it's associated with ZLE?  
Yeah, that sounds about right.



  reply	other threads:[~2018-02-18  0:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 16:09 Ray Andrews
2018-02-17  0:30 ` Daniel Shahaf
2018-02-17  3:14   ` Ray Andrews
2018-02-17 13:54     ` Daniel Shahaf
2018-02-17 15:20       ` Ray Andrews
2018-02-17 15:30         ` Daniel Shahaf
2018-02-17 15:42           ` Ray Andrews
2018-02-17 22:04             ` Bart Schaefer
2018-02-18  0:17               ` Ray Andrews [this message]
2018-02-18  2:10                 ` Bart Schaefer
2018-02-18  3:38                   ` Ray Andrews
2018-02-19  6:37                     ` Bart Schaefer
2018-02-27 13:48           ` Vincent Lefevre
2018-02-27 15:26             ` Ray Andrews
2018-02-17 15:36       ` Daniel Shahaf
2018-02-17 21:40     ` Bart Schaefer
2018-02-18  0:08       ` Ray Andrews
2018-02-19  6:28   ` Bart Schaefer
2018-02-19 18:14     ` Ray Andrews

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=05e4360b-4989-af2b-70b6-79c2aef06f95@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=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).