On 17-May-2011 03:42, hari.rangara...@gmail.com wrote:
For the record, I have gone through the solutions at this wiki:
http://vim.wikia.com/wiki/Moving_through_camel_case_words; however, I
was still left wondering if there has been an attempt to solve the
camel case word movement natively in
Can't we make Vim accept custom moves then?
then dX vX =X etc would work where X is the custom vimL code moving the
cursor?
Something like
:setlocal custommovement=camelcase#CamelCaseMovement
What about regions ? Does something like this already exist for
regions?
What's the main point
On 17-May-2011 10:33, Marc Weber wrote:
Can't we make Vim accept custom moves then?
then dX vX =X etc would work where X is the custom vimL code moving the
cursor?
Something like
:setlocal custommovement=camelcase#CamelCaseMovement
And this new setting would affect the word-wise
You can already implement custom motions via :omap; that's what
camelcasemotion
uses.
I've missed that. The first camelcase samples are using (i,n,v)noremap
I think there are many good syncing solutions already out there, and
especially
non-Windows users have a need for keeping several
On Sun, 15 May 2011 20:18:18 +1000
Ben Schmidt mail_ben_schm...@yahoo.com.au wrote:
I have tracked it down now.
That's great, as it's one of the few things keeping me from finishing
my awesome syntax file for shell scripts ;)
Bad news is that I've found another bug in the syntax engine, this
On Mon, May 16, 2011 at 11:36 PM, Ingo Karkat sw...@ingo-karkat.de wrote:
On 17-May-2011 03:42, hari.rangara...@gmail.com wrote:
For the record, I have gone through the solutions at this wiki:
http://vim.wikia.com/wiki/Moving_through_camel_case_words; however, I
was still left wondering if
What's the main point about being native? That you don't have to get
custom .vimrc ?
For me, that would be:
- available everywhere, and therefore:
- beneficial to all users (who are more likely to find the feature in the
help
than in one of thousands of plugins on vim.org which need to
Another strange behavior of syntax engine. Though it occurs only when
there's at least one syntax group with 'containedin=' attribute, it
affects even completely unrelated syntax items. As before, I feel that
an example will explain it best.
--
You received this message from the vim_dev
On 17-May-2011 17:07, hari.rangara...@gmail.com wrote:
Ingo -- I did check out your plugin, and I might actually end up using
it regularly :). There were a basic things which caught my eye as
incomplete: Is there a reason you didn't choose to implement the 'ge'
operator?
[code snipped]
Gary Johnson wrote:
This patch addresses some documentation issues raised in the vim_use
thread, 'indentexpr and = operator'. It adds references to 'lisp'
and Lisp indenting to the 'indentexpr' and = help topics.
Thanks!
--
% cat /usr/include/life.h
void life(void);
/// Bram Moolenaar
On 18/05/11 1:50 AM, Radek wrote:
Another strange behavior of syntax engine. Though it occurs only when
there's at least one syntax group with 'containedin=' attribute, it
affects even completely unrelated syntax items. As before, I feel that
an example will explain it best.
Found it. Not sure
The other question is whether a sizeable population works on camelcase
code and would like to have this solved :).
I would like to see a camelcase and/or underscore-seperation movement
commands. But I think if done, it has to be done really carefully so it
doesn't end up using obscure keys or
I've uploaded release 0.9 of my patch for Vim NSIS installer to
github:
https://github.com/gpwen/vim-installer-mui2/wiki
The following new features have been added since v0.8:
- New language support
Dutch language support by Peter Odding
Italian language support by Antonio Colombo
-
/tmp$ mkdir -p tmp
/tmp$ gvim .
I open the directory tmp by the above commands. (/tmp is the current
dir). Then I see a number of directories gvim. Then I select tmp/ in
gvim and press ctrl+W ctrl+F. Instead of going to /tmp/tmp, I get /tmp
reopened.
I think the correct behavior should be
Guopeng Wen schrob am 18.05.2011 03:02:
The new installer also intended to add multiple language support to
the Vim Windows installer, you can help to translate messages to
your own language
While browsing through the german.nsi file again (just for the fun of
it), I noticed 'nother typo.
On Wed, May 18, 2011 at 10:01 AM, tux. der_tux...@arcor.de wrote:
Guopeng Wen schrob am 18.05.2011 03:02:
The new installer also intended to add multiple language support to
the Vim Windows installer, you can help to translate messages to
your own language
While browsing through the
On Wed, May 18, 2011 at 9:02 AM, Guopeng Wen wenguop...@gmail.com wrote:
I've uploaded release 0.9 of my patch for Vim NSIS installer to
github:
https://github.com/gpwen/vim-installer-mui2/wiki
The following new features have been added since v0.8:
- New language support
Dutch language
On 18 May 2011 03:02, Guopeng Wen wenguop...@gmail.com wrote:
I've uploaded release 0.9 of my patch for Vim NSIS installer to
github:
https://github.com/gpwen/vim-installer-mui2/wiki
The following new features have been added since v0.8:
- New language support
Dutch language support by
On 18/05/11 1:50 AM, Radek wrote:
Another strange behavior of syntax engine. Though it occurs only when
there's at least one syntax group with 'containedin=' attribute, it
affects even completely unrelated syntax items. As before, I feel that
an example will explain it best.
The patch below
19 matches
Mail list logo
