Hi Ben,
It looks like the x64 build gets compiled with two gvimext libraries, one for
each arch where the x64 version is appended with a 64 (gvimext64.dll). However
the installer is unaware of this and creates the following example reg entry:
I wanted to file some issues for the Windows nightly builds however the Github
issues tab is disabled. Where is the correct place for doing this?
Thanks.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
On Wednesday, October 5, 2016 at 2:36:06 AM UTC-6, Ken Takata wrote:
> You can check the function RegisterMe() in src/if_ole.cpp.
> It writes some data to the registry and calls RegisterTypeLib() API.
Thanks Ken.
--
--
You received this message from the "vim_use" maillist.
Do not top-post!
On Tuesday, October 4, 2016 at 1:00:44 PM UTC-6, Ben Fritz wrote:
> Is something missing from the official nightly installers?
Hi Ben,
I never knew the project was officially producing x64 binaries on github.
I have switched over to them (and I noticed they already bundle diff.exe).
I would like
I am writing an MSI installer based on the compiled distribution that
https://tuxproject.de/projects/vim/ distributes. I looked through the source
briefly but not being fluent I wasn't certain.
What exactly happens when a user runs `gvim.exe -register` to complete the ole
registration? I'd
On May 1, 3:10 pm, Ritmo2k jcas...@gmail.com wrote:
no backups are made in /tmp? How do you control this?
The 'backupskip' option; the default value includes /tmp/*.
Please excuse me if I'm wrong, but you seem unaware how good vim's
help is. Mucking around with the whatever option, it's
:help backupskip says,
{not available when compiled without the |+wildignore| feature}
Ahh, so if not specified, it defaults to exclude the /tmp dirs.
adding 'set backupskip=' gets the behavior I wanted.
Thanks guys!
--
You received this message from the vim_use maillist.
Do not
With an empty .vimrc or one with just set backup in it, or
typing :set backup, I can't get a backup file created on any
of my CentOS 5 servers. It used to work and has recently stopped
on all of them?
A strace on a remote hosting chroot running an older version of Centos
shows it working as
My guess is that your newer Centos comes with a system vimrc that
contains some setting that's interfering with your backups.
One way to check this is to execute
:scriptnames
and look for a system vimrc being sourced. It might be
/etc/vimrc or /usr/share/vim/vimrc. See
:help
