Talk:Using your own editor
Diccon 12:16, 27 April 2009 (UTC) - Few suggestions Tom.
- Since this is not specific to VIM, can you generalise the var names and the command itself. I know it ultimately calls vim as it is, but simply exchanging the command var means it can be anything as I understand your code (Nano, vi, hell Kate if you have X windows). Called it EDITOR in mine, which is too long a name IMO, and of course EDIT and ED exist :) Any other good names would be good (suggestions?).
- It currently screams if you do not have the syntax highlighting qmbasic.vim file there. Either note that the file is not optional or reduce the screaming warning volume. This could break the above mentioned generic nature too, perhaps parametrise it? I've not looked at that bit of code.
- Can we have a fail-over question asked if you don't provide details, in a QM Style. Ie no file name, then ask Filename?.. etc. Partly to be consistent, but also because it smooths the CLI flow if you miss a step. ? query function at this point is too much to ask IMO at this time.
Given the above i think it's idea to go into workdevbranch1.
Diccon 12:43, 27 April 2009 (UTC) Also i have some ideas about Dynamic files. Simply Write a BASIC precursor that copies the indervidual record being requested to a TEMP Directory file. When the editor finishes copy back the temp file over the record. If nothing has been altered and the external prog just exited, then you will be copying back an identicle record. If it was altered then the edits are copied in. No clever detection of alterations are needed. This can even implement record locking if you lock before the shell execute and the BASIC prog returns and releases after you exit.