.vim
Thus, I really don't think this should be failing.
I also tried using the latest MacVim and console vim on Mac OS X 10.9, and I
also tried Cygwin console vim on the same Windows 8.1 system, and none of those
failed.
Thanks!
Ben
--
--
You received this message from the "vim_d
Just had a feature idea, thought I'd throw it out here.
It would be nice if you could specify the various ++opt options to instruct vim
how to interpret the bytestreams of files opened right from the command-line.
Currently the only way to use ++opt options is when calling :edit or :read (as
fa
either; should we include a preprocessor
test to exclude the code if compiling for GUI mode?
3. I'm not sure about how much testing needs to be done for a new
patch (this is the first patch I've ever submitted); I've only tested
it on one Windows 7 machine.
Any feedback is appreciated
On Dec 26, 1:16 am, Tony Mechelynck
wrote:
> On 26/12/11 06:37, Ben wrote:
>
> > Hi vim_dev,
>
> > I always liked the feature in win32 console vim where the cursor
> > changed shape depending on what mode you're in. I recently switched to
> > using cygwin con
On Dec 26, 9:47 pm, Tony Mechelynck
wrote:
> On 26/12/11 19:22, Ben wrote:
>
> > On Dec 26, 1:16 am, Tony Mechelynck
> > wrote:
> >> On 26/12/11 06:37, Ben wrote:
>
> >>> Hi vim_dev,
>
> >>> I always liked the feature in win32 console v
7;t a very helpful
answer, but it's an experience I had, so I guess it's a possible avenue
to explore...
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the &qu
o Vim--perhaps even to be available only when
'encoding=utf8', which would be better than nothing!
Could someone with a bit of experience with the Vim codebase and
development process give me some pointers/advice?
Ben.
Send instant messages to your online friends http://au.messenger
sn't compile for Mac out of the
box rather than having these different distributions?
> Well, if I understand you correctly, this already does work. I didn't
> test with a different encoding, I don't see a reason for not using
nyone got any ideas? Or is this not worth pursuing?
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
e, and ideally it would work with the Mac clipboard.
Cheers,
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
oubly defined? Does it
need some conditional compilation #ifdefs, and if so, what? Or would you
just remove the MacVim clipboard support if the other worked without the
GUI?
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~
> Ideally the colors would be mixed, but that's quite difficult (and
> impossible in a terminal).
>
> --
>
> Nothing is impossible for the man who doesn't have to do it.
> /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
LOL.
Ben.
te like that, though there is the :bufdo
command.
I suspect it would be easiest to use the functionality of :vimgrep to do the
searching, provided your files are all in the same directory or something
similarly convenient. Your recording would just use :cn rather than just n to
jump
to
;
>> :bufdo vimgrep /re/ %
>>
>> But it has few downsides: matches for all files will be saved into
>> separated quickfix lists, Vim will remember only last ten lists.
You should be able to join them together by doing
:bufdo vimgrepadd /re/ %
shouldn't you?
Need to cle
ility for the 'lambda user' might be a 'naive user'.
Your English is extremely good, Tony. It took quite a few of your posts before
I
realised it wasn't your native tongue, and even then, I'm not sure it was the
English that gave the game away!
Ben.
Send instan
ables. Most commands do not take
variables/expressions as input directly but need to be constructed using the
:exe command. I don't see any good reason why :catch should differ.
Regards,
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~
erent for Cygwin and native Windows, etc.
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
That could be handy on Windows, too, but I don't know
what
hoops you might need to go through to reliably find other users' directories!
> Vim-for-Cygwin is a Unix-like build, the shell handles the tilde. This thread
> is only busy with native-window at this point.
O yes,
to moving the clipboard support and providing more details on the
trouble with right-to-left stuff later.
Cheers,
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
older with the name of the zip for you.
Ah, right. Will it do so even if there is a single item? 'Cause if it doesn't
then
you could have the best of both worlds packaging differently. If it still
creates
an extra folder anyway, though, then yeah, it would be a nuisance, understood
ht be related to 'tenc' to, I suppose. What's that set to for you?
It works fine for me with Hebrew characters and enc=tenc=utf8.
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You re
lly,
but I
guess you get the gist.)
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
verything else to be pushed backward by the 'showbreak' string as well.
If I have some time, I'll have a look at this, but don't expect I will for at
least a week!
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
bug in a particular version, system or GUI!
Which version/system/GUI are you using?
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
help clientserver
for a start. Once you can get Vim itself to do what you need, you should be
able
to make something else. E.g. find the code that implements the --remote-send
option and integrate it into your application.
Smiles,
Ben.
Send instant messages to y
do that if you are unsure, though it looks like you're
pretty savvy. I thought this was worth mentioning as this is how the whole
thread
started!
Cheers,
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ts of mine) but in both cases fenc will be unset. It will fall back to enc
when
the file is written, but gives no indication of how stdin was read. I think this
is another bug. CCing vim_dev again.
Bug: When reading stdin, fenc is not set (including when the encoding used to
read
stdin was differen
disk, using
fencs.
I wonder if this behaviour could be platform-specific or depend on which
libraries
are available/compiled in. Because we both seem to have solutions, but neither
of
them works for the other person.
H.
Ben.
Send instant messages to your online friends http://au.m
uence after the next
read(). Solution: Check partial sequences for validity.
Ben.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.o
matches = add(l:matches, l:curmatch)
let l:matchnum = l:matchnum + 1
let l:curmatch = matchstr(a:subject, a:pattern, 0, l:matchnum)
endwhile
return l:matches
endfunction
E.g.
:echo ListOfMatches("abracadabra","a.")
['ab',
> Still buggy:
> :echo SplitMatch("aba", ".*")
> ['aba', '']
Looks OK to me.
Maybe you wanted
:echo SplitMatch("aba", '.\+')
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
o, I haven't tested much. Testing and consequent feedback from others would
be
worthwhile. There may be issues with things not being escaped which should be,
etc.
Ben.
--~--~-~--~~~---~--~~
You received this m
ns).
And I ignored the case of literal entry in insert mode, which I shouldn't have.
So
a bit of work to do there still, too.
I should have done this one while a bit less rushed! My coding isn't usually
this
poor...honest...
Ben.
Send inst
think?
Also, I haven't tested much. Testing and consequent feedback from others would
be
worthwhile. There may be issues with things not being escaped which should be,
etc.
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
--~--~-~--~~--
scaped which should
> be, etc.
My apologies; that was a poor patch. And I thought I'd tested @, but trying it
again showed it didn't work. I have now made sure it doesn't work. The .
command
is for that purpose, and implementing it isn't trivial!
Revised more robust pat
On Tuesday, July 29, 2014 3:10:56 PM UTC-5, Tim Brosnan wrote:
> I initially send a version of this message through the google groups
> interface, but it seems to have disappeared. Apologies if there is
> duplication.
>
> When going through some regex examples from
> VimRegexTutor(https://githu
On Wednesday, July 30, 2014 6:58:11 AM UTC-5, Ingo Karkat wrote:
> > It's a suprise it works at all. Probably because in the old regex
>
> > engine the "\@<=" part is used only after finding a match for the
>
> > rest.
>
> >
>
The help for /\@<= pretty explicitly says it should work this way
On Thursday, July 31, 2014 4:46:22 AM UTC-5, Paul Moore wrote:
> On Windows, Vim does not correctly display international characters. To
> demonstrate this, create a file in UTF-8 encoding with the Unicode characters
> \x5000 \x5001 \x5002 in it. These should display as Chinese chacaters.
>
> W
On Thursday, July 31, 2014 8:30:36 AM UTC-5, Paul Moore wrote:
> On Thursday, 31 July 2014 14:08:16 UTC+1, Ben Fritz wrote:
> > I don't see this problem.
> [...]
> > I entered unicode characters 5000, 5001, and 5002 which you say are Chinese
> > characters, by press
On Tuesday, August 26, 2014 12:20:44 AM UTC-5, mattn wrote:
> Hi list.
>
> When vim allocate many objects, some times vim hang for GC. Ariya Mizutani
> suggested below's patch.
>
> https://gist.github.com/mattn/0c58a7398c63ab4c3066
>
> Try following test code.
>
On Friday, August 29, 2014 8:12:34 PM UTC-5, James McCoy wrote:
> On Fri, Aug 29, 2014 at 11:58:09AM +0200, Bram Moolenaar wrote:
>
> >
>
> > Patch 7.4.421
>
> > Problem:Crash when searching for "\ze*". (Urtica Dioica)
>
> > Solution: Disallow a multi after \ze and \zs.
>
>
>
> This n
On Saturday, August 30, 2014 11:10:49 AM UTC-5, Bram Moolenaar wrote:
> Ben Fritz wrote:
>
>
> > I'm pretty sure \ze* should be an invalid pattern, not match everything.
>
>
>
> Yes, that's what I thought. So we could also change the old engine.
>
On Tuesday, September 16, 2014 6:04:41 AM UTC-5, Marslo Jiao wrote:
> Because of some reason, the .vimrc file and .vim folder has been saved in the
> specified location:
> - .vimrc: ~/.marslo/.vimrc
> - .vim: ~/.marslo/.vim/
> - colorscheme is marslo256.vim (made by myself):
> ~/.marslo/.vim/bund
On Friday, September 12, 2014 8:01:50 PM UTC-5, Ben Fritz wrote:
> On Fri, Sep 12, 2014 at 11:06 AM, Bram Moolenaar wrote:
> >
> > Thanks, I'll put it in the todo list. I'll await comments for a little
> > while.
>
>
> I'll try to test it with TOhtm
On Thursday, September 18, 2014 3:25:39 PM UTC-5, s.sel...@gmail.com wrote:
>
> Proposed patch will prevent redrawing when sign without text or image was
> placed.
>
Signs can also define a background color for an entire line, without defining
an image or text. For example, in the past I used
On Friday, September 26, 2014 1:40:36 PM UTC-5, v...@googlecode.com wrote:
>
> What steps will reproduce the problem?
>
> 1. set showbreak=↪ " character show when wrapping line
>
> 2.
>
> 3.
>
>
>
> What is the expected output? What do you see instead?
>
> Previously i see the "↪" escape ch
I see in :help 'columns':
Vim limits the number of columns to
what fits on the screen. You can use this command to get the widest
window possible:
:set columns=
Minimum value is 12, maximum value is 1.
This is all well and good...except that I have
On Thursday, October 2, 2014 11:58:26 AM UTC-5, Christian Brabandt wrote:
>
>
> But Erik asked for something like to undo the abbreviation. To the best
>
> of my knowledge there is not (and there is even a todo list entry :h
>
> todo and search for abbreviation).
>
>
>
> Perhaps it would
On Tuesday, October 14, 2014 9:40:09 AM UTC-5, nikolavp wrote:
> I found the following issue with vimdiff. I want to %diffput the left
>
> hand side from vimdiff to the right hand side. This has the side effect
>
> of adding 1 additional blank line which is a problem for the workflow I
>
> am cu
On Monday, October 27, 2014 7:00:22 PM UTC-5, Eelis wrote:
> On 2008-05-10 22:16, Bram Moolenaar wrote:
> >
> > Gary Johnson wrote:
> >
> >> I just discovered that the parenthesis matching the one the cursor
> >> is on is not highlighted if it was initially off-screen and is
> >> brought on-screen
On Sunday, November 9, 2014 11:53:38 AM UTC-6, Eric Christopherson wrote:
> On Thu, Nov 06, 2014, Ben Fritz wrote:
> >
> > if exists('+relativenumber')
> > nnoremap CycleLNum()
> > xnoremap CycleLNum()
> > onoremap CycleLNum()
> >
&
On Monday, November 10, 2014 10:25:55 AM UTC-6, Christian Brabandt wrote:
> Am 2014-11-10 14:51, schrieb Ben Fritz:
> > I've noticed this myself over the last few years I've been using the
> > mapping. Especially this is apparent in operator-pending mode. It
> > loo
On Monday, November 10, 2014 12:41:06 PM UTC-6, Christian Brabandt wrote:
> Hi Ben!
>
> On Mo, 10 Nov 2014, Ben Fritz wrote:
>
> > On Monday, November 10, 2014 10:25:55 AM UTC-6, Christian Brabandt wrote:
> > > Am 2014-11-10 14:51, schrieb Ben Fritz:
> > >
On Friday, November 14, 2014 3:22:19 AM UTC-6, Emanuel Palm wrote:
> Hey!
>
> So, I was thinking about the Vim Logo. The Logo really has most of the
> characteristics of a good logo. It's unique, its distinguishable, its clear,
> etc.
>
> But I thought it was lacking one thing.
>
> An open sou
On Thursday, December 4, 2014 3:51:05 PM UTC-6, John Whitley wrote:
> ### Repro steps
>
> 1. From this gist[1], download the files `killvimrc` and `longline.rb`.
> 2. Run vim with `vim -u killvimrc longline.rb`.
>
> ### Actual results
>
> `vim` locks up at 100% CPU utilization and must be kill
On Tuesday, December 16, 2014 9:49:48 AM UTC-6, Ingo Karkat wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 16-Dec-2014 14:30, Axel Bender wrote:
> > Using autochdir in .vimrc together with the --remote-silent start
> > option works fine: the first edited file's path is set correct
On Wednesday, December 17, 2014 10:38:50 AM UTC-6, Bram Moolenaar wrote:
>
> This is one of those options that changes the behavior of Vim in a way
> that many things work differently. I do want to discourage users from
> setting it.
>
> Indeed, many plugins have been fixed. That means they wer
On Friday, January 16, 2015 at 4:55:44 PM UTC-6, Christian Brabandt wrote:
> Hi Bram!
>
> On Fr, 16 Jan 2015, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote:
> > > Hm, we already have special cases and
> > > to move by word|WORD. So how about making and move
> > > without breakin
On Saturday, January 17, 2015 at 1:20:04 PM UTC-6, Bram Moolenaar wrote:
>
> Since undo works by saving the line before changing it, restricting the
> "keep undo" modifier to only work when the cursor remains in the same
> line should work. It's also fairly easy to understand, instead of
> making
On Wednesday, January 21, 2015 at 1:33:35 PM UTC-6, Tim Lebedkov wrote:
> > For a beginning, you could maintain a separate installer so that people
> > can actually try that it works and you get feedback. Then you can also
> > gradually change further things, if this is required.
>
> I did, but
On Sunday, June 22, 2014 at 3:29:32 PM UTC-5, Ben Fritz wrote:
> The attached patch seems to fix the crash reported here:
>
> https://groups.google.com/d/topic/vim_dev/Nr8Ja4Zjghw/discussion
>
> The fix is simple in concept: any recursive call can be replaced with
> an explic
On Wednesday, January 21, 2015 at 8:00:27 PM UTC-6, James McCoy wrote:
> On Wed, Jan 21, 2015 at 02:32:29PM -0800, Sergey Vlasov wrote:
> > Since around last year I experience very frequent vim crashes. This is
> > caused by Lua written plugin neocomplete.vim. Plugin's author reply
> > was: "Vim pl
On Thursday, January 22, 2015 at 10:11:40 AM UTC-6, ZyX wrote:
> 2015-01-21 23:02 GMT+03:00 Ben Fritz :
> >
> > Many open-source projects do not accept major new features or
> > potentially breaking changes except at minor or major version
> > updates. Vim is the same
Trying on Windows 7 64-bit with 64-bit HUGE Vim 7.4.522 shows it taking a
REALLY long time just to match "1234567890" (one line in the buffer) with
pattern ".\{1,8000}".
Furthermore, I can't seem to interrupt the search with , and I get a
"search hit BOTTOM, continuing at TOP" message before it
On Saturday, January 31, 2015 at 4:33:24 PM UTC-6, Christian Brabandt wrote:
> Hi Benjamin!
>
> On Do, 29 Jan 2015, Benjamin Fritz wrote:
> > Removing the "set linebreak" line from test.vim shows:
> >
> > ee<---<-; >
> > Note there are extra '-' characters added for listchars, and they are t
On Tuesday, February 3, 2015 at 6:16:26 AM UTC-6, Bram Moolenaar wrote:
> Patch 7.4.611 (after 7.4.609)
> Problem:Syntax error.
> Solution: Change statement to return.
> Files:src/if_python3.c
>
>
> *** ../vim-7.4.610/src/if_python3.c 2015-02-03 12:55:11.140179551 +0100
> ---
On Tuesday, February 3, 2015 at 3:14:13 PM UTC-6, Ozaki Kiichi wrote:
> This patch drops "return 0;" from luaV_setref (if_lua.c:1549) against
> return-type.
> Its change seems to cause trouble with lua, especially luajit.
>
> Actually I encountered SEGV problem;
>
> [environment]
> * vim +lua wi
On Wednesday, February 4, 2015 at 6:48:45 AM UTC-6, Tony Mechelynck wrote:
> Sorry if this has already been reported, I'm very far behind reading mail due
> to computer slowness (computer won't stay up unless I set "Fan: silent (but
> may reduce CPU performance)" in the BIOS, and this makes it *v
On Wednesday, February 4, 2015 at 5:44:21 AM UTC-6, Yukihiro Nakadaira wrote:
> On Wed, Feb 4, 2015 at 7:11 AM, Bram Moolenaar wrote:
>
>
> Patch 7.4.618 (after 7.4.609)
>
> Problem: luaV_setref() is missing a return statement. (Ozaki Kiichi)
>
> Solution: Put the return statement back.
>
On Friday, February 6, 2015 at 11:38:17 AM UTC-6, itchyny wrote:
> The option 'incsearch' just jumps to the first matching place and highlights
> it.
> We then press enter, all the matches are get highlighted (if we set hlsearch
> on).
> If Vim highlights all the matching strings, it would be nic
On Tuesday, February 10, 2015 at 3:57:57 PM UTC-6, v...@googlecode.com wrote:
> Comment #10 on issue 326 by fmerci...@gmail.com: filetype plugin not loaded
> when file opened from within vim rather than from command line
> https://code.google.com/p/vim/issues/detail?id=326
>
> Interestingly enou
On Friday, February 13, 2015 at 4:03:48 PM UTC-6, Christian Brabandt wrote:
>
> Finally, I could debug this. Here is the patch, including a test.
>
I confirm this seems to fix both issues (too much text hidden, and fillchars
drawing in the wrong color), in both the test file and in the actual f
On Monday, February 16, 2015 at 11:30:05 AM UTC-6, Ben Fritz wrote:
> On Friday, February 13, 2015 at 4:03:48 PM UTC-6, Christian Brabandt wrote:
> >
> > Finally, I could debug this. Here is the patch, including a test.
> >
>
> I confirm this seems to fix both issues
On Tuesday, February 17, 2015 at 9:54:00 AM UTC-6, Christian Brabandt wrote:
> Hi Ben!
>
> On Mo, 16 Feb 2015, Ben Fritz wrote:
>
> > On Monday, February 16, 2015 at 11:30:05 AM UTC-6, Ben Fritz wrote:
> > > On Friday, February 13, 2015 at 4:03:48 PM UTC-6, Chri
On Thursday, February 26, 2015 at 6:59:22 AM UTC-6, Don wrote:
> Running gvim 7.4.591 on a FreeBSD 10.1 system (or 7.4.617 on an
> up-to-date Arch Linux system), I attempt to reduce the font size
> (using Edit->Set font) from the default 10-point Monospace to
> 8-points, for the purpose of getting
On Thursday, March 12, 2015 at 12:46:32 PM UTC-5, Gary Johnson wrote:
> On 2015-03-12, zeug wrote:
> > Am 2015-03-12 18:27, schrieb Bruno Sutic:
> >
> > >Any thoughts on where will vim source code repo be moved?
> > >I know I'd be more than delighted if it was hosted on Github.
> >
> > Bitbucket
On Thursday, March 12, 2015 at 3:27:43 PM UTC-5, ewfalor wrote:
>
> I just signed up for a Bitbucket account, and all of the new-user
> tutorials I'm presented with encourage me to start a git repo. In
> fact, I've only seen Mercurial mentioned once so far. Is Bitbucket
> leaning towards git now,
On Friday, March 13, 2015 at 2:57:04 AM UTC-5, Fredrik Gustafsson wrote:
> On Thu, Mar 12, 2015 at 02:38:23PM -0700, Ben Fritz wrote:
> > And, Mercurial is a tool that makes it very hard to shoot yourself in
> > the foot. Git makes it very easy to lose data permanently, even when
&
I read somewhat recently about Kiln, which gives one front-end that lets you
use *either* Hg or git with:
http://blog.fogcreek.com/announcing-kiln-harmony-the-future-of-dvcs/
They seem to imply they may be flexible on the number of users for open-source
projects
(http://blog.fogcreek.com/share
On Friday, March 20, 2015 at 7:00:21 AM UTC-5, Bram Moolenaar wrote:
>
> Are you able to get a stack trace of the crash? Or even better, have it
> crash in a debugger?
>
Sure will!
...as soon as I can figure out how to force ctags to parse those stupid *.pro
files along with the rest of the co
On Friday, March 20, 2015 at 8:39:19 PM UTC-5, Ben Fritz wrote:
> On Friday, March 20, 2015 at 7:00:21 AM UTC-5, Bram Moolenaar wrote:
> >
> > Are you able to get a stack trace of the crash? Or even better, have it
> > crash in a debugger?
> >
>
> Sure will!
&g
On Wednesday, March 25, 2015 at 10:21:41 AM UTC-5, Bruno Sutic wrote:
> I'm curious, when a switch is made, will Github's "pull request" feature be
> used? Or will code contributions still be done with patches via mailing list?
>
> I'd guess a move to "pull request" workflow will be done since it
On Wednesday, January 21, 2015 at 11:06:53 AM UTC-6, Ben Fritz wrote:
> On Saturday, January 17, 2015 at 1:20:04 PM UTC-6, Bram Moolenaar wrote:
> >
> > Since undo works by saving the line before changing it, restricting the
> > "keep undo" modifier to only work
On Wednesday, March 25, 2015 at 12:18:46 PM UTC-5, LCD 47 wrote:
> On 25 March 2015, Ben Fritz wrote:
> > On Wednesday, March 25, 2015 at 10:21:41 AM UTC-5, Bruno Sutic wrote:
> > > I'm curious, when a switch is made, will Github's "pull request"
> > &
On Wednesday, March 25, 2015 at 3:35:21 PM UTC-5, Martin Lundberg wrote:
> Not sure if I'm missing something but to organize multiple repositories all
> you have to do is to create a Github organization described here
> https://help.github.com/articles/creating-a-new-organization-account/
You're
On Tuesday, March 24, 2015 at 4:36:32 PM UTC-5, Bram Moolenaar wrote:
>
> Look here: https://github.com/vim
>
> Please respond to the list if something doesn't work well.
>
When I click the "branches" tab I get a Unicorn! error page saying "This page
is taking way too long to load."
Somehow I
I'd just like to point out that all you githeads arguing over the various
different options on pull and fetch and whether they break or keep your
repository intact, are making me VERY sad about losing Mercurial.
Bram, is there a chance you'd be willing to also push to a Mercurial mirror
using o
On Friday, March 27, 2015 at 11:28:42 AM UTC-5, Christian Brabandt wrote:
>
> If I have understood correctly, it's easy enough to setup a mirror
> somewhere else. If that is straightforward, I could set it up for github
> to mirror somewhere else (bitbucket?)
>
Yes, it's pretty easy to set up
On Friday, March 27, 2015 at 1:21:48 PM UTC-5, James McCoy wrote:
> Why should this be different than any other open source project? If
> you want to contribute, you need to learn the tools that are being
> used. When tools change, then something different needs to be learned.
> It's not up to the
On Friday, March 27, 2015 at 4:06:47 PM UTC-5, Bruno Sutic wrote:
> - lastly, it has been mentioned a couple times vim plugin community is
> already on github. The objective statement that proves this: github
> currently has 42,636 vim related repositories, bitbucket has only 1652
> (this is based
On Sunday, March 29, 2015 at 2:27:56 PM UTC-5, Bruno Sutic wrote:
> Hi all,
> in "Preparations for moving to github" thread Bram said it would be a good
> idea to update the following pages:
>
> - http://www.vim.org/develop.php
> - http://www.vim.org/mercurial.php
>
> And also create a new page
I'm not sure why everyone seems to think the Vim development process is going
to change drastically just because Bram is moving Vim to Github. A lot of that
stuff you're daydreaming about is also possible with Mercurial, and Bram has
resisted significant changes there for a long time. Although I
One sanity check, from within Vim, make sure your python paths match what you
expect from your earlier test in your shell:
:!where python27.dll
Next step, maybe install a more recent python?
Yours just shows "Python 2.7" whereas mine (which has been working fine for a
long time) shows "Pyt
On Wednesday, April 8, 2015 at 9:47:30 AM UTC-5, Testipation Testo wrote:
> Hi,
> I would like to use vim in a new platform. Is there any way, skeleton or
> tutorial to learn how to create a new GUI for vim ?
I don't think there is such a tutorial (I'd love to be proven wrong) but I'm
curious: w
On Friday, April 10, 2015 at 11:02:55 AM UTC-5, tux. wrote:
> There's a Bitbucket mirror? Hmm, wouldn't it be easier to just change the
> upstream URL then? Or is that impossible?
It's not the same repository, so no you can't just change the URL.
IIUC the GitHub repository is the result of some
On Saturday, April 11, 2015 at 12:22:07 PM UTC-5, m wrote:
> In blowfish.c,
>
> The args src and dest to mch_memmove reversed from
> the convention used by memmove, so code is zeroing out sbx_init
> instead of initializing bfs->sbx
>
> Reverse the src and dest in this line to fix the code.
>
>
On Tuesday, April 14, 2015 at 10:43:11 AM UTC-5, Thiago Arruda wrote:
> > It's easy to accidentally make a Vim script that consumes all
> memory.
>
> If you see this often then you must be running Vim on a machine with
> an extremely low amount of memory. This is not the case for most users
> tho
On Wednesday, April 29, 2015 at 11:06:20 AM UTC-5, mattn wrote:
> call s:foo_func("\%(foo\)")
> call s:foo_func('\%(foo\)')
>
> When type "vi(" on '%' in above, it should select like below.
>
> http://go-gyazo.appspot.com/ce98f67480ace7b0.png
>
> but not selected in latest of vim.
I can confir
On Thursday, April 30, 2015 at 2:27:30 AM UTC-5, mattn wrote:
> >
> > You lost me here. I would either expect this to select "foo\", or if it's
> > smart, to do the same as before and select just the outer parenthesis.
> > Neither happens. In the first line (double quote case) nothing at all
>
On Thursday, April 30, 2015 at 9:17:33 AM UTC-5, Ben Fritz wrote:
> On Thursday, April 30, 2015 at 2:27:30 AM UTC-5, mattn wrote:
> > >
> > > You lost me here. I would either expect this to select "foo\", or if it's
> > > smart, to do the same as
1 - 100 of 1064 matches
Mail list logo
