zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: NEWS updated for 5.0.
Date: Sat, 14 Apr 2012 11:03:22 -0700	[thread overview]
Message-ID: <120414110322.ZM8688@torch.brasslantern.com> (raw)
In-Reply-To: <20120413231453.0a141084@pws-pc.ntlworld.com>

On Apr 13, 11:14pm, Peter Stephenson wrote:
}
} +- The zshroadmap manual page provides a slightly more helpful
} +  introduction to the shell manual than was available hitherto.

"Hitherto"?  No worries about talking over the audience's head, I
guess. :-)

} +- The parameter expansion flag (D) abbreviates directories in parameters
} +  using the familiary ~ form.

Unless Tilde is the name of your housekeeper, you mean familiar.

} +- The parameter subscript flag (e) forces the argument to be treated
} +  as a string, never a pattern, e.g. ${array[(ie)*]} looks for the
} +  index of the array element containing the literal string "*".

Wow, is that really new since 4.2 ?

} +- New prompt escapes:
} +  %x and %I show source file and line number, usefil
} +    in $PS4 (the existing %N and %i show names and lines in the execution
} +    environment rather than the source file).

Why the strange line lengths?  Also, "useful".

} +  KEYBOARD_HACK defines characters to be ignored if typed unmatched at
} +    the end of the line (an extension of the SUN_KEYBOARD_HACK option).

I believe it's still the case that touching SUN_KEYBOARD_HACK will clobber
the value of KEYBOARD_HACK.  This is the case no matter what value the
option has to start with, and even clobbers the global parameter if a shell
function sets or unsets SUN_KEYBOARD_HACK, in spite of LOCAL_OPTIONS.

} +  ZSH_PATCHLEVEL provides a unique indication of the code compiled to
} +    make the shell even between releases.

Comma after "shell"?  The shell is not being made even (or odd).

} +  ZSH_SUBSHELL indicates the subshell live, incremented once per fork, at
} +    which the code is being run.

s/live/level/

} +  HASH_EXECUTABLES_ONLY: don't insert non-executable files into the
} +    command hash used e.g. by completion.  This may be very slow
} +    on network paths.

This could be misinterpreted as advice that you *should* set the option
when you have network paths, but I'm having a hard time rewording it.
"Setting this option may slow down shell startup if there are networked
directories in the path." ??

} +  MULTI_FUNCDEF (on by default): "foo bar () { ... }" defines two
} +    functions.  This is often found to be confusing and bug-prone.

... so you may want to unset this.

} +- The undo widget takes an argument, a previuos value of $UNDO_CHANGE_NO.

previous

That's all I saw.  Thanks for writing this up.

-- 
Barton E. Schaefer


      parent reply	other threads:[~2012-04-14 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 22:14 Peter Stephenson
2012-04-14 17:21 ` Mikael Magnusson
2012-04-14 18:03 ` 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=120414110322.ZM8688@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).