+1 on getting this fixed. This bug has been pretty annoying as of late.
Cheers
On Monday, January 5, 2015 5:06:09 AM UTC-8, mattn wrote:
> Sorry it's an expected
>
> On 1/5/15, mattn wrote:
> >
> > bug.vim
> > ---
> > set nocompatible
> >
> > inoremap =ListMonths()
> >
> > func
made sense.
On Monday, January 5, 2015 10:38:43 AM UTC-8, Amadeus Demarzi wrote:
> +1 on getting this fixed. This bug has been pretty annoying as of late.
>
> Cheers
>
> On Monday, January 5, 2015 5:06:09 AM UTC-8, mattn wrote:
> > Sorry it's an expected
> >
> &
you say, and that functionality would have to be fixed in
NeoComplete.
On Tuesday, January 6, 2015 2:39:56 AM UTC-8, Christian Brabandt wrote:
> Am 2015-01-05 20:02, schrieb Amadeus Demarzi:
> > I just tested this patch, and it doesn't quite work the way it had
> > origina
You are a god amongst men Christian, works like a charm, thanks!
On Tuesday, January 6, 2015 10:25:43 AM UTC-8, Christian Brabandt wrote:
> Hi vim_dev!
>
> On Di, 06 Jan 2015, Christian Brabandt wrote:
>
> > Am 2015-01-05 20:02, schrieb Amadeus Demarzi:
> > >I jus
Using vim with patches 1-567 I get a range error when calling wincmd in certain
contexts:
vim -u NONE
:split
:wincmd+ # works as expected
:2wincmd+ # also works as expected
:3wincmd+ # throws the error: Invalid Range
In fact, any value above 2 seems to throw this error.
--
--
You received thi
On Tuesday, January 6, 2015 at 6:15:50 PM UTC-8, h_east wrote:
> Hi list,
>
> 2015/1/7(Wed) 4:09:31 UTC+9 h_east:
> > Nice. Perhaps I think that We need a little more modification such an
> > attached a patch url.
> > https://gist.github.com/h-east/be555467ddfc3dfb8d54
>
> I updated Gist. (Add l
I am very excited that Github is being considered. It has become something of a
standard for open source software these days, for better or worse, it's what
most people are using which I think is good for Vim.
For those of you unfamiliar with Git, I HIGHLY recommend reading this free book:
http
Ben: I would argue that Github provides a huge variety of useful tools to
manage Vim that will net a major net positive going forward.
Having a central place for issues and patches that is very familiar to many
developers will help to make the barrier of entry for new contributors far
lower as
It appears that ce vs cw is actually intended behavior. More info here -
https://groups.google.com/forum/#!topic/vim_use/iLZJm7ywh40
These macvim issues should be brought up to the MacVim maintainer, they aren't
issues that Vim can fix, per se since they deal with how OSX deals with the
macvim
I should add that here is where you can report Macvim issues:
https://github.com/macvim-dev/macvim
On Thursday, April 16, 2015 at 12:52:40 PM UTC-7, Amadeus Demarzi wrote:
> It appears that ce vs cw is actually intended behavior. More info here -
> https://groups.google.com/forum/#
I should add that here is where you can report MacVim issues:
https://groups.google.com/forum/?hl=en#!forum/vim_mac
On Thursday, April 16, 2015 at 12:52:40 PM UTC-7, Amadeus Demarzi wrote:
> It appears that ce vs cw is actually intended behavior. More info here -
> https://groups.goog
So this is a post that is in regards to what I think may be an overall
limitation in the syntax region API, or perhaps there is some sort of
workaround that I am not thinking of, but I figured I would post here to get
thoughts. I have a theory that it's not possible, but I would love to hear you
I've also noticed that if I do
:help guicolors
or
:help 'guicolors'
I get E149: Sorry no help for guicolors
On Monday, April 25, 2016 at 3:04:59 AM UTC-7, h_east wrote:
> Hi Ken!
>
> 2016-4-25(Mon) 18:58:05 UTC+9 Ken Takata:
> > Hi h_east,
> >
> > 2016/4/25 Mon 6:51:36 UTC+9 h_east wrote:
>
With the update to vim 7.4, it seems as if this particular regex just doesn't
match in particular cases in 7.4, but it worked fine in 7.3.
syntax region jsRegexpString
start=+\(\(\(return\|case\)\s\+\)\@<=\|\(\([)\]"']\|\d\|\w\)\s*\)\@http://www.vim.org/maillist.php
---
You received this m
etting the regexpengine=1 | syntax enable fixes the problem, although it's
a far from ideal solution.
On Tuesday, August 13, 2013 11:09:49 AM UTC-7, Bram Moolenaar wrote:
> Amadeus Demarzi wrote:
>
>
>
> > With the update to vim 7.4, it seems as if this particular r
p://github.com/pangloss/vim-javascript
>
> And setting the regexpengine=1 | syntax enable fixes the problem, although
> it's a far from ideal solution.
>
> On Tuesday, August 13, 2013 11:09:49 AM UTC-7, Bram Moolenaar wrote:
> > Amadeus Demarzi wrote:
> >
> &
Just curious if any headway has been made on this lookbehind regex issue?
I only ask because it breaks a pretty popular JS syntax plugin.
On Tuesday, August 13, 2013 5:34:52 PM UTC-7, Amadeus Demarzi wrote:
> Alright, so I am admittedly terrible with Regexes, but I think I did find
> som
I can confirm that Patch 2 fixes this! Thanks so much! Seriously!
On Wednesday, August 21, 2013 11:45:52 AM UTC-7, Amadeus Demarzi wrote:
> Just curious if any headway has been made on this lookbehind regex issue?
>
> I only ask because it breaks a pretty popular JS syntax plugin
I've been working with Jules on updating that syntax file and I was the one who
introduced that change.
It was only there to be able to target specific IE css hacks, and it could
trivially be removed for another update.
Let me know if you'd like this.
Cheers,
Amadeus
On Monday, September 23,
This is a feature I would find highly useful, and could enable many plugins to
operate more efficiently.
Has this ever come up for discussion? Perhaps there's a reason it hasn't been
done already?
I know with my workflow, I often first cd into a directory, and then operate
vim from there using
the same.
On Wednesday, October 2, 2013 2:14:40 PM UTC-7, David Fishburn wrote:
> On 2013-10-02, Amadeus Demarzi wrote:
>
>
>
>
> > This is a feature I would find highly useful, and could enable
>
> > many plugins to operate more efficiently.
>
>
> Isn't
I am interested in this patch for MacVim, unfortunately when I apply it, I get
the following errors.
Non verbose output:
~/Development/macvim: git apply file.patch
error: patch failed: src/option.c:8501
error: src/option.c: patch does not apply
Verbose output:
~/Development/macvim: git apply -v
Awesome, works like a charm, thanks!
On Sunday, October 6, 2013 8:17:36 PM UTC-7, Ken Takata wrote:
> Hi Amadeus,
>
> 2013/10/07 Mon 5:59:13 UTC+9 Amadeus Demarzi wrote:
> > I am interested in this patch for MacVim, unfortunately when I apply it, I
> > get the following
Obviously I am not a developer on this project, but as a lurker/avid vim user,
I can definitely say I would love to see something like this get incorporated
into the mainline vim.
On Friday, December 6, 2013 3:00:47 AM UTC-8, Thiago Arruda wrote:
> My last post(https://groups.google.com/forum/#!
I would love to see this added. I find those messages to be quite irritating
when using a lot of autocomplete.
On Tuesday, December 31, 2013 4:01:55 AM UTC-8, Shougo wrote:
> Hi, Bram.
>
>
>
> I created the patch for adding option to disable insert completion message in
>
> shortmess.
>
> B
hari.g:
Overall, this patch is pretty good. A couple things I have noticed:
1) Seems I must do `set incsearch` AFTER the `set showindent` declaration or
else incsearch never gets set?
2) It would be nice to also highlight the first column on indentations, to
match functionality with tabs
Thi
Christian, thanks for tackling a ton of little nitpicks I've had with Vim!
One thing in general that would be awesome if fixed, especially in line with
this patch, would be that when scrolling past lines that are wrapped, not
having the document jump the number of lines the wrap take up. It make
Not sure if this has already been fixed, but I noticed that with this JS Syntax
file:
https://github.com/pangloss/vim-javascript/
That lines directly after a comment continue to appear commented until there is
an empty line.
This is from the 1020 changeset merged into MacVim btw:
https://gith
This is far from a complete JS example file, but it does trigger the bug I
mentioned in the afore-linked repo:
https://gist.github.com/amadeus/5667508
On Monday, May 27, 2013 10:59:51 AM UTC+1, Bram Moolenaar wrote:
> I have fixed all the reported bugs in the NFA regexp engine.
>
> All the synt
!
On Wednesday, May 29, 2013 6:42:26 PM UTC+1, Bram Moolenaar wrote:
> Amadeus Demarzi wrote:
>
>
>
> > This is far from a complete JS example file, but it does trigger the
>
> > bug I mentioned in the afore-linked repo:
>
> >
>
> > https://gist
I was able to test the a version of Vim with the latest patches, consider my JS
comment error fixed!
Cheers
On Thursday, May 30, 2013 11:51:26 AM UTC+2, Bram Moolenaar wrote:
> Hiroshi Shirosaki wrote:
>
>
>
> > > > I noticed a syntax highlighting issue with filetype=html.
>
> > > > test.htm
I use `q` as my leader key, which means I have the following set in my vimrc:
let mapleader="q"
nnoremap q
vnoremap q
nnoremap Q q
vnoremap Q q
However, it seems on the newer builds of MacVim (specifically version 7.3 with
patches 1-1233) that when I press `q` in quickfix or nofile splits (lik
As per the reply in my issue I raised, I think this causes problems as
specified here:
https://groups.google.com/forum/#!topic/vim_dev/SIUBjOVmJx4
Is there any way to work around this?
On Saturday, June 22, 2013 1:52:22 PM UTC-7, Bram Moolenaar wrote:
> ZyX wrote:
>
>
>
> > How to disable th
Just a quick bump on this issue? Technically it seems like remaps in quickfix
and other specialized buffers can be broken due to patch 1179.
Cheers,
Amadeus
On Monday, June 24, 2013 11:54:56 AM UTC-7, Christian Brabandt wrote:
> Hi Amadeus!
>
>
>
> On Mo, 24 Jun 2013, Amadeu
Looks like my issue was fixed with most recent patches.
Cheers and thanks!
On Wednesday, June 26, 2013 10:04:33 PM UTC-7, Amadeus Demarzi wrote:
> Just a quick bump on this issue? Technically it seems like remaps in quickfix
> and other specialized buffers can be broken due to patc
This is probably going to be a bit long winded, so bear with me.
As a preface, I do a lot of HTML/CSS/Javascript development in vim. I use both
a special Javascript ( https://github.com/amadeus/vim-javascript ) and CSS (
https://github.com/amadeus/Better-CSS-Syntax-for-Vim ) plugin that override
I have attached a patch for this fix.
It essentially amounts to the change that I mentioned at the end.
Would it be possible to get this patch in?
Cheers,
Amadeus
On Wednesday, July 17, 2013 12:16:25 PM UTC-7, Amadeus Demarzi wrote:
> This is probably going to be a bit long winded, so b
This patch fixes javascript.vim and css.vim from clobbering plugin syntaxes
when sourced via html.vim.
Would it be possible to get this in for 7.4?
More details here:
https://groups.google.com/forum/#!topic/vim_dev/4Idz6Em2ZuU
It's a long explanation, so this would be the TL;DR for it
Cheers,
On Monday, July 22, 2013 1:50:39 PM UTC-7, Bram Moolenaar wrote:
> Amadeus Demarzi wrote:
>
>
>
> > This patch fixes javascript.vim and css.vim from clobbering plugin syntaxes
> > when sourced via html.vim.
>
> >
>
> > Would it be possible to get th
On Monday, July 22, 2013 1:57:34 PM UTC-7, Amadeus Demarzi wrote:
> On Monday, July 22, 2013 1:50:39 PM UTC-7, Bram Moolenaar wrote:
> > Amadeus Demarzi wrote:
> >
> >
> >
> > > This patch fixes javascript.vim and css.vim from clobbering plugin
>
On Monday, July 22, 2013 11:25:40 PM UTC-7, Amadeus Demarzi wrote:
> On Monday, July 22, 2013 1:57:34 PM UTC-7, Amadeus Demarzi wrote:
> > On Monday, July 22, 2013 1:50:39 PM UTC-7, Bram Moolenaar wrote:
> > > Amadeus Demarzi wrote:
> > >
> > >
> > >
On Sunday, July 28, 2013 11:05:26 AM UTC-7, Marcin Szamotulski wrote:
> On 19:02 Sun 28 Jul , Marcin Szamotulski wrote:
>
> > On 18:35 Sun 28 Jul , Bram Moolenaar wrote:
>
> > >
>
> > > Hello Vim users,
>
> > >
>
> > >
>
> > > Announcing: Vim (Vi IMproved) version 7.4b BETA
>
> >
On Sunday, July 28, 2013 1:07:17 PM UTC-7, Bram Moolenaar wrote:
> [ please start a new thread for unrelated messages )
>
>
>
> > Any chance this patch can get added as a todo for this beta?
>
> >
>
> > https://groups.google.com/forum/#!topic/vim_dev/o9-IL3zmuK0
>
>
>
> I think that was al
Unfortunately after this patch, I am unable to compile MacVim. I figured this
out through git bisect.
The last few lines from failed make are:
/System/Library/Frameworks/Foundation.framework/Headers/NSPropertyList.h:58:1:
note: 'propertyListFromData:mutabilityOption:format:errorDescription:' ha
44 matches
Mail list logo
