| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
zman.yo.
The difference was mostly harmless in the common case "(see manref(foo)(42))",
which expanded to "(see man page foo(42))" under ztexi.yo, but in other
contexts the ztexi.yo expansion was was nonsensical; for example:
"the BSD manref(echo)(1) command"
"the string returned by the manref(getlogin)(3) system call"
"advisory file locking (via the manref(fcntl)(2) system call)"
"this is the exact opposite from manref(ls)(1),"
While there, copyedit some uses of manref()().
|
|
|
|
| |
cleans up its tempfiles.
|
|
|
|
|
|
|
|
|
| |
hex dump incantation that may replace some bytes' values with asterisks.
Discussion: https://github.com/zsh-users/zsh/pull/11#issuecomment-457970494 et seq
Incidentally, GitHub #11 is also where workers/39786 (commit
zsh-5.2-578-g74aa45910) was first reported.
|
|
|
|
| |
expansion flags, and add a forward compatibility hatch to the latter.
|
|
|
|
| |
files in the root directory.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Remove calls to programs from /sbin/ with _call_program and to avoid the
system complies to the FHS.
Support modules completion for NixOS and Guix which store their kernel
modules not at /lib/modules.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
processes the current directory rather than the root directory.
The bug will be fixed in the next commit.
|
| |
|
|
|
|
| |
functional change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test harness created tempfiles with a predictable names and sourced
them without verifying they had been created by itself. This opened
anyone who ran the test suite to a symlink attacks from other local
users on the build machine.
Fix this by creating the file whilst NO_CLOBBER and ERR_EXIT are both in
scope, to ensure that we'll abort unless the file really was created as
expected.
Put the existing rm(1) call in a try/always block to help it be unlinked
on test failures, thus reducing the chances of the NO_CLOBBER check
triggering on tempfiles created by earlier test suite runs.
I had first tried to fix this by using the
.
() { ... } =(:)
.
idiom, but couldn't get that to work: it broke the %prep code of X03
with ZTST_verbose unset (its default value) but not with ZTST_verbose=3.
(I tried to set the latter to debug zpty_flush.)
While there, add a needed-in-principle-but-noop-in-this-specific-case (q).
Indentation will be restored in the next commit.
|
| |
|
|
|
|
| |
than a dash.
|
| |
|
|
|
|
| |
See 46090 for details.
|
|
|
|
|
|
| |
qualifier.
This should be easier to read, both as a tutorial and as a reference.
|
|
|
|
|
|
|
|
|
| |
completed to 'foo.bar.baz'.
Now it properly gets completed, but in the case of gpg.openpgp.program,
the description would be shown as "unknown option name", that being the
description of gpg.*.program via `git help -c`, which shadows the
more description of gpg.openpgp.program in $git_options.
|
| |
|
|
|
|
| |
incorrectly offered.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The warning was:
.
warning: passing 'const char *' to parameter of type 'void *'
discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
|
|
|
|
|
|
| |
add-zle-hook-widget support for multiple hook functions.
See workers/46004 for the use-case.
|
|
|
|
| |
ALIAS_FUNC_DEF option.
|
| |
|
| |
|
|
|
|
|
|
| |
This occurs with SH file expansion ordering.
Add test.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is useful when multiple plugins add region_highlight entries and
subsequently want to remove only their own entries. Without this
functionality, recognizing one's region_highlight entries is not trivial
because the 'start' and 'end' offsets are modified by editing of $BUFFER
and the highlight specification may not be unique or distinctive.
The tweaks are as follows:
- Change zfree() to zsfree() per workers/46070.
- Remove the mem.c hunk, as it changed the signature of only one out of
two alternative definitions of zsfree(). (The definition that hunk
touched is the one that's not used by default.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new output is:
./Test/B02typeset.ztst: starting.
Test ./Test/B02typeset.ztst was expected to fail, but passed.
Was testing: this is the description that's after the colon on in the ztst file
./Test/B02typeset.ztst: test XPassed.
**************************************
0 successful test scripts, 1 failure, 0 skipped
**************************************
make[1]: *** [Makefile:190: check] Error 1
make: *** [Makefile:263: check] Error 2
The new function is deliberately very similar to ZTST_testfailed() just
above it.
|
|
|
|
|
|
|
| |
Treat as white space.
This is required for compatibility and previously had no use in zsh
as it generated an error.
|
|
|
|
|
|
|
|
| |
"Topics" is an experimental concept in Mercurial that augments the
current branching concept (called "named branches").
For more information, see the not always up-to-date Mercurial Wiki page
https://www.mercurial-scm.org/wiki/TopicPlan.
|