zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: _arguments and state_descr (Re: Next release)
Date: Mon, 12 Dec 2011 10:15:29 -0800	[thread overview]
Message-ID: <111212101529.ZM1878@torch.brasslantern.com> (raw)
In-Reply-To: <20111212164626.16c7234c@pwslap01u.europe.root.pri>

On Dec 12,  4:46pm, Peter Stephenson wrote:
}
} Well, you could call it "state_message", or perhaps better
} "state_messages".

I'd call it "state_messages" if "state" were also plural, but neither
that nor "context" is.

I'm tempted toward just "message" to go with the other two, but we
probably should be sticking with things unlikely to clash with other
names in the scope ... so I guess I'll just leave it "state_descr"
if no one has a strong opinion.


  reply	other threads:[~2011-12-12 18:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 14:11 Next release Peter Stephenson
2011-12-09 16:37 ` Bart Schaefer
2011-12-09 16:42   ` Peter Stephenson
2011-12-12 16:28     ` _arguments and state_descr (Re: Next release) Bart Schaefer
2011-12-12 16:46       ` Peter Stephenson
2011-12-12 18:15         ` Bart Schaefer [this message]
2011-12-09 19:50 ` Next release Frank Terbeck
2011-12-10 17:19   ` Peter Stephenson
2011-12-10 19:20     ` Frank Terbeck
2011-12-10 19:46       ` Peter Stephenson
2011-12-10 19:55         ` Frank Terbeck
2012-01-24 13:03         ` ChangeLog generation (was: Re: Next release) Frank Terbeck
2012-01-24 19:06           ` Peter Stephenson
2012-01-25  0:26             ` ChangeLog generation Frank Terbeck
2012-01-24 19:40           ` ChangeLog generation (was: Re: Next release) Bart Schaefer
2012-01-25  0:59             ` ChangeLog generation Frank Terbeck
2011-12-09 23:38 ` Next release Phil Pennock

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=111212101529.ZM1878@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).