BK-EDIT(1)

💅 BK-EDIT(1) 💅

okay so bestie, welcome to the bk edit(none) page — it’s from the BitKeeper User’s Manual, and it is literally about checking out a file for editing. no cap. 💖

✨ NAME ✨

bk edit − check out a file for editing. 🎀

🦋 SYNOPSIS 🦋

bk edit [−q] [−rrev] [file ... | −]

🌸 DESCRIPTION 🌸

If a file is not locked for writing — i.e., it is not visible in a directory listing or it is read-only — then use bk edit to check out the file and lock it, making it available for writing. slay. 💅

bk edit with no options will check out all files in a directory. periodt. ✨

💖 OPTIONS 💖

• −q — run quietly. shhh 🤫
• −rrev — Edit the file, rolling it back to the contents specified by rev. (Or key or changeset revision. See bk help terms under “rev argument”.) BitKeeper will check out the tip revision combined with a set of include and exclude deltas needed to produce the requested revision.

🧚 NOTES 🧚

okay so it may seem like this step could be done with a simple

$ chmod +w foo.c

but that is not correct. bestie, the reason is keyword expansion. Keywords are expanded only in read-only files; they are unexpanded in locked files. For example, if a file contains %M% %I%, when it is not locked that will look like foo.c 1.2. If the file is modified after the chmod then the keywords will forever more be foo.c 1.2, which is not likely to be the desired result. 😭

One could argue that BitKeeper should try and catch this case (and it does — bk check will frequently fix it), but it is impossible to do so correctly in all cases. lowkey tragic, but fr fr. 💀

👑 SEE ALSO 👑

• bk‐terms

🌈 CATEGORY 🌈

• File
• Common

---

source/version/date footer vibes: BitKeeper Inc · 1E1 · bk edit(none) — mwah 💋🫶✨