zsh, branch declarednull[no description]http://git.sudomsg.com/mirror/zsh/atom/?h=declarednull2021-04-14T04:30:06ZMerge branch 'typesettounset' into declarednull2021-04-14T04:30:06ZBart Schaeferschaefer@ipost.com2021-04-14T04:30:06Zurn:sha1:f85cb4504561df0b486e3e140d4c0434516a0f7f
Adds 'setopt typeset_to_unset', documentation, failure tests for POSIX incompatibilies, etc.
unposted (cf. 48469): document oddness of ${emptystr[(i)]}.2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2021-04-10T19:22:43Zurn:sha1:0793ce4e61290d15ee7e53c15a2b8425e20c806cChange DECLAREDNULL to DEFAULTED2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2021-03-27T21:04:05Zurn:sha1:fbc1125316b07ddc9d51fa032fffc5b09b98f2acFix ${(t)var} output, add comparative test cases2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-27T22:36:35Zurn:sha1:f621fb7ab8ba9a7d4992a45b4b1033e7ef897154Missed files from POSXIBUILTINS commit2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-18T05:08:47Zurn:sha1:dcd4439a9f3a2212d753ece6ef644aed2ec4d333Make DECLAREDNULL require POSIXBUILTINS and introduce a new test file.2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-10T05:32:36Zurn:sha1:3099e79d25cd1cb1f718a060eadb4bb55080d816
V10private has been made agnostic to POSIXBUILTINS.
Final repairs for declared state of tied arrays2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-05T00:14:28Zurn:sha1:69bd4a197c0df766d84dcaadbd76bc7a8e94a6ce
Fixups still required in bin_typeset, but assignments to scalar work.
Additional tied-array cleanup when tied scalar had a previous value2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-04T23:09:14Zurn:sha1:733c166115841e42c39a5a11fed0a3e79b12d7d1Unset of a tied local scalar previously left it using tiedarr_gsu2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-04T22:46:19Zurn:sha1:ec4093659ba316e8fb1ba0559457c72ba450ca99Partial fix for handling of tied arrays.2021-04-14T04:18:35ZBart Schaeferschaefer@ipost.com2020-12-04T06:30:04Zurn:sha1:709af2bf3c7eba33c1425b2dcd2071a2c5bb1179
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_DECLARED2021-04-14T04:18:34ZBart Schaeferschaefer@ipost.com2020-11-28T19:25:23Zurn:sha1:d0a25afe323abe0183c2a530c5324e7e93426b64Add PM_DECLARED and PM_DECLAREDNULL parameter flags.2021-04-14T04:18:34ZBart Schaeferschaefer@ipost.com2020-11-28T17:23:10Zurn:sha1:dddae7f05582c6c8e91501dbea6106636cd76f6c
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.
48522: README: Clarify _alternative change2021-04-13T21:54:03ZDaniel Shahafd.s@daniel.shahaf.name2021-04-13T11:43:27Zurn:sha1:9dc195120cf4e01cd0068f90db12fc9a7eb522b548487 (amended): Failure test for math evaluation oddity2021-04-13T21:22:11ZBart Schaeferschaefer@ipost.com2021-04-13T21:22:11Zurn:sha1:fefd3854b4abea8b46a2ad568762d3a710af77d9
This was inadvertently included with TYPESET_TO_UNSET, so only the amendment is included here.
48525: vcs_info git docs: ahead/behind commits: Run fewer external programs2021-04-13T13:55:48ZTim Leeprogscriptclone@gmail.com2021-04-13T11:58:30Zurn:sha1:3b631babec67c15c893c0d31f8aaaaaa06ca8cfaUpdate descriptive test for POSIX $((inf)) failure2021-04-12T22:43:23ZBart Schaeferschaefer@ipost.com2021-04-12T22:43:23Zurn:sha1:6c9a1f5e80d018e28cf6760cda7ffe18cc5a2df8Completion system assumes typeset does initialize declared variables.2021-04-12T21:45:48ZBart Schaeferschaefer@ipost.com2021-04-12T21:45:48Zurn:sha1:3811abe01c1f2247fc078230eec205ba7e6b08d2Change TYPESET_DOES_NOT_SET to TYPESET_TO_UNSET to avoid double-negative2021-04-12T20:59:06ZBart Schaeferschaefer@ipost.com2021-04-12T20:59:06Zurn:sha1:b3613e4895f7b059558c4ef211189b516dbf903d48439: remove macros that became unnecessary by df48cc82021-04-12T05:42:29ZJun-ichi Takimototakimoto-j@kba.biglobe.ne.jp2021-04-12T05:42:29Zurn:sha1:a90d5ab90191c3681f9216579d2e134314cd8cd748504: use SEEK_ macros in fseek() calls2021-04-11T20:26:36ZOliver Kiddleopk@zsh.org2021-04-11T20:26:36Zurn:sha1:704d10989e0db83bd6460e847a9f89017e29047445396: readhistfile: avoid thousands of lseek(2) syscalls via ftell()2021-04-11T19:38:27ZMichael Stapelbergstapelberg@google.com2020-02-07T07:41:26Zurn:sha1:638815623368683e685a8d706e57634f6fec640148466: correct indentation and remove tabs and trailing spaces2021-04-11T19:32:18ZMarc Chantreuxeiro@phear.org2021-04-10T08:25:02Zurn:sha1:82ba2261abbfa5673fbd5df980c8cbbeb794665348445: pluralize tags in _surfraw2021-04-11T19:05:39ZMarc Chantreuxeiro@phear.org2021-04-09T19:44:54Zurn:sha1:80d5210195593576dbffe10867cab358bbb58148users/26645: update options in gv completion2021-04-11T18:49:30ZMarc Chantreuxeiro@phear.org2021-04-10T09:41:26Zurn:sha1:90352a827858b221f35f4cf0c3f7c1dc7c7bd06947794: exec: run final pipeline command in a subshell in sh mode2021-04-10T22:56:39Zbrian m. carlsonsandals@crustytoothpaste.net2021-01-04T00:23:00Zurn:sha1:f7a417388c73e7cfefb8e93fa8beba193fb1dd1f
zsh typically runs the final command in a pipeline in the main shell
instead of a subshell. However, POSIX specifies that all commands in a
pipeline run in a subshell, but permits zsh's behavior as an extension.
The default /bin/sh implementations on various Linux distros and the
BSDs always use a subshell for all components of a pipeline.
Since zsh may be used as /bin/sh in some cases (such as macOS Catalina),
it makes sense to have the common sh behavior when emulating sh, so do
that by checking for being the final item of a multi-item pipeline and
creating a subshell in that case.
From the comment above execpline(), we know the following:
last1 is a flag that this command is the last command in a shell that
is about to exit, so we can exec instead of forking. It gets passed
all the way down to execcmd() which actually makes the decision. A 0
is always passed if the command is not the last in the pipeline. […]
If last1 is zero but the command is at the end of a pipeline, we pass
2 down to execcmd().
So there are three cases to consider in this code:
• last1 is 0, which means we are not at the end of a pipeline, in which
case we should not change behavior.
• last1 is 1, which means we are effectively running in a subshell,
because nothing that happens due to the exec is going to affect the
actual shell, since it will have been replaced. So there is nothing
to do here.
• last1 is 2, which means our command is at the end of the pipeline, so
in sh mode we should create a subshell by forking.
input is nonzero if the input to this process is a pipe that we've
opened. At the end of a multi-stage pipeline, it will necessarily be
nonzero.
Note that several of the tests may appear bizarre, since most developers
do not place useless variable assignments directly at the end of a
pipeline. However, as the function tests demonstrate, there are cases
where assignments may occur when a shell function is used at the end of
a command. The remaining assignment tests simply test additional cases,
such as the use of local, that would otherwise be untested.
47913: implement CASE_PATHS option to make NO_CASE_GLOB more sensible2021-04-10T21:26:46ZBart Schaeferschaefer@ipost.com2021-04-10T21:26:46Zurn:sha1:408a83048366a22bf7645b71bee7428743793736unposted: README: Document incompatibility caused by workers/439282021-04-10T21:16:26Zdanadana@dana.is2021-04-10T21:16:26Zurn:sha1:1bec15a0105c7884c1a6d1243087ebcc801a5937Add TYPESET_DOES_NOT_SET option (cf. 48469)2021-04-10T21:13:02ZBart Schaeferschaefer@ipost.com2021-04-10T21:10:21Zurn:sha1:e67ccd7f1efae7696dc17f6e3e720cd994e90155unposted (cf. 48469): document oddness of ${emptystr[(i)]}.2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2021-04-10T19:22:43Zurn:sha1:13f85796ac15c871cf760f6415424f4f96c0a460Change DECLAREDNULL to DEFAULTED2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2021-03-27T21:04:05Zurn:sha1:fd89e7cefa4d3806f3f469d5ad4b496d130305a6Fix ${(t)var} output, add comparative test cases2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-27T22:36:35Zurn:sha1:d649bf78dc3096d6ca0c705257a928b1acce3b82Missed files from POSXIBUILTINS commit2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-18T05:08:47Zurn:sha1:2eb9289d1277bf71b1b9dea2addbddd36b61f276Make DECLAREDNULL require POSIXBUILTINS and introduce a new test file.2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-10T05:32:36Zurn:sha1:d4fa4c36896e0d89bf4b32388db08fc1a8523dd4
V10private has been made agnostic to POSIXBUILTINS.
Final repairs for declared state of tied arrays2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-05T00:14:28Zurn:sha1:b1bd99b67f1a2e09dff651f102249c441529d530
Fixups still required in bin_typeset, but assignments to scalar work.
Additional tied-array cleanup when tied scalar had a previous value2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-04T23:09:14Zurn:sha1:fa5f59bf710099dcaa8f22729591c2580c052db9Unset of a tied local scalar previously left it using tiedarr_gsu2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-04T22:46:19Zurn:sha1:7a2d6589ba5e088b959657e35fee867d3d72e55bPartial fix for handling of tied arrays.2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-12-04T06:30:04Zurn:sha1:128035c93c5bc149e9c3babd48c8c145609e29e0
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_DECLARED2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-11-28T19:25:23Zurn:sha1:a8f2a5d0c868e2a2263bbfaf98713f43477ba896Add PM_DECLARED and PM_DECLAREDNULL parameter flags.2021-04-10T21:12:29ZBart Schaeferschaefer@ipost.com2020-11-28T17:23:10Zurn:sha1:36886b5bac75cda19506ba357136200ccf2fe2d4
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 matching2021-04-10T20:54:26Zdanadana@dana.is2021-04-10T20:54:26Zurn:sha1:7269bc1ac46852f8624b99211500276c758eb46e48432 and enable test: fix quotiing of zstyle -L for zstyle -e2021-04-09T20:01:37ZPeter Stephensonp.w.stephenson@ntlworld.com2021-04-09T20:01:37Zurn:sha1:283d2f3c2761ac549a647638bb7d8fd8de3dabb448378: complete compadd options for other completion functions2021-04-09T19:53:41ZOliver Kiddleopk@zsh.org2021-04-09T19:53:41Zurn:sha1:eaff11c748e005bbcd14dbd1850880e4bffee3fa48437: fix pid completion when cursor is in the middle of the line2021-04-09T19:51:31ZOliver Kiddleopk@zsh.org2021-04-09T19:51:31Zurn:sha1:f3caff1536c4a4061d353314eef2628bcd1c840347786: prepare for autoconf 2.702021-04-09T19:49:14ZFelipe Contrerasfelipe.contreras@gmail.com2020-12-31T05:41:31Zurn:sha1:69ffb0bf0aa6c59e3c0529e540f67a26a6cdc54147785: remove deprecated autoconf functions2021-04-09T19:45:11ZFelipe Contrerasfelipe.contreras@gmail.com2020-12-31T05:41:30Zurn:sha1:df48cc8404f3fc2976c9d70c9aeefda171432cf9
STDC_HEADERS and TIME_WITH_SYS_TIME are deprecated.
48416: update _gcore for macOS and GNU2021-04-08T13:24:52ZJun-ichi Takimototakimoto-j@kba.biglobe.ne.jp2021-04-08T13:24:52Zurn:sha1:62e86515e79e57e791bc9f5ed815e8020d1dcf6b48410: FAQ, METAFAQ: Mention zsh-security@.2021-04-08T02:31:58ZDaniel Shahafd.s@daniel.shahaf.name2021-04-05T22:32:41Zurn:sha1:e4a8740c789970178b81162349e4b33104b6f48248379: Make the parameter expansion subscript flags parse error message, "error in flags", identify the location of the parse error.2021-04-08T02:19:39ZDaniel Shahafd.s@daniel.shahaf.name2021-04-03T02:49:54Zurn:sha1:4ba9008ec7842770289645dc6a8829555915086b48321 (tweaked per thread): _perl_modules: Don't assume ${words[1]} to be either "perl" or "perldoc"2021-04-08T02:17:08ZDaniel Shahafd.s@daniel.shahaf.name2021-03-29T15:06:44Zurn:sha1:295fbc0998db7204a9eb68f46c8bedab171ff387
Also, correct an always-true condition guarding the fallback @INC
codepath.
48425: Add an XFail test for a 'zstyle -L' escaping bug (workers/48424).2021-04-07T17:45:57ZDaniel Shahafd.s@daniel.shahaf.name2021-04-07T17:45:53Zurn:sha1:608e49ac193ed81a4f0648d5630cbdbf18d2eb2048391: fix display problem in menu-complete2021-04-06T14:38:52ZJun-ichi Takimototakimoto-j@kba.biglobe.ne.jp2021-04-06T14:36:53Zurn:sha1:9562a1ee7bd0d9cb4793f2441c7709e3da6dcefe
Take account of the trailing file type character even when '-d disp'
is given to compadd.
48389: getkeystring() should not return ptr to local var2021-04-06T14:05:03ZJun-ichi Takimototakimoto-j@kba.biglobe.ne.jp2021-04-06T14:05:03Zurn:sha1:0f62e07c802e3fa58d1199f34fcf9772da70c264
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 awk2021-04-06T12:42:07ZMarc Chantreuxeiro@phear.org2021-03-11T18:08:57Zurn:sha1:ccc7ff90a46d7b1bdcf61bae2dba20d68dca765448414: quote closing bracket to adapt for change in 439282021-04-06T12:20:32ZOliver Kiddleopk@zsh.org2021-04-06T12:20:32Zurn:sha1:2c000ee7bab65f950fd4bec2077332d90ef5417a48413: Fix _expand completion test2021-04-06T11:59:43ZMarlon Richertmarlon.richert@gmail.com2021-04-06T11:29:26Zurn:sha1:aaf619cc22b0c2bf431be9c3d1d13d90585a17d3unposted: add several references to bugs in old list posts2021-04-06T09:00:53ZOliver Kiddleopk@zsh.org2021-04-06T09:00:53Zurn:sha1:e3c4c80f3ece4e28b4b29303f80efec861087ac4unposted: FAQ: Move the 'The mailing lists have moved' notice to a more appropriate place.2021-04-05T22:38:15ZDaniel Shahafd.s@daniel.shahaf.name2021-04-05T22:27:38Zurn:sha1:c0034b3c7b74d7fcb8da1f2e49309f08b117b8ab47784: silence a compiler waring from pattern.c2021-04-04T05:48:01ZFelipe Contrerasfelipe.contreras@gmail.com2021-04-04T05:48:01Zurn:sha1:94b5446838c4c57bd9bab8a410595cf7e81e51fc48218 (+ 48354): various improvements for _gcc2021-04-04T04:39:32ZJacob Gelbmangelbman@gmail.com2021-04-04T04:39:32Zurn:sha1:7a81e6344f233f8f8c3863f0835277582fb7de5847510: drop code that avoided termcap for named colours2021-04-02T22:58:45ZOliver Kiddleopk@zsh.org2021-04-02T20:41:07Zurn:sha1:0721060f3616deac84f82c4a97d75987e276fe0a
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 control2021-04-02T22:58:18ZOliver Kiddleopk@zsh.org2021-04-02T20:29:28Zurn:sha1:714864a87b11b080da92dee7abc29b8bc64107a5unposted: BUGS: Add 39319, a named-file process substitution cleanup bug.2021-04-01T21:17:14ZDaniel Shahafd.s@daniel.shahaf.name2021-04-01T21:17:12Zurn:sha1:ad7948611c96596e585bc93642d997522452509248202 + 48366: Fix handling of NUL bytes in zexpandtabs multibyte version2021-04-01T07:50:52ZMikael Magnussonmikachu@gmail.com2021-03-12T02:50:01Zurn:sha1:ea3351c49610355512672ab478c715ba3cb92aefgithub #74: Drop vcsh completions, maintained upstream2021-03-31T10:16:34ZCaleb Maclennancaleb@alerque.com2021-03-30T21:00:18Zurn:sha1:3afdfef31cf5da224c2e69bb0b942412cbf78b59
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 complist2021-03-30T23:20:36ZMarlon Richertmarlon.richert@gmail.com2021-03-21T15:24:49Zurn:sha1:07a30613f0b0a5b782d30dbeb46df8382f8a4e2a48192: Fix _openstack completion for new style clients2021-03-30T23:16:25ZSyphdiassyphdias+git@gmail.com2021-03-18T22:23:16Zurn:sha1:5d0bb152ef1486e1b38326e37e91e98295bc6946users/26557: add bookmarks support and remove the header from the final list in surfraw completion2021-03-30T23:16:21ZMarc Chantreuxeiro@phear.org2021-02-27T15:27:35Zurn:sha1:7518b20a01bd27a9246d9b040ba5f972ab686e6247561 (the git and cvs parts) (compare 44919 + 44920): vcs_info internals: cvs, git: Set ${vcs_comm[basedir]} like all other backends do.2021-03-29T17:03:40ZAleksandr Mezinmezin.alexander@gmail.com2021-03-29T15:53:44Zurn:sha1:fc82e8193bad79db5de9e40ec99814fe401ad876
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 present (regression from workers/39659 (commit ae3b675ce6e4ac62451ea08169c2b4dc45cf533b))2021-03-29T13:44:44Zdanadana@dana.is2021-03-29T13:42:32Zurn:sha1:2ffd2928336154cf38ee390db835f25c685fe713
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.2021-03-29T13:33:46ZDaniel Shahafd.s@daniel.shahaf.name2021-03-29T13:30:45Zurn:sha1:aebdbfd7baff25f360481992094efa3052adb99eunposted: docs: _arguments: Fix a typo in the example.2021-03-29T13:33:45ZDaniel Shahafd.s@daniel.shahaf.name2021-03-29T09:13:43Zurn:sha1:3d2814072ac2f8ae5640cc479a23dde5fa03ff9c48166: add completion for ctags language options2021-03-28T22:50:42ZJacob Gelbmangelbman@gmail.com2021-03-11T17:08:05Zurn:sha1:ab166725dd5983b00cf21113fb77717c6be324c548210: Introduce new completion for setpriv(1) on Linux2021-03-28T10:47:36ZArseny Maslennikovar@cs.msu.ru2021-03-21T13:01:30Zurn:sha1:e469b8c4e3187e19c96f118ce37579e92f12602f48212: Introduce new completion for Linux task capabilities2021-03-28T10:27:12ZArseny Maslennikovar@cs.msu.ru2021-03-21T13:01:29Zurn:sha1:14709db6d6009c198b1b90f2c7b87f65194527a548231: add missing git --pretty formats and improve descriptions2021-03-28T08:49:34ZŠtěpán Němecstepnem@gmail.com2021-03-23T23:17:07Zurn:sha1:42de9318f1bd05873eb850a830d30af13bc0741548230, 48233 (Jun T): completion of dtrace probes and runtime options2021-03-28T08:38:13ZOliver Kiddleopk@zsh.org2021-03-28T08:38:13Zurn:sha1:d7c8d6826deec089006d57ecdf6dc3f5c8a38d6448216: Fix broken Y01 test from workers/481802021-03-28T05:22:59Zdanadana@dana.is2021-03-28T05:22:59Zurn:sha1:d3906d7a2fb64ae5c33576cd98872262fb68638348131/0004: FAQ: 3.31: Rearrange2021-03-26T23:20:20ZDaniel Shahafd.s@daniel.shahaf.name2021-03-03T00:34:11Zurn:sha1:2c062e8e69acf887a808f53cdd3cea11078a820548131/0003: FAQ: 3.31: Move two paragraphs unchanged, reordering them2021-03-26T23:20:20ZDaniel Shahafd.s@daniel.shahaf.name2021-03-03T00:18:24Zurn:sha1:7c201b1b3e180cb4bcb4e7fbc5823a4dd4842aac
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.
48131/0002: FAQ: 3.31: Tweak summary paragraph2021-03-26T23:20:19ZDaniel Shahafd.s@daniel.shahaf.name2021-03-03T00:18:18Zurn:sha1:2ad942b7582de28cb0acf34255e5c3d0e5173d8448131/0001: FAQ: 3.31: Add a one-sentence summary2021-03-26T23:20:19ZDaniel Shahafd.s@daniel.shahaf.name2021-03-03T00:17:53Zurn:sha1:a5a093d5fec5b03c0fee34650d4f31469e18ca1dunposted: Improve documentation and add regression test for workers/477452021-03-23T05:26:21Zdanadana@dana.is2021-03-23T05:26:21Zurn:sha1:78cf45587100965553a879fc8b026294c79bd75647745: Fix [:IDENT:] vs posixidentifiers2021-03-23T05:15:09ZStephane Chazelasstephane@chazelas.org2020-12-17T14:49:50Zurn:sha1:d96c8981011294cfef62cd1f8d76b2a982957ca4
wcsitype(c, IIDENT) should return false for non-ASCII characters
when the POSIX_IDENTIFIERS option is on, not the other way round.
48180: Start menu selection with select=long-list in menu style2021-03-17T17:50:57ZMarlon Richertmarlon.richert@gmail.com2021-03-17T17:50:57Zurn:sha1:f4a248f9d38dc02d65610395f4c7f9a95a5d661248147/0002: zmathfunc: Fix bug where the exit code would be non-zero if the expression evaluted to zero.2021-03-07T21:58:13ZDaniel Shahafd.s@daniel.shahaf.name2021-03-07T17:07:06Zurn:sha1:f87b73e677739970c61eab55d4a3276beba1bd4348147/0001: tests: Add a unit test for zmathfunc and a regression test for workers/48146 affecting it.2021-03-07T21:58:12ZDaniel Shahafd.s@daniel.shahaf.name2021-03-07T16:58:03Zurn:sha1:6a2a8acf09bc39795f18cc60e90a0d4427d36edd48105: Update ctags completion with format fix2021-02-24T09:24:37ZJacob Gelbmangelbman@gmail.com2021-02-24T07:20:24Zurn:sha1:5ede2c55f144593c16498c3131a76e188114a9c648096: New ctags completion2021-02-23T10:10:34ZJacob Gelbmangelbman@gmail.com2021-02-23T03:11:57Zurn:sha1:055ce784017ebd42fbcef09165c52310fc7f6efd48094: apply cleanup commands of the current theme on any theme change2021-02-23T04:29:55ZArseny Maslennikovar@cs.msu.ru2021-02-23T04:29:55Zurn:sha1:8b67c36d929c2661a1f4e28ff137c7ddd53ec33d
* Rename zstyle `cleanup' on the context `:prompt-theme' to `restore'
everywhere but in prompt_cleanup(). It is only used as a restore
mechanism now.
* Ensure prompt_cleanup() continues to store its command list in the
`cleanup' style.
* Clean up before theme switch at the end of set_prompt().
* Prepend every use of prompt_*_setup (which might modify the shell
state in ways that require cleanup) with a cleanup run.
* Adjust `prompt restore' to do both parts of the newly split restore
mechanism, cleanup first.
47867: Fix RPROMPT typo in prompinit2021-02-20T00:39:22ZArseny Maslennikovar@cs.msu.ru2021-02-20T00:38:09Zurn:sha1:5c60ec46ec087e7e58c8fc00c6821060e8caecb8users/26509: fix for r -L2021-02-18T21:37:08ZPeter Stephensonp.w.stephenson@ntlworld.com2021-02-18T21:37:08Zurn:sha1:6bef719302d6db33c63fb6f2636986dff1941ac2
fc with the -L option should ignore remote entires, rather than
reading them and treating them as an error.
48073: Add fc -s as POSIX way of rerunning command without starting editor2021-02-17T10:21:08ZMartijn Dekkermartijn@inlv.org2021-02-16T18:34:41Zurn:sha1:9c0533931c51b7d512d3e95850404f5aac2dbce1Allow more scripts without #!2021-02-16T09:16:20ZJustine Tunneyjtunney@gmail.com2021-01-26T05:34:50Zurn:sha1:326d9c203b3980c0f841bc62b06e37134c6e51ea
This change modifies the zsh binary safety check surrounding execve() so
it can run shell scripts having concatenated binary content. We're using
the same safety check as FreeBSD /bin/sh [1]. POSIX was recently revised
to require this behavior:
"The input file may be of any type, but the initial portion of the
file intended to be parsed according to the shell grammar (XREF to
XSH 2.10.2 Shell Grammar Rules) shall consist of characters and
shall not contain the NUL character. The shell shall not enforce
any line length limits."
"Earlier versions of this standard required that input files to the
shell be text files except that line lengths were unlimited.
However, that was overly restrictive in relation to the fact that
shells can parse a script without a trailing newline, and in
relation to a common practice of concatenating a shell script
ending with an 'exit' or 'exec $command' with a binary data payload
to form a single-file self-extracting archive." [2] [3]
One example use case of such scripts, is the Cosmopolitan C Library [4]
which configuse the GNU Linker to output a polyglot shell+binary format
that runs on Linux / Mac / Windows / FreeBSD / OpenBSD.
[1] https://github.com/freebsd/freebsd-src/commit/9a1cd363318b7e9e70ef6af27d1675b371c16b1a
[2] http://austingroupbugs.net/view.php?id=1250
[3] http://austingroupbugs.net/view.php?id=1226#c4394
[4] https://justine.lol/cosmopolitan/index.html
47830: Fix some documentation typos2021-02-16T00:59:14ZLawrence Velázquezvq@larryv.me2021-01-14T06:04:54Zurn:sha1:83cc7c6bf08762c3fdeb76a44e4086734ff1db13unposted (Daniel): add exclusion list missed in recent OpenBSD update to locale completion2021-02-13T00:15:10ZOliver Kiddleopk@zsh.org2021-02-13T00:15:10Zurn:sha1:d909dc7323e53dfa63e12d11fa1a7bfc7e3ce81dgithub #68: support section suffix completion for man pages2021-02-13T00:01:40Ztaiyutaiyu.len@gmail.com2021-02-07T13:15:03Zurn:sha1:3714ee0b5868a30d7556acab337889849a3c8226
Support prepend and suffix values for insert-sections
Add values for insert-sections for zstyle completion
47905: Add leading '-' to zparseopts option parsing errors2021-02-12T23:54:59ZJoshua Kruselljs.shirin@gmail.com2021-02-03T15:46:59Zurn:sha1:3d6e5b6231f0d80873c6f83924a48df223121e7247997: Disable XTRACE around user-defined completion widgets.2021-02-12T03:13:47ZBart Schaeferschaefer@ipost.com2021-02-12T03:13:47Zurn:sha1:2cf6032a301d994c578e5e1942c4815e8565164747944: update completions for NetBSD 92021-02-07T23:40:10ZOliver Kiddleopk@zsh.org2021-02-07T23:40:10Zurn:sha1:073092f89dcf9fc1e59f9e3c5048f8c4829eae0747943: update completions for DragonflyBSD 5.8.32021-02-07T23:06:57ZOliver Kiddleopk@zsh.org2021-02-07T23:06:57Zurn:sha1:25d69da85c707bfe08c2bad1d0b288baf8184b72