the following drives me nuts and it seems to be a VEDIT-bug:
(I have compressed it to a few lines, the real code is more complex, but fully working as such (alt-m-x)!)
- try txt-pseudo-open.vdm by load/exec user macro (alt-m-x) in any file: this works (appends something to 1st line, goes to line 10; a file in another buffer and window is opened and perfectly closed, including buffer and window)
- now try the same vediting any .txt after first enabling event macros for .txt-extension (sample txt.cft included):
everything as expected except that a 2nd "buffer"/"window" rests open!!! (You can close it by pressing alt-f-c, by a command window and buf_quit(ok) etc)
- and not only rests this 2nd useless "buffer" open, there are 2 different behaviours:
- a) launch VEDIT, open .txt -> cursor remains in this 2nd buffer, even if the last command in the txt-pseudo-open.vdm is buf_switch("main")!
- b) launch .txt by double-clicking on it in Explorer (I use PowerDesk) -> 2nd buffer still open, but cursor correctly in 1st buffer!
- what's going on here? Any solutions? I launch VEDIT programmatically opening my source code and I don't want to alt-f-c these useless additional buffers hundreds of times daily...