Re: New Icon for Windows.

2015-02-13 Fir de Conversatie James McCoy
On Fri, Feb 13, 2015 at 03:02:03PM -0800, Edward Fox wrote: > On Fri, Feb 13, 2015 at 1:43 PM, Edward Fox wrote: > [...] > > I agree that it looks much better. The "Vim" text in front has > > good-looking texture. The dialog after has quite nice shadow effect, > > too. However, it's somehow quite

Re: New Icon for Windows.

2015-02-13 Fir de Conversatie Edward Fox
On Fri, Feb 13, 2015 at 1:43 PM, Edward Fox wrote: [...] > I agree that it looks much better. The "Vim" text in front has > good-looking texture. The dialog after has quite nice shadow effect, > too. However, it's somehow quite stylized to Mac. Usually the whole > community would prefer the standa

Re: linebreak and conceal display problems

2015-02-13 Fir de Conversatie Christian Brabandt
On Do, 29 Jan 2015, Benjamin Fritz wrote: > I know there have been recent problem with linebreak when combined with > conceal, I think I have found one or two more. > > With the attached test.vim file as a .vimrc, enter the following text: > > bbee;some text > > The expected output is: > >

Re: New Icon for Windows.

2015-02-13 Fir de Conversatie Edward Fox
Hi Pat, Thank you so much for your work. Yes, we definitely need to re-compose the icon for Windows build! On Fri, Feb 13, 2015 at 11:55 AM, Pat Suwalski wrote: > Hello, > > I normally do not use Windows, but for some recent work, I needed that > environment. I was surprised that the Vim Window

Re: [bug] outcome of delete "inner tag block" changes with indent of closing tag

2015-02-13 Fir de Conversatie Yegappan Lakshmanan
Hi, On Fri, Feb 13, 2015 at 10:01 AM, Christian Brabandt wrote: > Hi Bram! > > On Mo, 09 Feb 2015, Bram Moolenaar wrote: > >> > Here is a patch including a test case. > > Updated patch (mainly changing some comments) available at: > https://github.com/chrisbra/vim-mq-patches/blob/master/inner_tag

Re: [bug] outcome of delete "inner tag block" changes with indent of closing tag

2015-02-13 Fir de Conversatie Bram Moolenaar
Christian wrote: > On Mo, 09 Feb 2015, Bram Moolenaar wrote: > > > > Here is a patch including a test case. > > Updated patch (mainly changing some comments) available at: > https://github.com/chrisbra/vim-mq-patches/blob/master/inner_tagblock_inconsistent > > > We should actually divide the l

Re: New Icon for Windows.

2015-02-13 Fir de Conversatie David Fishburn
> > ... > This icon looks much better in modern Windows, and simply reuses artwork > already available for the Mac build. The last icon is derivative work by > me, using the outlines of the original 16x16 icon and coloured to the 32bpp > icon. > > Is there any chance of making it into the offici

New Icon for Windows.

2015-02-13 Fir de Conversatie Pat Suwalski
Hello, I normally do not use Windows, but for some recent work, I needed that environment. I was surprised that the Vim Windows icon looks quite dated, so I took a few minutes to make a new one. "vimicon.png" shows the before and after. In modern Windows, the old 32x32 4-bit icon was being str

Re: [bug] outcome of delete "inner tag block" changes with indent of closing tag

2015-02-13 Fir de Conversatie Christian Brabandt
Hi Bram! On Mo, 09 Feb 2015, Bram Moolenaar wrote: > > Here is a patch including a test case. Updated patch (mainly changing some comments) available at: https://github.com/chrisbra/vim-mq-patches/blob/master/inner_tagblock_inconsistent > We should actually divide the length of the todo list by

Re: Issue 77 in vim: [patch] Non-empty file without EOL markers should use default fileformat instead of mac.

2015-02-13 Fir de Conversatie vim
Comment #4 on issue 77 by chrisbr...@googlemail.com: [patch] Non-empty file without EOL markers should use default fileformat instead of mac. https://code.google.com/p/vim/issues/detail?id=77 Updated minimal patch available at https://github.com/chrisbra/vim-mq-patches/blob/master/issue71_m

