Confirmed, the docs are there now. Thanks!
On Wednesday, September 9, 2015 at 8:27:28 PM UTC+2, Bram Moolenaar wrote:
> Christian Wellenbrock wrote:
>
> > Really happy to see those new commands being added! After updating Vim
> > I tried :h :cdo, but no help was found. I che
Really happy to see those new commands being added! After updating Vim I tried
:h :cdo, but no help was found. I checked my repository and indeed, the added
documentation is nowhere to be found. As you can see in the commit on GitHub
[1] there are no changes to runtime/doc/quickfix.txt. Looks li
I just ran into the same problem ended up here. I would appreciate if this
could get fixed.
I'm using version 7.4.567 on Mac OS. Thanks!
On Monday, September 15, 2014 at 6:21:23 AM UTC+2, v...@googlecode.com wrote:
> Comment #1 on issue 212 by jke...@connectwise.com: feedkeys(".", "n")
> insid
Similarly, I feel like ":`<,`>" would be consistent with with how "'" is
linewise and "`" is character wise (single quote vs backtick).
On Monday, November 3, 2014 9:25:21 PM UTC+1, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > On Mi, 29 Okt 2014, Bram Moolenaar wrote:
> >
> > > It co
On Friday, June 13, 2014 4:39:37 PM UTC+2, Tom McDonald wrote:
> Here's a recording of a demonstration of the current behaviour:
>
> https://asciinema.org/a/10129
I agree that this change is useful and more consistent.
@Tom: In the meantime you could try targets.vim [1] which supports that
beha
On Thursday, June 12, 2014 12:54:14 PM UTC+2, bo...@airbladesoftware.com wrote:
> Hello!
>
> I have a plugin which updates signs when a CursorHold auto-command fires
> (among other auto-commands). When `updatetime` is set to a low value, say
> anything under 100, and highlighting is in effect,
On Wednesday, May 28, 2014 4:47:35 PM UTC+2, Bram Moolenaar wrote:
> I wrote:
>
>
>
> > Patch 7.4.310
>
> > Problem:getpos()/setpos() don't include curswant.
>
> > Solution: Add a fifth number when getting/setting the cursor.
>
> > Files: src/eval.c, src/testdir/test_eval.in,
On Friday, March 28, 2014 2:50:39 AM UTC+1, Daniel "paradigm" Thau wrote:
> On Thursday, March 27, 2014 1:05:08 PM UTC-4, Ben Fritz wrote:
> > On Friday, January 31, 2014 1:54:30 PM UTC-6, Daniel "paradigm" Thau wrote:
> > > On Thursday, January 30, 2014 9:07:19 PM UTC-5, Daniel "paradigm" Thau
>
On Saturday, March 8, 2014 12:37:38 AM UTC+1, v...@googlecode.com wrote:
> Comment #7 on issue 202 by howej...@gmail.com: Dot operator doesn't work
>
> with user-defined insert functions
>
> http://code.google.com/p/vim/issues/detail?id=202
>
>
>
> No problem! Thank you for your input.
>
>
On Saturday, February 15, 2014 5:25:10 PM UTC+1, Christian Wellenbrock wrote:
> On Saturday, July 6, 2013 1:35:26 PM UTC+2, Bram Moolenaar wrote:
>
> > Christian Wellenbrock wrote:
>
> >
>
> >
>
> >
>
> > > In order to test
On Saturday, July 6, 2013 1:35:26 PM UTC+2, Bram Moolenaar wrote:
> Christian Wellenbrock wrote:
>
>
>
> > In order to test the changes I made, I started out with a patch that
>
> > helped me to find and verify 'statusline' options that show the nine
>
On Wednesday, January 29, 2014 9:27:32 PM UTC+1, Christian Brabandt wrote:
> On Mi, 29 Jan 2014, Christian Wellenbrock wrote:
>
>
>
> > On Wednesday, January 29, 2014 3:51:25 PM UTC+1, glts wrote:
>
> > > On Wed, Jan 29, 2014 at 1:09 PM, Christian Wellenb
On Wednesday, January 29, 2014 3:51:25 PM UTC+1, glts wrote:
> On Wed, Jan 29, 2014 at 1:09 PM, Christian Wellenbrock
>
> wrote:
>
> > Here is a small example to illustrate the issue:
>
> >
>
> > echo 123456789 | vim - +":omap a0 :execute 'n
Here is a small example to illustrate the issue:
echo 123456789 | vim - +":omap a0 :execute 'norm 0v'.v:count1.'lh'"
This invocation puts the string "123456789" into a new buffer and creates an
operator-pending mapping `a0` that selects the first characters of the current
line for the pending
On Thursday, January 23, 2014 3:57:04 PM UTC+1, Christian Brabandt wrote:
> On Thu, January 23, 2014 15:48, Christian Wellenbrock wrote:
>
> > On Thursday, January 23, 2014 7:49:33 AM UTC+1, Ben Fritz wrote:
>
> >> On Thursday, January 23, 2014 12:10:32 AM UTC
On Thursday, January 23, 2014 7:49:33 AM UTC+1, Ben Fritz wrote:
> On Thursday, January 23, 2014 12:10:32 AM UTC-6, Anton Shemerey wrote:
> > Recently i made a mistake, and wrote following command, for selected text,
> > and editor just disappear
> >
> > i've tried it for bought vim, and macvim w
On Tuesday, January 21, 2014 9:24:27 PM UTC+1, Thiago Arruda wrote:
> This patch implements a simple but efficient form of job-control for
> vimscript,
>
> enabling vim to cooperate with long-running processes without blocking the UI.
>
>
>
> It is my second attempt to bring multitasking to vi
On Monday, January 20, 2014 1:08:07 PM UTC+1, Lech Lorens wrote:
> On 20-Jan-2014 Yukihiro Nakadaira wrote:
>
> > On Sun, Jan 19, 2014 at 1:45 PM, Anhad Jai Singh
>
> > wrote:
>
> >
>
> > >
>
> > > When I do 'o' (plain old 'o', no fancy mappings nothing, the deafult
>
> > > open-INSERT-mode
On Monday, January 20, 2014 1:37:10 AM UTC+1, Gary Johnson wrote:
> One problem I've found with using the quickfix window is that when
>
> it is open, the quickfix list traversal commands :cn, :cp, etc., no
>
> longer display "(n of m)" in the command line.
>
>
>
> To work around that problem,
On Tuesday, January 14, 2014 4:53:07 AM UTC+1, Thiago Arruda wrote:
> Today I got some free time and decided to give this patch another try.
>
>
>
> I have made a few modifications to the original:
>
>
>
> - Rebased against the current master
>
> - Removed the 'defer' function, and added an
On Thursday, November 14, 2013 12:23:03 AM UTC+1, Christian Wellenbrock wrote:
> On Monday, August 12, 2013 9:22:21 PM UTC+2, Christian Brabandt wrote:
> > On Do, 08 Aug 2013, Dimitar DIMITROV wrote:
> >
> >
> >
> > > As per the subject :)
> >
> &g
On Monday, August 12, 2013 9:22:21 PM UTC+2, Christian Brabandt wrote:
> On Do, 08 Aug 2013, Dimitar DIMITROV wrote:
>
>
>
> > As per the subject :)
>
>
>
> Can you check, whether the attached patch fixes it for you?
>
>
>
> regards,
>
> Christian
>
> --
>
> Was die Welt in diesem Auge
On Monday, September 30, 2013 6:01:58 PM UTC+2, Christian Brabandt wrote:
> On Mon, September 30, 2013 17:53, eckes wrote:
>
> > +1 have this demand too:http://stackoverflow.com/q/19097216/520162
>
>
>
> While I like the idea of having a :cdo and :ldo command, for the time
>
> being, you can s
On Wednesday, July 3, 2013 4:06:32 PM UTC+2, Christian Wellenbrock wrote:
> 2013/7/3 Bram Moolenaar
>
>
>
>
> Christian Wellenbrock wrote:
>
>
>
> > I added the MB_CHAR2LEN macro and used that instead of mb_char2len.
>
> >
>
> > Does th
2013/7/3 Bram Moolenaar
>
> Christian Wellenbrock wrote:
>
> > I added the MB_CHAR2LEN macro and used that instead of mb_char2len.
> >
> > Does the mb_char2bytes call need a has_mbyte check as well?
> >
> > Are there any other issues that need to resolved
;
>
> -Manny
>
>
> On Fri, Jun 14, 2013 at 3:22 PM, Christian Wellenbrock
> wrote:
>
>
>
>
> On Friday, June 14, 2013 9:15:48 PM UTC+2, Bram Moolenaar wrote:
>
>
> > Christian Wellenbrock wrote:
>
> > > > > I just cloned a
On Friday, June 14, 2013 9:15:48 PM UTC+2, Bram Moolenaar wrote:
> Christian Wellenbrock wrote:
>
>
>
> > > > I just cloned a completely new copy of the hg vim sources and called
>
> > > > make from the src folder. I get the following errors:
>
> &
On Friday, June 14, 2013 7:16:16 PM UTC+2, Bram Moolenaar wrote:
> Christian Wellenbrock wrote:
>
>
>
> > I just cloned a completely new copy of the hg vim sources and called
>
> > make from the src folder. I get the following errors:
>
> > https:
I just cloned a completely new copy of the hg vim sources and called make from
the src folder. I get the following errors:
https://gist.github.com/wellle/5783452/raw/b7b02012331575f646b5bb09246329947ae7eb44/gistfile1.txt
--
--
You received this message from the "vim_dev" maillist.
Do not top-p
I attached a yaml file as example. Please open it with vim to test the
highlighting speed. Scolling and searching is very slow. Tested on vim 7.3.1106
--
--
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 infor
2013/6/4 Kazunobu Kuriyama
> On Jun 5, 2013, at 3:41 AM, Christian Wellenbrock <
> christian.wellenbr...@gmail.com> wrote:
>
> >
> > Yes the update fixed the problems. You saved it with Windows line
> endings again though.
>
> I apologize to you for getting
s you pointed out, at least for the given part
> of the code.
>
>
>
> KK
>
>
>
> On Jun 4, 2013, at 11:51 PM, Christian Wellenbrock wrote:
>
> >
>
> > I quickly scrolled over some AFNetworking sources [1]. I like the
> > highlighting of
On Tuesday, June 4, 2013 4:33:11 PM UTC+2, Christian Wellenbrock wrote:
> On Tuesday, June 4, 2013 4:27:49 PM UTC+2, David Fishburn wrote:
>
> > ...>
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > > "
On Tuesday, June 4, 2013 4:27:49 PM UTC+2, David Fishburn wrote:
> ...>
>
>
>
>
>
>
> > "AdjustIo.h" 81L, 2743C
>
> > Error detected while processing /usr/share/vim/vim73/syntax/objc.vim:
>
> > line 6:
>
> > E492: Not an editor command: ^M
>
> > line 8:
>
> > E15: Invalid expressio
On Tuesday, June 4, 2013 3:12:20 PM UTC+2, Kazunobu Kuriyama wrote:
> Hi,
>
>
>
> I'm the maintainer of the Objective-C syntax file, syntax/objc.vim. As the
> new features that have been added to the language for years appear to become
> stable and have passed the point of no return (really?)
enaar
>
> Christian Wellenbrock wrote:
>
> > Hi vim_dev,
> >
> > I recently noticed the following inconsistency regarding the 'fillchars'
> and 'statusline options:
> >
> > - multi-byte 'fillchars' work with default
On Monday, June 3, 2013 12:25:50 PM UTC+2, mattn wrote:
> On Monday, June 3, 2013 6:01:47 PM UTC+9, Christian Wellenbrock wrote:
> > I have not tried using it with double width characters. The original intent
> > was to support single width multi-byte characters. I don't know
On Monday, June 3, 2013 9:29:03 AM UTC+2, mattn wrote:
> On Monday, June 3, 2013 7:33:39 AM UTC+9, Christian Wellenbrock wrote:
>
> > I recently noticed the following inconsistency regarding the 'fillchars'
> > and 'statusline options:
>
> >
>
Hi vim_dev,
I recently noticed the following inconsistency regarding the 'fillchars' and
'statusline options:
- multi-byte 'fillchars' work with default 'statusline':
vim -u NONE -c "set ls=2 fcs=stl:●"
[No Name] [+]●●
- single-byte 'fillchars' work with
39 matches
Mail list logo