At present, the only way to add a .leo file to the Open Recent menu is to open the file *without* using leoInteg. Alas, the running leoInteg has no access to the Open Recent menu. I have to give the full path to ekr-leoInteg every. single. time.
While researching this topic, I ran across vs code issue 64223 <https://github.com/Microsoft/vscode/issues/64223>: Extension API access to recent files/projects. This topic has been closed: "we are closing issues that are not going to be addressed in the foreseeable future." I think we should push back. I am wondering whether the vs code devs would be interested in a PR. I think this is a significant hole in the api that should be plugged. Without access to recent files, leoInteg looks like it would have to create its own "Recent Leo Files" menu item, along with the necessary machinery to make it work. Possible a setting would work, to be updated when opening a .leo file. Félix, these are my first thoughts. What do you think? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/ca6f6fdc-5a54-473d-9cfa-16e6a7d724edo%40googlegroups.com.
