The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steve jenkin <>
To: TUHS <>
Subject: [TUHS] Re: Fwd: Message from the family of Bram Moolenaar
Date: Sun, 6 Aug 2023 11:34:25 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Thanks very much for the note.

The world for me is a greyer place with his passing.

Lots of articles on the ’Net of his passing.


> On 6 Aug 2023, at 06:08, Steffen Nurpmeso <> wrote:
> I do not know whether it is right, and i am surely not the right
> person to mourn in public, but i wanted to forward this.



	Main author of Vim, the text editor.

	I have been working on all kinds of software, 
		from machine code and assembly, via embedded software 
		to user interfaces and web applications.

	Spending most of my time working on Vim 9 script: faster, better.

	Now retired. 
	Last work i did for Google was modernizing Merchant Center.

	Worked on a nice new programming language: Zimbu. Paused for now.

		Spell checking algorithms, complex designs, being different.


A Tribute to Bram Moolenaar, The Maestro Behind Vim Code Editor

In a profound loss to the world of computing and software development, 
	Bram Moolenaar, 
the creator of the widely respected Vim code editor, has passed away at the age of 62. 
The family announced his passing in a heartfelt Google Groups message on August 5, 
revealing a sudden progression of a medical condition that had afflicted him.


Family Announcement


Steve Jenkin, IT Systems and Design 
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA

      parent reply	other threads:[~2023-08-06  1:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05 20:08 [TUHS] " Steffen Nurpmeso
2023-08-06  0:15 ` [TUHS] " Larry McVoy
2023-08-06  1:42   ` John Cowan
2023-08-06  2:03     ` Larry McVoy
2023-08-06 13:30       ` Andy Kosela
2023-08-06  1:34 ` steve jenkin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).