Timeline for In nvi, how do I undo "already locked, session is read-only?"
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2022 at 18:03 | answer | added | Jason | timeline score: 0 | |
| Mar 3, 2022 at 19:15 | vote | accept | turtleyacht | ||
| Mar 1, 2022 at 15:26 | comment | added | turtleyacht |
Separate answers added. I can mark the tmux kill-session -a post as the Answer in a bit, unless otherwise suggested. Thank-you again @D.BenKnoble.
|
|
| Mar 1, 2022 at 15:19 | answer | added | turtleyacht | timeline score: 0 | |
| Mar 1, 2022 at 15:16 | history | edited | turtleyacht | CC BY-SA 4.0 |
deleted 142 characters in body
|
| Mar 1, 2022 at 15:15 | answer | added | turtleyacht | timeline score: 0 | |
| Mar 1, 2022 at 15:13 | history | edited | turtleyacht | CC BY-SA 4.0 |
deleted 138 characters in body
|
| Mar 1, 2022 at 15:12 | answer | added | turtleyacht | timeline score: 0 | |
| Mar 1, 2022 at 15:10 | answer | added | turtleyacht | timeline score: 0 | |
| Mar 1, 2022 at 15:06 | comment | added | D. Ben Knoble♦ | Separate answers is probably the best option, but you can also agglomerate them into a “Workarounds” answer if you want. You can use the edit button to update posts. | |
| Mar 1, 2022 at 15:05 | comment | added | turtleyacht |
@D.BenKnoble Thank-you for that. Running lsof <file> does show one entry, and it is for nvi. I have no visible editing sessions for the file; maybe this is running in the tmux session from before I quit Terminal? I can check for that. In the meantime, should I make the workarounds above separate Answers?
|
|
| Mar 1, 2022 at 15:01 | history | edited | turtleyacht | CC BY-SA 4.0 |
added 9 characters in body
|
| Mar 1, 2022 at 15:00 | comment | added | D. Ben Knoble♦ |
Note that answers really belong below, in the answer section, and not in the Question. Another thing to try: find out if any processes are still using the file (e.g., via lsof)
|
|
| Mar 1, 2022 at 14:58 | history | edited | turtleyacht | CC BY-SA 4.0 |
added 113 characters in body
|
| Mar 1, 2022 at 14:58 | comment | added | turtleyacht |
@D.BenKnoble Thank-you. After adding set nolock to the nvi startup file ~/.nexrc, the read-only issue is resolved. However, a nice "feature" of the read-only warning is knowing the file is opened already (in another tmux panel or new Terminal tab). The question originally did not mention this, so I'll update to provide more context.
|
|
| Mar 1, 2022 at 14:47 | history | edited | turtleyacht | CC BY-SA 4.0 |
added 113 characters in body
|
| Mar 1, 2022 at 14:35 | comment | added | D. Ben Knoble♦ |
perhaps try :set nolock?
|
|
| Mar 1, 2022 at 14:32 | history | edited | turtleyacht | CC BY-SA 4.0 |
added 33 characters in body
|
| Mar 1, 2022 at 13:53 | history | edited | turtleyacht | CC BY-SA 4.0 |
added 63 characters in body
|
| Mar 1, 2022 at 11:45 | history | edited | turtleyacht | CC BY-SA 4.0 |
added 121 characters in body
|
| S Mar 1, 2022 at 11:37 | review | First questions | |||
| Mar 1, 2022 at 14:35 | |||||
| S Mar 1, 2022 at 11:37 | history | asked | turtleyacht | CC BY-SA 4.0 |