On 2023-08-09 07:18, Yegappan Lakshmanan wrote:
Hi,
On Tue, Aug 8, 2023 at 12:57 PM Christian Brabandt
wrote:
On Di, 08 Aug 2023, Christian Brabandt wrote:
> patch 9.0.1679: Cleanup Tests from leftover files
Sorry, trying to get the patch mails working.
While this seems to fix the recent
Hi,
On Tue, Aug 8, 2023 at 12:57 PM Christian Brabandt wrote:
>
>
> On Di, 08 Aug 2023, Christian Brabandt wrote:
>
> > patch 9.0.1679: Cleanup Tests from leftover files
>
> Sorry, trying to get the patch mails working.
>
> While this seems to fix the recent CI test failures about the file
> Xcry
On Di, 08 Aug 2023, Christian Brabandt wrote:
> patch 9.0.1679: Cleanup Tests from leftover files
Sorry, trying to get the patch mails working.
While this seems to fix the recent CI test failures about the file
Xcrypt_sodium_v2.txt now I am seeing sodium_mlock() failures. I don't
know yet wh
patch 9.0.1679: Cleanup Tests from leftover files
Commit:
https://github.com/vim/vim/commit/84bc00e9b52b1174888f2f696f8b628a83c49988
Author: Christian Brabandt
Date: Thu Jul 13 11:45:54 2023 +0200
patch 9.0.1679: Cleanup Tests from leftover files
Problem:Tests may leave lefto
--
--
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 unsubs
On Wed, 9 Aug 2023 at 04:52, Christian Brabandt wrote:
>
> On Mi, 09 Aug 2023, Doug Kearns wrote:
>
> > Runtime file updates often include test updates (e.g., filetype
> detection tests) and changes to runtime infrastructure (e.g.,
> runtime/ftplugin.vim) are also arguably worth a version bump.
>
On Di, 08 Aug 2023, Dragan Simic wrote:
> On 2023-08-08 20:15, Christian Brabandt wrote:
> > On Di, 08 Aug 2023, 'Dragan Simic' via vim_dev wrote:
> >
> > > diff --git a/runtime/doc/usr_05.txt b/runtime/doc/usr_05.txt
> > > index bc68e61b8..acc0f0c6b 100644
> > > --- a/runtime/doc/usr_05.txt
>
On Mi, 09 Aug 2023, Doug Kearns wrote:
> Runtime file updates often include test updates (e.g., filetype detection
> tests) and changes to runtime infrastructure (e.g., runtime/ftplugin.vim) are
> also arguably worth a version bump.
>
> Bram's distinction here actually makes a lot of sense bu
May you rest peacefully, Bram. You started and continued doing a
monumental thing for the humanity.
No matter how sad this moment is, let it remind us that the good things
we do in our lives are important. Human lives are extremely fragile, so
let's do our best while we all are able to.
--
On Wed, 9 Aug 2023 at 03:56, Christian Brabandt wrote:
>
> On Di, 08 Aug 2023, Yegappan Lakshmanan wrote:
>
> > I am not suggesting a separate minor release for each runtime file
> update here.
> > Otherwise, we will have too many minor releases. Can we make a minor
> release
> > only for PRs th
On 2023-08-08 20:15, Christian Brabandt wrote:
On Di, 08 Aug 2023, 'Dragan Simic' via vim_dev wrote:
diff --git a/runtime/doc/usr_05.txt b/runtime/doc/usr_05.txt
index bc68e61b8..acc0f0c6b 100644
--- a/runtime/doc/usr_05.txt
+++ b/runtime/doc/usr_05.txt
@@ -308,10 +308,14 @@ This switches on th
On Di, 08 Aug 2023, 'Dragan Simic' via vim_dev wrote:
> diff --git a/runtime/doc/usr_05.txt b/runtime/doc/usr_05.txt
> index bc68e61b8..acc0f0c6b 100644
> --- a/runtime/doc/usr_05.txt
> +++ b/runtime/doc/usr_05.txt
> @@ -308,10 +308,14 @@ This switches on three very clever mechanisms:
>
>
>
On Di, 08 Aug 2023, 'Dragan Simic' via vim_dev wrote:
>
> This version saves and restores the view position while saving the
> buffer, to keep the current view unchanged after doing ":w", which
> previously caused the window to scroll back to the very beginning of
> the buffer. I believe it's
On Di, 08 Aug 2023, Yegappan Lakshmanan wrote:
> I am not suggesting a separate minor release for each runtime file update
> here.
> Otherwise, we will have too many minor releases. Can we make a minor release
> only for PRs that change the C code and not the runtime files (still
> merge the r
On Di, 08 Aug 2023, Dominique Pellé wrote:
> I can see some bugs at https://huntr.dev/repos/vim/vim/
> but I have the impression that I only see those that are
> fixed, which then become public. The most recent one
> I see is from June 15, 2023. I'll look at this in more details
> later.
There
On Di, 08 Aug 2023, Marvin Renich wrote:
> Christian, just a suggestion for a minor grammatical correction:
>
> > ,
> > | [2023-08-09] The Vim project is deeply shocked and sad by the sudden
>^ saddened
Thanks, fixed.
> I would like
Yegappan Lakshmanan wrote:
> > About point #2 i.e. "Addressing reported security
> > vulnerabilities including those reported in https://huntr.dev/repos/vim/vim";
> > I never looked at this, as I thought only Bram had
> > access to bug reported there for security reasons.
> > But if I can have acc
* Christian Brabandt [230808 12:37]:
>
> After fighting with mysql for a while, this should be done now:
> https://www.vim.org/news/news.php sharing here:
Christian, just a suggestion for a minor grammatical correction:
> ,
> | [2023-08-09] The Vim project is deeply shocked and sad by the
Hi,
On Tue, Aug 8, 2023 at 8:39 AM Yegappan Lakshmanan wrote:
>
> Hi Dominique,
>
> On Mon, Aug 7, 2023 at 1:12 PM Dominique Pellé
> wrote:
> >
> > Yegappan Lakshmanan wrote:
> >
> > > Hi all,
> > >
> > > I am listing the tasks that Bram used to do for developing and maintaining
> > > Vim below
On Di, 08 Aug 2023, Yegappan Lakshmanan wrote:
>
> Yes. Also, there are references in the todo.txt file about many
> patches sent directly
> to Bram in the past. All these patches are lost now.
Yes + Brams check scripts, to verify there were no obvious errors in the
provided runtime files.
On Mo, 07 Aug 2023, Christian Brabandt wrote:
> Yes, it is on my agenad, once I return from vacation. I don't have currently
> SSH access on my vacation place (only HTTPs unfortunately).
After fighting with mysql for a while, this should be done now:
https://www.vim.org/news/news.php sharing h
On Di, 08 Aug 2023, Yegappan Lakshmanan wrote:
> Yes. I think we should move the PR model for the runtime file updates.
Yes, we should go ahead with this mode as of now. I am not sure, if this
will however cause problems with e.g. the vim-win32-installer
repository, if there are many changes
Hi Dominique,
On Mon, Aug 7, 2023 at 1:12 PM Dominique Pellé
wrote:
>
> Yegappan Lakshmanan wrote:
>
> > Hi all,
> >
> > I am listing the tasks that Bram used to do for developing and maintaining
> > Vim below (as far I can remember):
> >
> > 1. Developing fixes for Vim crash reports including th
Hi,
On Tue, Aug 8, 2023 at 8:18 AM Doug Kearns wrote:
>
> On Tue, 8 Aug 2023 at 06:12, Dominique Pellé
> wrote:
>
>
>
>> About point #9 i.e. "Incorporating the runtime file updates"
>> I've always found it odd that some changes were split into
>> a commit in src and another commit later in run
On Tue, 8 Aug 2023 at 06:12, Dominique Pellé
wrote:
About point #9 i.e. "Incorporating the runtime file updates"
> I've always found it odd that some changes were split into
> a commit in src and another commit later in runtime. It
> often caused confusion, with PR author asking "part of
> my c
This version saves and restores the view position while saving the
buffer, to keep the current view unchanged after doing ":w", which
previously caused the window to scroll back to the very beginning of
the buffer. I believe it's needles to say how annoying and actually
counterproductive that was
Thanks to the input file's dual nature, so to speak, using xxd(1)
to filter and edit binary files makes restoring the cursor position
broken. Fix that by ignoring the appropriate file type in the code
that restores the cursor position.
While there, refactor the code a bit to save a few CPU cycle
I wrote a post about Bram at my
blog: https://www.georgevreilly.com/blog/2023/08/07/BramMoolenaarRIP.html
On Monday, August 7, 2023 at 3:00:04 PM UTC-7 Yegappan Lakshmanan wrote:
Some more articles:
https://thenewstack.io/bram-moolenaar-author-of-the-open-source-vim-code-editor-has-died/
https:
28 matches
Mail list logo
