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:
you can't.
Vim.org is a PHP-based website, but is it actually using any server-side
code? If it's static HTML, then GitHub Pages is quite satisfactory.
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
*www.GeorgeVReilly.com <http://www.georgevreilly.com/>*
--
--
You
On Mon, Apr 4, 2016 at 1:16 PM, Christian J. Robinson
wrote:
> On Mon, 4 Apr 2016, Bram Moolenaar wrote:
>
> I have been wondering if the next release should be called 7.5 or 8.
>>
>
> I'm inclined to think it should be version 8.
+0.6
--
/George V. Reilly
m/wiki/Working_with_Unicode
> etc.
Several monospace fonts have recently grown support for programmer-related
ligatures, such as https://github.com/i-tu/Hasklig and
https://github.com/tonsky/FiraCode.
BTW, there's a great list of monospaced fonts at
https://github.com/chrissimpkins/codeface
ll Requests [1], though I haven't worked with them.
Google Code does not [2].
1: https://confluence.atlassian.com/display/BITBUCKET/Work+with+pull+requests
2: https://code.google.com/p/support/issues/detail?id=4753
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.ge
Let's not make life any harder for semi-modern versions of Windows at
the expense of versions that have been obsolete for a decade. XP
still has approximately one-third market share. Anything before that
is lost in the noise. Anyone obdurate enough to run NT4 or Win2K can
settle for Vim 7.3
es at
http://code.google.com/p/vim-win3264/downloads/list that will help in
building a native Win64 build of Vim. I don't use Windows much anymore and
when I do, I run the Win32 binaries by default on Win64, for the reasons
elucidated at http://code.google.com/p/vim-win3264/
--
/George V. Rei
eve Yegge of Google talked at the Northwest C++ Users' Group about an
indexing tool like you describe. Unfortunately, it was intended for
Google's internal codebase. There were vague noises about making it more
widely available, but I haven't heard anything more.
http://www.nwcp
hg.python.org/cpython/file/b8593ec7e8c5/Lib/subprocess.py
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below t
ing bitwise operators, you also need left shift (#<<), signed right
shift (#>>), and unsigned right shift (#>>>), per
http://docs.oracle.com/javase/tutorial/java/nutsandbolts/op3.html.
Without the shifts, constructing masks and isolating groups of bits is
hard.
-
ighlighting, it just yanks 'build_number'
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
alled.
This patch uses KEY_WOW64_64KEY to write to the native, non-redirected
registry. It should do the right thing, whether install.exe
is 32-bit or 64-bit, regardless of whether it's run on Win32 or Win64.
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.georgevreill
Unlike
Ruby 1.8, it simply wasn't possible with the MSVC compiler, because
1.9 came with include files and libs for MinGW only.
Vim can be built with either MSVC or MinGW, but the official Windows
builds have always been built with MSVC.
It'd certainly be nice to have Ruby 1.9 be the def
w.flexwiki.com site was not available, thus
> I could not check any specification there.
I haven't used Flexwiki in 3 years, so I forget the details of why 'bomb'
was needed.
I think Flexwiki is dead or nearly so. It seems like mapping .wiki files to
wikipedia (MediaWiki?) rat
e with the MSVC compiler.
I've never tried to get a 64-bit version of Perl running with Win64 Vim.
I think a better solution would be a smarter Windows installer for Vim which
included Win32 and Win64 copies of gvimext.dll and a Win32 gvim.exe, that
installed the appropriate flavor of the shell
I almost forgot. Test69 breaks for me with both the Win32 and Win64 builds:
nmake -f Make_dos.mak test69.out
I've attached test69.ok (dosified) and test69.out.
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
The attached patch makes Vim 72.376 build cleanly with the RC1 build
of Visual Studio 2010, targeting Win32 and Win64.
Updated binaries can be downloaded from http://code.google.com/p/vim-win3264/
--
/George V. Reilly geo...@reilly.org Twitter: @georgevreilly
http://www.georgevreilly.com/blog
Make_mvc.mak needs to be patched for Visual Studio 2010 Beta 1 too.
--
/George V. Reilly geo...@reilly.org
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist
Patch to make Windows Gvim high-DPI aware, per an email thread several weeks
ago.
--
/George V. Reilly geo...@reilly.org
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" mai
A one-line patch to make Vim build cleanly with Beta 1 of Visual Studio
2010.
--
/George V. Reilly geo...@reilly.org
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" mai
On Sun, Apr 5, 2009 at 11:12 PM, Spencer Collyer
wrote:
>
> On Sun, 05 Apr 2009 11:38:18 +0200, Tony Mechelynck wrote:
>>
>> On 05/04/09 04:33, George V. Reilly wrote:
>> >
>> > On Sat, Apr 4, 2009 at 5:31 PM, Tony Mechelynck
>> > wrote:
>>
of Vim or really old operating systems. Their numbers are
dwindling and supporting them has real costs in terms of testing and
code complexity. Look at the horrendous amounts of conditional code in
the C source. If they don't want to upgrade (or can't), they'll have
to accept li
On Thu, Apr 2, 2009 at 12:05 AM, Ron Aaron wrote:
> On Apr 2, 9:57 am, "George V. Reilly" wrote:
>> On Wed, Apr 1, 2009 at 11:23 PM, Ron Aaron wrote:
>> > It would also be "really nice" to allow a per-window font. That is,
>> > make 'gf
the two grids?
On a related note, it would be nice if it were possible to supply a
set of alternatives to guifont, as in CSS. GVim would work its way
down the list until it found one that was present on the system; e.g.,
:set guifont=Consolas:h12,Monaco:h12,Andale_Mono:h13,Lucida_Cons
On Tue, Mar 24, 2009 at 10:45 AM, Tony Mechelynck
wrote:
>
> On 24/03/09 18:23, George V. Reilly wrote:
>>
>> I have a reproable crash, apparently due to syntax highlighting memory
>> corruption.
>>
>> The stack traces below were taken with WinDbg whi
may be wrong.
0012ff94 7714e4b6 kernel32!BaseThreadInitThunk+0x12
0012ffd4 7714e489 ntdll!RtlInitializeExceptionChain+0x63
0012ffec ntdll!RtlInitializeExceptionChain+0x36
I don't have time to look into this further today.
--
/George V. Reilly geo...@reilly.org
http://www.
CVim::SendKeys() */
> ! }
>return;
> }
> #endif
The patch looks good, though Ray's suggestion of RegisterWindowMessage
might be safer.
I'd argue, however, that the fault really lies with Ultramon. It's
supposed to unobtrusively hook into other proce
flushslist
>
> Now, the interesting bit. If I use Visual Studio 2008 Express with the
> SDK addon to build a 64-bit version of gvim, I don't get any errors on
> if_ole.h and I get a working copy of gvim.exe.
>
> Has anyone else tried this?
>
Trying the mingw-x64 build has
at on all systems?
More specifically, qsort expects a signed int. If MyCompare returns
1E37 - 1E20, it's probably not going to have a happy ending.
--
/George V. Reilly [EMAIL PROTECTED]
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
;& !defined(_WIN64) case?
Better, I think, to return (long_u) min(0xFF00, msex.ullAvailPhys
+ msex.ullAvailPageFile). Or for Bram to widen this signature to a
64-bit int for all platforms. Linux and Mac boxes with >4GiB are going
to be common soon.
--
/George V. R
et_fmode is not defined in VC2003 -- though I could have sworn it
was. It seems to have been introduced in VC2005. I guess you don't
build the debug binaries often.
I've checked the patch with VS98, VS2003, VC 2003 Toolkit, VS2005, and
VS2008 (x86 and x64). VS98 knows nothing about /Wp6
2008/7/14 Bram Moolenaar <[EMAIL PROTECTED]>:
> George V. Reilly wrote:
> > I believe I have it this time. ex_helpgrep is setting p_cpo =
> > (char_u*)"", then that's being free'd as a side-effect of an autocmd
> > doing "set cpo&vim&qu
2008/7/14 Bram Moolenaar <[EMAIL PROTECTED]>:
>
> George V. Reilly wrote:
>
>> >> An autocmd, selectbuf#BufNew, is calling set cpo&vim. Vim is freeing
>> >> invalid memory for the old value from did_set_string_option. The
>> >> previous val
2008/7/9 Bram Moolenaar <[EMAIL PROTECTED]>:
> George V. Reilly wrote:
>
>> An autocmd, selectbuf#BufNew, is calling set cpo&vim. Vim is freeing
>> invalid memory for the old value from did_set_string_option. The
>> previous value was (probably) set
${VIMSRC}\xxd.exe -> ${VIMSRC}\xxd\xxd.exe
> ${VIMRT}\README.txt -> ..\README.txt
> etc.
>
> Eventually, I gave up. Is there something I should have done
> differently to make it Just Work(tm)?
>
I ran into the same problems when I tried many months ago. Bram says that
it's a
n
Win64.
2. After I've built vim, which files do I need? There are several EXEs
> and DLLs produced in a couple different subdirectories of src/, but
> the INSTALL* documentation files don't explain what to do with them in
> the absence of UNIX-style "make install". For e
An autocmd, selectbuf#BufNew, is calling set cpo&vim. Vim is freeing
invalid memory for the old value from did_set_string_option. The
previous value was (probably) set by vim72a\menu.vim.
I think get_varp_scope() is at fault.
/George
-- Forwarded message --
From: Geor
ve not yet looked into trying to make the NSIS installer
work with the Win64 binaries.
I'm attaching a small patch that fixes all build warnings with
the VC8 and VC9 x64 compilers.
Note: ":helpgrep libintl" crashes for me when I build with VC9,
but not VC8. I have not
ertainly how I'd do it in Windows. I don't know enough about SO's
under Linux/Mac.
> It may be reasonable to have a limited number of callbacks available, though
> that would be an unfortunate restriction. Any ideas on this?
> Oh, one last thing. in the callback example ment
Getting them from a previous version might help. Or using
> empty files.
>
> Anyway, it would be very helpful to find out how to build a gvim.exe
> that runs on Windows 98 using VC 2008.
Which version of make do you build this Makefile with? Cygwin? Something else?
--
/George V. Reilly
FTP, CVS, and SVN
repositories is ... unsatisfying.
--
/George V. Reilly [EMAIL PROTECTED]
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
tried to
build a Vim installer several months ago and gave up in complete
frustration. My guess was that you had some additional build scripts
which weren't in the SVN archive.
--
/George V. Reilly [EMAIL PROTECTED]
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
http://docs.sun.com/source/806-3568/ncg_goldberg.html. I should re-read it
myself; it's been years.
--
/George V. Reilly [EMAIL PROTECTED]
http://www.georgevreilly.com/blog http://blogs.cozi.com/tech
--~--~-~--~~~---~--~~
You received this message from the &qu
> This would be of great benefit to all web developers using
> > VIM.
>
> to me this sounds very interesting, and very useful
>
This is the first GSoC proposal that I've seen float past that really made
me perk up, probably because I've been doing a lot of complex web
develop
On 20/02/2008, Richard Hartmann <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, Feb 21, 2008 at 12:21 AM, George V. Reilly <[EMAIL PROTECTED]>
> wrote:
>
>
> > The same caveats apply on Windows, which wasn't clear in Bram's help
> text.
>
>
> I a
xactly. So if you were to create a permanent save file of whatever based
> on
> that number, you could lose data. Granted that it's unlikely, but
> clarification
> in the help file can't hurt.
The same caveats apply on Windows, which wasn't clear in Bram's help text
On 02/02/2008, George V. Reilly <[EMAIL PROTECTED]> wrote:
>
> I'm trying to write some syntax highlighting for PBwiki, and I'd like to
> reuse some complex regexps. Here are some concrete examples:
> http://pbwiki.com -and-
> [http://pbwiki.com/|PBw
let + execute. That makes a lot of sense. Thanks
/G
On 03/02/2008, Szabolcs <[EMAIL PROTECTED]> wrote:
>
>
>
>
> On Feb 3, 7:04 am, "George V. Reilly" <[EMAIL PROTECTED]> wrote:
> > I'm trying to write some syntax highlighting for PBwiki, and I&
x match pbwikiLink
[EMAIL PROTECTED],4}`
syntax match pbwikiLink
[EMAIL PROTECTED],4}|[^]].\{-}\]`
How do I reuse the URL regexp and the email regexp inside the
[|]?
--
/George V. Reilly
http://www.georgevreilly.com/blog
--~--~-~--~~~---~--~~
You received thi
your system. Most notably:
>
> 12.12.2007 14:03 1'670 _H_A_ .vimrc
> 0
> {4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
>
Every NTFS file is implemented as one or more streams, and the default
stream is called $DATA. It's a b
On 16/01/2008, George V. Reilly <[EMAIL PROTECTED]> wrote:
> On 14/01/2008, Mike Williams <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Catching up from the weekend patches I had two warnings for my builds.
> > The attached patch fixes them - done against 7.1
o.
I'm not saying that it can't be done, but it moves the Vim codebase in
a direction that it's never gone before.
Is there some existing open source project that can be leveraged to
solve a lot of these problems? Or some Google project?
--
/George V. Reilly
http://www.georgev
On 15/01/2008, Mike Williams <[EMAIL PROTECTED]> wrote:
> On 14/01/2008 21:43, George V. Reilly wrote:
> > On 14/01/2008, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> >>
> >> Mike Williams wrote:
> >>
> >>> Catching up from the weekend
g if LONGLONG is always defined when WIN3264 is defined. We
> don't use LONGLONG yet anywhere.
LONGLONG should be defined in all recent versions of the compiler and
SDK. Always as a 64-bit signed quantity. Recent = last six years or
so.
more compilers before I'm happy with it.
--
/George V. Reilly
http://www.georgevreilly.com/blog
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
55 matches
Mail list logo
