about summary refs log tree commit diff
Commit message (Collapse)AuthorAgeFilesLines
* Change DECLAREDNULL to DEFAULTEDBart Schaefer2021-04-103-12/+12
|
* Fix ${(t)var} output, add comparative test casesBart Schaefer2021-04-103-1/+31
|
* Missed files from POSXIBUILTINS commitBart Schaefer2021-04-102-8/+9
|
* Make DECLAREDNULL require POSIXBUILTINS and introduce a new test file.Bart Schaefer2021-04-101-0/+105
| | | | V10private has been made agnostic to POSIXBUILTINS.
* Final repairs for declared state of tied arraysBart Schaefer2021-04-102-2/+7
| | | | Fixups still required in bin_typeset, but assignments to scalar work.
* Additional tied-array cleanup when tied scalar had a previous valueBart Schaefer2021-04-101-3/+3
|
* Unset of a tied local scalar previously left it using tiedarr_gsuBart Schaefer2021-04-101-0/+2
|
* Partial fix for handling of tied arrays.Bart Schaefer2021-04-101-0/+6
| | | | | | | | | | | | As of this commit when a tied array is declared but neither the scalar nor the array has an initializer, the array is initialized to empty. The scalar struct param of a tied pair stores a direct pointer to the internal array value of the array struct param, and upon assignment modifies it without referring to the containing struct. This means that there's no opportunity to clear the PM_DECLAREDNULL bits on both structs when the scalar is assigned. Conversely, assigning to the array does use the struct for the scalar.
* Choose a better bit-value for PM_DECLAREDBart Schaefer2021-04-101-1/+1
|
* Add PM_DECLARED and PM_DECLAREDNULL parameter flags.Bart Schaefer2021-04-105-5/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | This addresses the issue that "typeset foo" creates $foo set to an empty string, which differs from typeset handling in bash and ksh. It does this by concealing the internal value rather than alter the way internal values are defaulted. This imposes the following changes: A typeset variable with no assignment triggers NO_UNSET warnings when the name is used in parameter expansion or math. The typeset -AEFHLRTZailux options are applied upon the first assignment to the variable. Explicit unset before the first assignment discards all of those properties. If any option is applied to an existing name, historic behavior is unchanged. Consequent to the foregoing, the (t) parameter expansion flag prints nothing until after the first assignment, and the (i) and (I) subscript flags also print nothing. The bash behavior of "unset foo; typeset -p foo" is NOT used. This is called out as an emulation distinction, not a change. The test cases have not been updated, so several now fail. The test harness has been updated to declare default values.
* 48338: _git: Support case-insensitive path matchingdana2021-04-102-3/+13
|
* 48432 and enable test: fix quotiing of zstyle -L for zstyle -ePeter Stephenson2021-04-093-2/+9
|
* 48378: complete compadd options for other completion functionsOliver Kiddle2021-04-092-37/+87
|
* 48437: fix pid completion when cursor is in the middle of the lineOliver Kiddle2021-04-092-2/+5
|
* 47786: prepare for autoconf 2.70Felipe Contreras2021-04-093-56/+59
|
* 47785: remove deprecated autoconf functionsFelipe Contreras2021-04-095-40/+12
| | | | STDC_HEADERS and TIME_WITH_SYS_TIME are deprecated.
* 48416: update _gcore for macOS and GNUJun-ichi Takimoto2021-04-082-3/+18
|
* 48410: FAQ, METAFAQ: Mention zsh-security@.Daniel Shahaf2021-04-083-1/+15
|
* 48379: Make the parameter expansion subscript flags parse error message, ↵Daniel Shahaf2021-04-083-3/+34
| | | | "error in flags", identify the location of the parse error.
* 48321 (tweaked per thread): _perl_modules: Don't assume ${words[1]} to be ↵Daniel Shahaf2021-04-082-5/+11
| | | | | | | either "perl" or "perldoc" Also, correct an always-true condition guarding the fallback @INC codepath.
* 48425: Add an XFail test for a 'zstyle -L' escaping bug (workers/48424).Daniel Shahaf2021-04-072-0/+14
|
* 48391: fix display problem in menu-completeJun-ichi Takimoto2021-04-062-1/+4
| | | | | Take account of the trailing file type character even when '-d disp' is given to compadd.
* 48389: getkeystring() should not return ptr to local varJun-ichi Takimoto2021-04-063-9/+36
| | | | | Now it returns NULL if called with GETKEY_SINGLE_CHAR and next character is not found. Caller must check the return value.
* users/26579: changes from review including parameter expansion to replace awkMarc Chantreux2021-04-062-13/+20
|
* 48414: quote closing bracket to adapt for change in 43928Oliver Kiddle2021-04-062-1/+4
|
* 48413: Fix _expand completion testMarlon Richert2021-04-063-7/+10
|
* unposted: add several references to bugs in old list postsOliver Kiddle2021-04-062-1/+11
|
* unposted: FAQ: Move the 'The mailing lists have moved' notice to a more ↵Daniel Shahaf2021-04-052-3/+8
| | | | appropriate place.
* 47784: silence a compiler waring from pattern.cFelipe Contreras2021-04-042-1/+4
|
* 48218 (+ 48354): various improvements for _gccJacob Gelbman2021-04-042-989/+2057
|
* 47510: drop code that avoided termcap for named coloursOliver Kiddle2021-04-033-44/+16
| | | | | | The inconsistency caused test failures where TERM is e.g. rxvt-unicode. This also makes a couple of bits available in zattr by removing flags indicating whether to use termcap which is not an attribute as such.
* 48356: clarify (the intended) behaviour for the two anchor forms of matching ↵Oliver Kiddle2021-04-032-2/+12
| | | | control
* unposted: BUGS: Add 39319, a named-file process substitution cleanup bug.Daniel Shahaf2021-04-012-0/+7
|
* 48202 + 48366: Fix handling of NUL bytes in zexpandtabs multibyte versionMikael Magnusson2021-04-013-5/+15
|
* github #74: Drop vcsh completions, maintained upstreamCaleb Maclennan2021-03-312-89/+3
| | | | | | See discussion on upstream project here: https://github.com/RichiH/vcsh/issues/270
* 48214: add file types to _expand completions, so they can be colored through ↵Marlon Richert2021-03-313-4/+28
| | | | complist
* 48192: Fix _openstack completion for new style clientsSyphdias2021-03-312-53/+67
|
* users/26557: add bookmarks support and remove the header from the final list ↵Marc Chantreux2021-03-312-2/+21
| | | | in surfraw completion
* 47561 (the git and cvs parts) (compare 44919 + 44920): vcs_info internals: ↵Aleksandr Mezin2021-03-295-13/+28
| | | | | | | cvs, git: Set ${vcs_comm[basedir]} like all other backends do. That doesn't affect anything, not even other vcs_info internals; it's just for consistency across backends.
* 47737: _zstyle: Fix option completion when positional arguments are already ↵dana2021-03-292-2/+8
| | | | | | | | | | | | | | present (regression from workers/39659 (commit ae3b675ce6e4ac62451ea08169c2b4dc45cf533b)) The following case: LBUFFER='zstyle -' RBUFFER=' foo bar' Before this patch, completed 'context pattern' (from the first positional argument). With this patch, completes options, which is correct.
* unposted: ChangeLog: Fix X-Seq numbers for the 39657, 39658, 39659 patch series.Daniel Shahaf2021-03-291-2/+5
|
* unposted: docs: _arguments: Fix a typo in the example.Daniel Shahaf2021-03-292-1/+6
|
* 48166: add completion for ctags language optionsJacob Gelbman2021-03-292-199/+249
|
* 48210: Introduce new completion for setpriv(1) on LinuxArseny Maslennikov2021-03-282-0/+110
|
* 48212: Introduce new completion for Linux task capabilitiesArseny Maslennikov2021-03-282-0/+68
|
* 48231: add missing git --pretty formats and improve descriptionsŠtěpán Němec2021-03-282-7/+12
|
* 48230, 48233 (Jun T): completion of dtrace probes and runtime optionsOliver Kiddle2021-03-282-38/+154
|
* 48216: Fix broken Y01 test from workers/48180dana2021-03-282-0/+8
|
* 48131/0004: FAQ: 3.31: RearrangeDaniel Shahaf2021-03-262-14/+21
|
* 48131/0003: FAQ: 3.31: Move two paragraphs unchanged, reordering themDaniel Shahaf2021-03-262-14/+20
| | | | | | | | | | | | | Factored out from the next patch for readability of the diff. The answer, as it stands in this commit, doesn't flow correctly. In order to keep the diffs small and easy to follow, this commit simply adds a TODO to record this issue, a TODO which is fixed by the next commit in this series (the child of this commit). Thus, a request: DEAR PEOPLE FROM THE FUTURE: Please don't create new branches off this commit; create them off the parent commit or off the child commit instead. Thank you.