Hi all,
I have a couple of branches that help with some of the problems with modern emacs: bzr+ssh://[email protected]/~markd-kermodei/vm/vm-emacs-28/ bzr+ssh://bazaar.launchpad.net/~markd-kermodei/vm/texinfo-utf8-fix/ However, I think whatever is left of the VM community needs to figure out if we want to breath new life into VM or let it join the crypt of yesterdays great software. Personally, I love VM, but the compatibility issues, as well as not scaling to modern email volume, is increasingly problematic. While I would be happy to be part of a community to resurrect and modernize VM, I just don't have bandwidth to be developing my own email client. If anyone is interested, lets start a conversation. VM is an amazing pieces of software. We might be able to attract others if we can seed a modern approach to collaborative development. Cheers Mark Stefan Monnier via General discussion of VM mail reader <[email protected]> writes: > > A naive attempt to clone from https://github.com/emacsorphanage/vm/ > > and run failed. I've been running a version from the bzr repo under > > 29.0.50. > > [ Hmm... 29.3 or the obsolete 29.0.50? ] > > > A few questions: > > - Am I starting from the right repo or is there a more recent version? > > - Are others running successfully in the case I'm trying? > > - Does any of the experienced maintainers have a sense of how hard this will > > be to fix? I'm willing to try it but would like an estimate of difficulty > > and time. > > Check the latest thread in this mailing-list, under the subject > > vm, emacs 28.2 (debian), urls in minibuffer > > where I sent a "cleanup" patch to help get the code closer to modern > ELisp. John Stoffel gave up on trying to make it work, but I don't > think it's should be very hard. I don't use VM myself, but I'm quite > experienced in fixing those kinds of things and would be glad to provide > guidance. Maybe you can team with John? > > > Stefan > >
