On Mon, August 27, 2012 22:16, Dan wrote:
> Steps:
> Put the following in your vimrc
> nnoremap z J
> autocmd BufWinLeave *.* mkview
> autocmd BufWinEnter *.* silent loadview
>
> In the commandline:
> vim ~/foo
>
> Insert this text:
> Test1
> Test1
>
> Test2
> Test2
>
> Fold the Test1 lines in one
> ...
>> advapi32.lib shell32.lib /machine:i386 /no
>
> Ok, the problem is in /machine:i386 which should be AMD64 for x64
> builds. Either something is wrong with your environment or
> Make_mvc.mak failed to detect the target architecture properly.
>
Thanks, you were right. I copied the line doi
On Tue, Aug 28, 2012 at 1:04 AM, Sergey Khorev wrote:
> set PROCESSOR_ARCHITECTURE
> set ASSEMBLY_ARCHITECTURE
> set CPU
Before and after setting the vars the result is the same:
C:\htemp\vim\src>set PROCESSOR_ARCHITECTURE
PROCESSOR_ARCHITECTURE=AMD64
C:\htemp\vim\src> set ASSEMBLY_ARCHITECTURE
> link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
...
> advapi32.lib shell32.lib /machine:i386 /no
Ok, the problem is in /machine:i386 which should be AMD64 for x64
builds. Either something is wrong with your environment or
Make_mvc.mak failed to detect the target architecture prope
> Can you remove ObjG again and paste here the full build log?
>
Sure, here it goes:
C:\htemp\vim\src> "c:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat"
Setting environment for using Microsoft Visual Studio 2010 x64 cross tools.
C:\htemp\vim\src>nmake -f
>> Apparently the linker tries using x86 binaries. The simplest solution
>> would be delete ObjG directory and build from scratch.
>>
>
> Thanks,
> I just tried that but the result is exactly the same. It compiles all
> the files correctly but linking gives the same error as before.
Can you remov
> Thanks for making this available. It's fairly small and a quick glance
> shows the license is liberal, so perhaps we should simply include it in
> the distribution. Otherwise I can put it on the Vim ftp site.
I think it's a good idea to include it into the distribution.
--
You received this
On Tue, Aug 28, 2012 at 12:11 AM, Sergey Khorev wrote:
>> .\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64'
>> conflicts with target machine typ
>> e 'X86'
>> NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio
>> 10.0\VC\BIN\x86_amd64\link
>> .EXE"' :
> .\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64'
> conflicts with target machine typ
> e 'X86'
> NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio
> 10.0\VC\BIN\x86_amd64\link
> .EXE"' : return code '0x458'
Apparently the linker tries using x86 bin
Hello,
By default the > markers of helpExample are not concealed which
causes them to be visible e.g. in transparent terminals because
the Ignore highlight group can't AFAIK make foreground text
invisible (ctermfg=NONE doesn't work for me).
The following patch adds concealends to hide them (thank
Steps:
Put the following in your vimrc
nnoremap z J
autocmd BufWinLeave *.* mkview
autocmd BufWinEnter *.* silent loadview
In the commandline:
vim ~/foo
Insert this text:
Test1
Test1
Test2
Test2
Fold the Test1 lines in one fold (enter visual mode, select them, then press zf)
Save and exit.
Op
Issue: views saved with mkview use "normal" instead of "normal!" commands to
recreate folding, causing user-create key mappings to trigger.
Steps to Reproduce:
Put the following in your vimrc
nnoremap z J
autocmd BufWinLeave *.* mkview
autocmd BufWinEnter *.* silent loadview
In the commandline:
---
runtime/doc/indent.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/runtime/doc/indent.txt b/runtime/doc/indent.txt
index ce02178..9804359 100644
--- a/runtime/doc/indent.txt
+++ b/runtime/doc/indent.txt
@@ -540,7 +540,7 @@ The examples below assume a 'shiftwidth'
Hello list.
I am using GVim/W7 as an OS shell having a boost in productivity over the last
months.
How can I remove the WS_SYSMENU properties in GVim besides removing it from the
code and recompile every time ?
Any hack on Windoze which removes WS_SYSMENU globally will be appreciated.
Regards
Sergey Khorev wrote:
> >> Note that depending on the license the source files need to be included
> >> as well. At least include a README that mentions the copyright.
> >
> > I am travelling now and don't have 64bit compiler on my laptop. Will
> > prepare the zip when I'm back (in 2 weeks).
>
>
On Mon, Aug 27, 2012 at 9:28 AM, skeept wrote:
> This is already a quite old thread but I can't find easily any instruction
> on how to compile vim for 64 bit windows. I am using windows 7.
>
> I tried the following:
>
> first I call
> "c:\Program Files (x86)\Microsoft Visual Studio
> 10.0\VC\bin
The following steps can reproduce the odd behaviour:
(you may firstly try this plugin
http://www.vim.org/scripts/script.php?script_id=4177 to monitor the undotree in
realtime)
1. Open Vim, which will initialize an empty new file.
2. Make some changes. Say, adding three new lines.
3. Now, the und
This is already a quite old thread but I can't find easily any instruction on
how to compile vim for 64 bit windows. I am using windows 7.
I tried the following:
first I call
"c:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat"
to set up the vars to 64 bit
Marc Weber wrote, on lun 27 aoû 14:46 :
> This is what I personally consider important and knowworthy for new
> users:
> https://github.com/MarcWeber/vim-addon-manager/blob/master/autoload/sample_vimrc_for_new_users.vim
>
> It also references the one on the wiki page:
> http://vim.wikia.com/wiki
hi thanks,it's very useful to me
On Wednesday, October 21, 2009 10:26:10 PM UTC+8, Arkanosis wrote:
> Hello,
>
> I've just started to use Vim, and missed the possibility to display
> middle-dots (or any other visible character) instead of spaces, so I
> made the following patch.
> It adds "space"
This is what I personally consider important and knowworthy for new
users:
https://github.com/MarcWeber/vim-addon-manager/blob/master/autoload/sample_vimrc_for_new_users.vim
It also references the one on the wiki page:
http://vim.wikia.com/wiki/Example_vimrc
You already mastered vim :) - You've f
I wish to submit some ideas regarding the vimrc provided with the vim
distribution. For example, these completion options :
> set wildchar=
> set wildmode=list:full,full " Or something similar
> set wildmenu
turn the :help command into a more friendly and easy to use on-line
help, even
Hi List,
I have been recently using the conceal feature a lot. It's very fun. However
it's still missing in some places for what I want (and looking at the list,
other people, too), so I thought I'd chime in.
I think the following conversation is the current status of the issue:
On Sunday, Augu
23 matches
Mail list logo
