zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <Peter.Stephenson@csr.com>
To: zsh-workers <zsh-workers@zsh.org>
Subject: Re: 'r' history parameter documentation fix
Date: Mon, 25 Jul 2011 13:40:18 +0100	[thread overview]
Message-ID: <20110725134018.445c0ccf@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <8762mq4kb7.fsf@gmail.com>

On Mon, 25 Jul 2011 14:27:24 +0200
Štěpán Němec <stepnem@gmail.com> wrote:
> > Remove a filename extension leaving the root name.  Strings with no
> > filename extension are not altered.  For this purpose, a filename
> > extension is a `tt(.)' followed by any number characters (including
>                                                ^
>                                                of
> > zero) that are neither `tt(.)' nor `tt(/)' and that continue to the end
> > of the string.  For example, the extension of
> > `tt(foo.orig.c)' is `tt(.c)', and `tt(dir.c/foo)' has no extension.
> 
> Quite clear to me. (Except that I'd still prefer just leaving the
> explanation out than opening this can of worms -- for instance, although
> it might seem far-fetched, the "for this purpose" thing made me wonder
> "Hm, is this supposed to imply that Zsh also might have other notions of
> file extensions in other contexts?"

I'll remove "for this purpose".

> Everybody knows what a file extension is, right?)

I think it's worth being explicit.  For example, it's probably obvious
to a geek that alongfilename.withalongbitontheend has a file extension,
but a casual shell user might say "surely that's too long to be an
extension?  aren't they limited to three characters, or something?",
or they might not realise "manpage.3" had an extension ("surely they've
got to be alphabetic, or something"?) and it's not necessarily clear
whether "foo." has an extension "." or no extension.  Etcetera.

-- 
Peter Stephenson <pws@csr.com>            Software Engineer
Tel: +44 (0)1223 692070                   Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog


  reply	other threads:[~2011-07-25 12:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23  6:37 Jesse Weinstein
2011-07-25  8:34 ` Bart Schaefer
2011-07-25 10:06   ` Štěpán Němec
2011-07-25 10:15     ` Peter Stephenson
2011-07-25 11:45       ` Štěpán Němec
2011-07-25 11:57         ` Peter Stephenson
2011-07-25 12:27           ` Štěpán Němec
2011-07-25 12:40             ` Peter Stephenson [this message]
2011-07-25 13:30               ` Manuel Presnitz
2011-07-25 13:32               ` Štěpán Němec
2011-07-25 13:41               ` Benjamin R. Haskell
2011-07-25 13:47                 ` Peter Stephenson
2011-07-26  0:47   ` Jesse Weinstein

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=20110725134018.445c0ccf@pwslap01u.europe.root.pri \
    --to=peter.stephenson@csr.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).