Re: Issue 329 in vim: Vim doesn't compile with Lua 5.3 on windows

2015-02-13 Fir de Conversatie vim
Comment #4 on issue 329 by ktakata6...@gmail.com: Vim doesn't compile with Lua 5.3 on windows https://code.google.com/p/vim/issues/detail?id=329 I also tested the patch with Lua 5.1. -- You received this message because this project is configured to send all issue notifications to this add

Re: Issue 330 in vim: Vim hangs when run within smbfs directory

2015-02-13 Fir de Conversatie vim
Comment #4 on issue 330 by freegli...@gmail.com: Vim hangs when run within smbfs directory https://code.google.com/p/vim/issues/detail?id=330 btw if i mount the directory without -EUTF8:CP1251 vim runs fine too. -- You received this message because this project is configured to send all is

Re: Issue 330 in vim: Vim hangs when run within smbfs directory

2015-02-13 Fir de Conversatie vim
Comment #3 on issue 330 by freegli...@gmail.com: Vim hangs when run within smbfs directory https://code.google.com/p/vim/issues/detail?id=330 Breakpoint 1, set_init_1 () at option.c:3348 3348p = (char_u *)_(*(char **)options[opt_idx].var); Current language: auto; currently mi

Re: Issue 330 in vim: Vim hangs when run within smbfs directory

2015-02-13 Fir de Conversatie vim
Comment #2 on issue 330 by freegli...@gmail.com: Vim hangs when run within smbfs directory https://code.google.com/p/vim/issues/detail?id=330 I've build debug version of vim, so i could "break option.c:3348" in gdb, but the freeze seems to be in the pthread_np.so calling for open() in lib

Re: Windows GVim Freezes on Redraw

2015-02-13 Fir de Conversatie Yukihiro Nakadaira
On Fri, Feb 13, 2015 at 8:14 PM, wrote: > Bump. No thoughts on this? > Maybe it calls Vim's function from non-main thread? Vim is not thread safe. -- Yukihiro Nakadaira - yukihiro.nakada...@gmail.com -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your rep

Re: Issue 331 in vim: Long lines and and fileformats

2015-02-13 Fir de Conversatie vim
Updates: Status: Duplicate Mergedinto: 77 Comment #1 on issue 331 by chrisbr...@googlemail.com: Long lines and and fileformats https://code.google.com/p/vim/issues/detail?id=331 This looks like issue 77. In fact, using the patch from issue 77, I can't reproduce it anymore.

Re: Issue 77 in vim: [patch] Non-empty file without EOL markers should use default fileformat instead of mac.

2015-02-13 Fir de Conversatie vim
Comment #3 on issue 77 by chrisbr...@googlemail.com: [patch] Non-empty file without EOL markers should use default fileformat instead of mac. https://code.google.com/p/vim/issues/detail?id=77 Issue 331 has been merged into this issue. -- You received this message because this project is conf

Re: Windows GVim Freezes on Redraw

2015-02-13 Fir de Conversatie unknown3000
Bump. No thoughts on this? -- -- 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

Issue 331 in vim: Long lines and and fileformats

2015-02-13 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 331 by tarcisio...@gmail.com: Long lines and and fileformats https://code.google.com/p/vim/issues/detail?id=331 What steps will reproduce the problem? 1. Run this command: function gen_str { perl -e '@l = "a".."z"; print(join(

Re: Issue 329 in vim: Vim doesn't compile with Lua 5.3 on windows

2015-02-13 Fir de Conversatie vim
Comment #3 on issue 329 by mpc.jans...@gmail.com: Vim doesn't compile with Lua 5.3 on windows https://code.google.com/p/vim/issues/detail?id=329 That sounds like the proper way of doing it. I am just wondering if this will break the build for people using older Lua versions? -- You receiv

Re: Issue 330 in vim: Vim hangs when run within smbfs directory

2015-02-13 Fir de Conversatie vim
Comment #1 on issue 330 by chrisbr...@googlemail.com: Vim hangs when run within smbfs directory https://code.google.com/p/vim/issues/detail?id=330 Can you show a backtrace? Could you build you own debug version to be able to get a meaningful backtrace? -- You received this message because