Hi,
Attached is a patch which was made to suppress some compiler warning put out by
a recent version of clang.
I'm on Mac OS X 10.8.5 and upgraded Xcode from 4.6.x to 5.0 a few days ago.
With that IDE, a new version of clang came and, when I had it compile vim, it
was complaining:
clang:
There one inconvenient thing in error messages: they come with line numbers
relative to the function start. This means to see the line that caused the
error you either need to use :fu or find function name in a file (and file
is only seen with :verb fu), be sure you open all folds contained in a
At the moment, when starting gvim --remote-silent gvim would display an error
message, indicating that no file name was provided.
This is quite a nasty behavior if you - like me - at times just start gvim
(using a macro including --remote-silent) w/o a file name just to get gvim
up and running
On 23:00 Wed 25 Sep , Christian Brabandt wrote:
Bram,
currently, the colorscheme autocommand matches the pattern against the
buffer name. I think, it would be more useful, to have the pattern match
against the actual colorscheme name. So here is a patch, that changes
it.
regards,
Full version info below; tl;dr == 7.3. I know this is old, but it's what's on
the server and I can't/don't have time to do anything about it.
I am editing source that has been badly converted dos=unix in the past, and
all the^M
lines^M
look like this^M
A common issue we're all familiar with. I
Wang Shoulin wrote:
os_mswin.c
os_mswin.c(536) : error C2065: 'intptr_t' : undeclared identifier
os_mswin.c(536) : error C2146: syntax error : missing ')' before identifier
'h'
os_mswin.c(536) : error C2198: '_open_osfhandle' : too few actual parameters
os_mswin.c(536) : error C2059:
Hi studog!
On Do, 26 Sep 2013, studog wrote:
Full version info below; tl;dr == 7.3. I know this is old, but it's what's on
the server and I can't/don't have time to do anything about it.
I am editing source that has been badly converted dos=unix in the past, and
all the^M
lines^M
look
(CC'ing vim-dev)
On Do, 26 Sep 2013, studog wrote:
On Thursday, September 26, 2013 2:40:47 PM UTC-4, Christian Brabandt wrote:
On Do, 26 Sep 2013, studog wrote:
Is this a known issue? Is it fixed in 7.4?
When using f/t, Vim gets the following char literally, which means, you
don't
Kazunobu Kuriyama wrote:
Attached is a patch which was made to suppress some compiler warning
put out by a recent version of clang.
I'm on Mac OS X 10.8.5 and upgraded Xcode from 4.6.x to 5.0 a few days
ago. With that IDE, a new version of clang came and, when I had it
compile vim, it
On Thursday, September 26, 2013 11:17:08 PM UTC+4, Christian Brabandt wrote:
(CC'ing vim-dev)
On Do, 26 Sep 2013, studog wrote:
On Thursday, September 26, 2013 2:40:47 PM UTC-4, Christian Brabandt wrote:
On Do, 26 Sep 2013, studog wrote:
Is this a known issue? Is it fixed in 7.4?
On Do, 26 Sep 2013, ZyX wrote:
But if t/T/f/F/r/gr are changed to accept C-v and C-k it will make
Actually, they do accept C-K.
them more consistent with other *normal-mode* things like `d`
operator: currently t/T/f/F/r/gr are not cancelled by C-c. In fact
Yeah, they accept C-C and try to
On Sep 26, 2013 11:52 PM, Christian Brabandt cbli...@256bit.org wrote:
On Do, 26 Sep 2013, ZyX wrote:
But if t/T/f/F/r/gr are changed to accept C-v and C-k it will make
Actually, they do accept C-K.
them more consistent with other *normal-mode* things like `d`
operator: currently
On 26 September 2013, Nikolay Pavlov zyx@gmail.com wrote:
There one inconvenient thing in error messages: they come with line
numbers relative to the function start. This means to see the line
that caused the error you either need to use :fu or find function name
in a file (and file is
On Wednesday, September 25, 2013 9:09:48 PM UTC-7, ZyX wrote:
On Sep 26, 2013 3:30 AM, kans mkan...@gmail.com wrote:
Java is the most used language these days and uses the Timer class.
JavaScript wasn't designed properly, it has lots of confusing stuff, I
would never
Yep,
I'm James Kolb.
On Wed, Sep 25, 2013 at 7:53 AM, Bram Moolenaar b...@moolenaar.net wrote:
James wrote:
Right now, there can't be right-aligned one-character signs(like sign
define rightsign text=\ r), because prefixing a sign with a space
breaks the define statement.
The
Hey, is it a good practice™ to promote your plug-ins in these mailing lists? I
have one I’ve been working on [1], but I don’t want to spam you guys.
[1]: http://jalcine.me/weblog/introducing-cmake-for-vim/
--
Jacky Alciné - PGP: 201999FC
http://jalcine.me
signature.asc
Description: This is a
On Sep 27, 2013 12:29 AM, LCD 47 lcd...@gmail.com wrote:
On 26 September 2013, Nikolay Pavlov zyx@gmail.com wrote:
There one inconvenient thing in error messages: they come with line
numbers relative to the function start. This means to see the line
that caused the error you either
This bug was reported in the Arch Linux bugtracker [1]
Just tested this behaviour in 7.4.041 and it stays the same.
With the new regexpengine the movement with j and k is massively slow.
Visible lag on a core i7 3GHz is extreme i might say.
I personally have no idea how to fix it right now so
18 matches
Mail list logo
