summaryrefslogtreecommitdiff
path: root/Etc
AgeCommit message (Collapse)AuthorFilesLines
2022-04-02unposted: creating-a-release: Normalise white space, clarify some stepsdana1-13/+21
(The need for these changes was discovered during the release of 5.8.1. Daniel suggested one. They were hinted at in security/107)
2022-03-3149907: Mention _numbers in completion guideMatthew Martin1-0/+2
2022-02-1549756 + 49758(Daniel): replace LPAR() in FAQ.yo by SUBST(_LPAR_)Jun-ichi Takimoto1-7/+7
In FAQ.yo, macros inside mytt() and tt() are not expanded. Also includes an update for zyodl.vim by Daniel.
2022-02-12unposted: Release 5.8.1dana1-1/+1
(cherry picked from commit 1a490c7050cfacd5daf8376d5a1f0e8cb14ccda5)
2022-02-12security/89: Add patch which can optionally be used to work around ↵Marc Cornellà1-0/+98
CVE-2021-45444 in VCS_Info (cherry picked from commit fdb8b0ce6244ff26bf55e0fd825310a58d0d3156)
2021-12-1449518: fix exclusions for mixed - and + stacked optionsOliver Kiddle1-2/+0
2021-11-12github #82: Fix typosDimitris Apostolou2-3/+3
2021-10-2449520: document $_args_chache_cmdJun-ichi Takimoto1-0/+10
2021-06-2248096: Update Sourceforge links to https://zsh.sourceforge.io/Peter Stephenson2-11/+11
2021-05-1648860: remove mention of bugs that have been fixedBart Schaefer1-21/+0
2021-05-03unposted: FAQ: Move section 3.31 to 2.8dana1-63/+63
See 48613
2021-04-18unposted: remove an already fixed bug from BUGSJun-ichi Takimoto1-2/+0
This was fixed by commit b6ba74c
2021-04-16unposted: update on bug listOliver Kiddle1-3/+2
2021-04-0848410: FAQ, METAFAQ: Mention zsh-security@.Daniel Shahaf1-0/+5
2021-04-06unposted: add several references to bugs in old list postsOliver Kiddle1-1/+7
2021-04-05unposted: FAQ: Move the 'The mailing lists have moved' notice to a more ↵Daniel Shahaf1-3/+3
appropriate place.
2021-04-01unposted: BUGS: Add 39319, a named-file process substitution cleanup bug.Daniel Shahaf1-0/+2
2021-03-2648131/0004: FAQ: 3.31: RearrangeDaniel Shahaf1-14/+19
2021-03-2648131/0003: FAQ: 3.31: Move two paragraphs unchanged, reordering themDaniel Shahaf1-14/+17
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.
2021-03-2648131/0002: FAQ: 3.31: Tweak summary paragraphDaniel Shahaf1-2/+3
2021-03-2648131/0001: FAQ: 3.31: Add a one-sentence summaryDaniel Shahaf1-0/+3
2021-02-0447889: Update csh aliasing equivalencesBart Schaefer1-5/+5
2021-01-26unposted: Etc/FAQ.yo: Fix a typo in the front matter.Daniel Shahaf1-1/+1
2020-12-0447716: Etc/BUGS: Add Alekxandr's vcs_info patch.Daniel Shahaf1-0/+2
2020-12-01users/26150: note failure of multios with execBart Schaefer1-0/+6
2020-08-2147328: remove references to old zsh.org mail addressesOliver Kiddle1-4/+4
2020-08-1047308: zsh-development-guide: Document the new X-Seq autoreply bot.Daniel Shahaf1-0/+8
2020-08-08unposted: Update documentation for the move to new hosting.Daniel Shahaf1-10/+7
2020-07-1446244 (cont.): Flesh out the TODO from the previous commit.Daniel Shahaf1-2/+19
2020-07-1446244: Start to introduce a release managers keyring.Daniel Shahaf1-0/+6
2020-07-0846201: add guidelines for caching and use of imperative mood in descriptionsOliver Kiddle1-4/+21
2020-06-26unposted: docs: Fix some markup and typos.Daniel Shahaf1-1/+1
2020-06-09unposted: Add 45400 (vared in subshells) plus remarks on users/24904.Bart Schaefer1-0/+9
2020-06-0745932: FAQ (3.1): Update ksh compatibility answer for reserved word typeset.Daniel Shahaf1-9/+19
2020-06-0745933: FAQ: Add "Why does my bash script report an error when I run it under ↵Daniel Shahaf1-3/+54
zsh?".
2020-06-0745791 (tweaked): FAQ: Explain how to binary search one's dotfilesDaniel Shahaf1-3/+102
2020-06-07unposted: FAQ: Update section number in links to the "The future of zsh" ↵Daniel Shahaf1-8/+8
section.
2020-06-06unposted: Add users/24904 to Etc/BUGS (a process substitution / forking issue).Daniel Shahaf1-0/+7
2020-05-2145884 (Oliver's, edited by me): Add a few entries.Daniel Shahaf1-0/+25
2020-04-0545656: Document the -o emacs segfault bug.Daniel Shahaf1-0/+3
2020-03-2545583/0008: Extend tests to prove that what remains of xsymlinks() handles ↵Daniel Shahaf1-3/+0
symlink loops gracefully.
2020-03-2545583/0004: Fix segfault on resolving symlink loopsDaniel Shahaf1-1/+2
2020-02-0245372: Record a symlink loop bug involving :PDaniel Shahaf1-0/+2
2020-01-0945269: Fix misspellings in completions and elsewhere.Jens Schleusener1-1/+1
2020-01-0145169/0002 (tweaked for trailing newlines): Add an expected-to-fail test for ↵Daniel Shahaf1-12/+2
workers/44007.
2019-12-2245111: zshmisc(1): Clarify the documentation of 'return' and 'exit' in ↵Daniel Shahaf1-3/+0
conjunction with try/always Having reviewed 20076, 20084, 21734, and 21735, my understanding is that the original intention was: - A 'return' in a function does run always-list - An 'exit' outside a function does not run always-list - A 'return' outside a function is treated as an 'exit' All of which are the case today. The remaining case, of 'exit' used inside a function, was not specified by the referenced -workers@ posts; does, as implemented, run the always-list; and furthermore, based in 21734 it's fair to assume that the original documentation was assuming that 'exit' would be used outside of any function, just like it assumed 'return' would be used inside a function. Therefore, have the documentation specify only the behaviour of 'exit' outside any function, and leave the behaviour of 'exit' inside a function unspecified. Anyone who relied on the documentation of 'exit' as documented until this commit would have run into the documentation/implementation discrepancy described in 45075.
2019-12-2145101: Adjust white spacedana1-4/+8
2019-12-2145101: Document new dev/test versioning scheme, clarify other release stepsdana1-9/+30
Also clarified the purpose of dev/test releases as suggested in workers/45104. Note that the old versioning scheme remains in effect until after 5.8 final has been released.
2019-12-21unposted: Etc/BUGS: Add two bugs discussed on -workers@ this weekDaniel Shahaf1-0/+16
2019-12-14unposted: Test release: 5.7.1-test-1dana1-1/+1