Hi, Can someone with the admin access to https://www.vim.org/ update the "News" section with a link to the message from Bram's family?
Regards, Yegappan On Mon, Aug 7, 2023 at 7:13 AM Antonio Giovanni Colombo <azc...@gmail.com> wrote: > > Hi everybody, > > I too will miss Bram a lot. > > I am a minor contributor to Vim, for the translation of messages. I have been > in touch with Bram since the Nineties, and even visited him in Venlo. > > I used to send new versions of language related files, like e.g. > "src/po/it.po" directly to Bram, who included them in the Vim distribution > without the need of patches. Pending further decisions, I will send future > modifications of such files to Christian Brabandt. This is not only about me, > but about a group of other translators. Bram sometimes sent mail to this > group, just before a new version of Vim was in sight. > > VALE, Bram! We will try to keep up the good work. > > Antonio > > Il giorno dom 6 ago 2023 alle ore 21:43 Dominique Pellé > <dominique.pe...@gmail.com> ha scritto: >> >> Zoltan Arpadffy wrote: >> >> > This is truly shocking - I do not have a word. >> > I just sent Bram a mail about a week ago - with no answer - when he >> > replied mails almost immediately in the past 20+ years. >> > >> > I am so sad. >> > My deepest condolences to the family. >> > >> > I have been in contact with Bram since 1998 - when I started to work >> > on the OpenVMS port and I am still maintaining the OpenVMS related >> > code and distributing the VMS executable packages on >> > http://polarhome.com/vim/ >> > >> > I am working on the the patch for Vim 9.0 and for the new x86_64 VMS >> > port (beside VAX, AXP and IA64) >> > I have had sent him my patches directly that he merged into the >> > eleases. >> > >> > Ken, Chris could you please instruct me, how can I continue to >> > contribute > to the Vim development? >> >> We're all shocked and feel empty with the loss of Bram. >> >> Thanks Zoltan for your contributions to Vim since 1998. That's >> amazing dedication. For now, I suggest to either send patch >> attachments to this mailing list, or better if you can, to submit >> git pull requests. A PR is preferable as CI will run and it makes >> it easier for people to review contributions. Code reviews were >> always important, but they have become even more important >> now the gate-keeper Bram is no longer here. >> >> I assume it will take some time before we figure out how to >> merge changes to the master branch. So PR may stay >> open for a while. Let's be patient. >> >> I will also try to contribute, as much as I can. I fear that some >> of the Vim internals are hard to maintain without Bram. >> I hope the community will step up to the challenge and honor >> Bram's project by continuing its development. >> >> Even if I have a personal preference for Vim rather than Neovim >> for various reasons (no need to go into details as to why here), >> it's clear that Neovim showed that the community was able to >> make impressive deep changes to Vim's code. Neovim still >> depended on Vim and Bram's work to some extent (regularly >> merging Vim patches). And Neovim was standing on the >> shoulders of giants by reusing Vim's code. So I hope that >> some of the Neovim developers can also help continuing >> the Vim development adventure. >> >> Regards >> Dominique >> -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7kKtFnLCcUcj90T-pr%2B1%3DHsr5E8mgGBCjNWdY3%2BmxvAOQ%40mail.gmail.com.