From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: compdump should write .zcompdump exclusively.
Date: 27 Jul 1999 11:13:54 +0900 [thread overview]
Message-ID: <rsqemhu6dr1.fsf@crane.jaist.ac.jp> (raw)
I found that two zsh started at the same time may break .zcompdump.
--- Completion/Core/compdump- Tue Jul 27 10:57:22 1999
+++ Completion/Core/compdump Tue Jul 27 11:05:00 1999
@@ -17,7 +17,7 @@
typeset _d_file _d_f _d_bks _d_line _d_als
-_d_file=${compconfig[dumpfile]-${0:h}/compinit.dump}
+_d_file=${compconfig[dumpfile]-${0:h}/compinit.dump}.$HOST.$$
typeset -U _d_files
_d_files=( ${^~fpath}/_(|*[^~])(N:t) )
@@ -87,6 +87,8 @@
done >> $_d_file
print >> $_d_file
+
+mv $_d_file ${_d_file%.$HOST.$$}
unfunction compdump
autoload -U compdump
--
Tanaka Akira
reply other threads:[~1999-07-27 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=rsqemhu6dr1.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--cc=zsh-workers@sunsite.auc.dk \
/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).