Re: Google Code shuts down

[Will Fiveash]

On Fri, Mar 13, 2015 at 10:08:09AM -0700, Manuel Ortega wrote:
> There are a lot of people saying "Github is better than Bitbucket for reasons 
> XYZ, therefore we should move to Github".
> 
> The problem is that moving to Github means Bram and the rest of us have to 
> switch to git.  The problem here is not git itself, but the switching.  The 
> path of minimum modification, and minimum risk of messing something up, is to 
> just go to some host that supports mercurial.
> 
> The fact that someone has a Vim clone on GH already is irrelevant.  Bram 
> would still have to learn how to use git and make his rookie mistakes (which 
> would affect all of us).  Even if Bram makes no mistakes, the rest of us who 
> barely know how to "git pull" would still have our workflows messed up, and 
> have to make our own rookie mistakes.[1]
> 
> OTOH, all of us already know enough about Hg to get by, and the whole thing 
> could be solved in five minutes by creating a BB (or wherever) account and 
> then nobody has to change anything except the URL for the repo.

++.  Seems to me that moving vim to another source repo host should be
done in phases.  First, move the vim repo to a host that supports
Mercurial which limits the issues to those specific to the new host (say
Bitbucket).  Then after things are stable and if it seems worth the
effort should vim be migrated to a different type of version control.

-- 
Will Fiveash
Oracle Solaris Software Engineer

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: minor issue with c.vim

[Will Fiveash]

On Fri, Aug 22, 2014 at 01:30:26PM +0200, Bram Moolenaar wrote:
> 
> Will Fiveash wrote:
> 
> > The C syntax file doesn't appear to handle this properly (the {} braces
> > are highlighted in red which isn't correct):
> > 
> > #define ALIGNOF(_t)  offsetof(struct { char c; _t _m; }, _m)
> 
> See ":he c.vim".  Most likely you want to set c_no_curly_error.

Thanks, I was unaware of that option.

-- 
Will Fiveash
Oracle Solaris Software Engineer

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

minor issue with c.vim

[Will Fiveash]

The C syntax file doesn't appear to handle this properly (the {} braces
are highlighted in red which isn't correct):

#define ALIGNOF(_t)  offsetof(struct { char c; _t _m; }, _m)

I'm running very current vim (changeset: 6146:7af530381fec) with c.vim at this
changeset:

 changeset:   5968:92751673cc37
 user:Bram Moolenaar 
 date:Thu Jun 12 21:46:14 2014 +0200
 description:
Update runtime files.

-- 
Will Fiveash

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

small sh.vim patch

[Will Fiveash]

Attached is a tiny patch to update sh.vim to support ksh93's ${!var[*]}
associative array index key list dereference syntax.
Basically, if foo is an associative array, print ${!foo[*]} would output
all the index keys associated with foo.

-- 
Will Fiveash
Oracle Solaris Software Engineer

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/runtime/syntax/sh.vim b/runtime/syntax/sh.vim
--- a/runtime/syntax/sh.vim
+++ b/runtime/syntax/sh.vim
@@ -438,6 +438,12 @@
  syn region shDerefmatchgroup=PreProc start="\${\$\$" end="}"  
contains=@shDerefList
 endif
 
+" ksh: ${!var[*]} array index list syntax: {{{1
+" 
+if exists("b:is_kornshell")
+ syn region shDerefmatchgroup=PreProc start="\${!" end="}" 
contains=@shDerefVarArray
+endif
+
 " bash: ${!prefix*} and ${#parameter}: {{{1
 " 
 if exists("b:is_bash")