12/2 So why did emarkp have the motd locked for like an hour?
\_ Because motdedit sucks.
\_ I closed the motd in my vim session, but did not quit vim. I
promise not to use motdedit again. Why the session didn't expire
on its own is beyond me. -emarkp
[Oh, and by the way, the reason I left the vim session up was to
keep a copy of the edit I made in the buffer in case it was
overwritten. Ironically, this bracketed statement was overwritten
just after I posted it.]
\_ Yeah, motdedit DOES suck. Wow. No more motdedit.
\_ You did not quit vim; you did send it SIGSTOP. -jon
[grammar god]
\_ Apparently you don't understand how vim uses buffers. I
closed the buffer that the motd was in. I left a different
buffer open which contained a copy of the text I'd added to
the motd. Then I ctrl-Z'ed it so I could restore the text
if it was overwritten. I didn't state anywhere that I
"quit vim". This is an incompatibility between my chosen
method of preserving my edits to the motd and motdedit. The
way I will fix the incompatibility is by ceasing to use
motdedit. Thanks for bringing it to my attention, but in
the future, feel free to nwrite me and ask me about it
instead of simply invoking root to kill the process. -emarkp
\_ grow up.
\_ Hey, I'm the one signing my name--not you. And what
in the above comment suggests that I need to "grow
up"? -emarkp
\_ you apparently don't understand child processes.
\_ Yes, I do. However, I have not investigated the inner
workings of motdedit, nor was I thinking carefully
about it when I was editing the motd. -emarkp
\_ SIGTSTP, as tom has corrected -jon
\_ Why do you ask the question about me by name but fail to sign your
own? -emarkp
\_ because he's a jackass. --emarkp #1 fan |
http://csua.com/feed/