Around about 19/04/06 20:03, Bram Moolenaar typed ...
Main issue is: Do you open another buffer or window?
I don't believe so. Apart from some tricky indirection (the srcctl plugin
has a generic set up, then calls the relevant real script functions depending
upon the SCM S/W being used, SourceSafe in my case), the sequence is pretty
much as you describe below.
The process does involve at least 2, maybe three system() calls [one 'cat'
of the config. file, one to deduce the status of the file in an initial
check-out attempt, and a potential third if this fails or requires
interaction: the script parses the output and if a question is asked (say,
"are you sure?"), converts this into a vim dialogue [is *that* the issue?
interactivity during the autocmd?].
I then have a bit that forcibly reloads the file (otherwise the edit that
triggered the autocmd happens in the to-be-forgotten read-only version of the
file), then finally the 'syntax on' which for some reason is required to make
the freshly loaded file have syntax highlighting.
I guess the basic sequence is:
- you do "z=" and select a suggestion, this is to be inserted
- your file is RO, thus the FileChangedRO autocmd is triggered
- your FileChangedRO autocmd uses sourcesafe to get the file
Hmm, does this then trigger the timestamp check and
trigger a FileChangedShell autocmd?
- your FileChangedRO autocmd reloads the file
As above; I don't know about the FileChangedShell autocmd; I can set a
dummy one up to see if it's happening if it'll help.
Efence should make your application crash as soon as it accesses memory
that it shouldn't access.
Well, as I said, it made it /not/ crash instead :-/
--
[EMAIL PROTECTED] ~]# rm -f .signature
[EMAIL PROTECTED] ~]# ls -l .signature
ls: .signature: No such file or directory
[EMAIL PROTECTED] ~]# exit
