leo barbosa.leona...@gmail.com a écrit:
Hi,
Is there a way of prioritize the listed files by their extension after a
:etab? I mean, like in zsh completion system?
Not that I know of; 'wildmenu' doesn’t allow custom completion (that
would be a nice feature request).
What you can do is write
On 2013-03-21 12:49, leo wrote:
Is there a way of prioritize the listed files by their extension
after a :etab? I mean, like in zsh completion system?
I don't know how zsh does it, but the 'suffixes' option allows you to
specify extensions of a lower-priority so that they get shown
afterward.
Dear all,
I have been trying to set the TEXINPUTS variable for my latex to have it search
for packages in paths, where I have some custom built macros and styles. I have
therefore added this line in my vimrc:
let g:Tex_TEXINPUTS = '/home/christoph/Dokumente/Dropbox/NuHAG/latex/**,./**'
Hi,
I often need to uncomment or copy a C function and I wonder if
there's a motion for that. What I do at the moment is
[[{v][y
which seems rather verbose and a lot to type for just “copy this
function”. The following does not work for some reason:
[[{y][
The closing brace is missing. I
Marco net...@lavabit.com a écrit:
Hi,
I often need to uncomment or copy a C function and I wonder if
there's a motion for that. What I do at the moment is
[[{v][y
which seems rather verbose and a lot to type for just “copy this
function”.
You can use an omap to do the same (with
On 2013–03–22 Paul Isambert wrote:
You can use an omap to do the same (with linewise visual mode to include the
closing brace):
onoremap af :C-Unormal! [[{V][CR
Then yaf yanks the current function.
This works, thanks. However, this raises more questions:
Why does the following
Marco net...@lavabit.com a écrit:
On 2013–03–22 Paul Isambert wrote:
You can use an omap to do the same (with linewise visual mode to include the
closing brace):
onoremap af :C-Unormal! [[{V][CR
Then yaf yanks the current function.
This works, thanks. However, this raises
On Thu, Mar 21, 2013 at 12:37 PM, Marcin Sztolcman mar...@urzenia.netwrote:
On 21 mar 2013, at 16:55, FlashBurn rail.shafigu...@gmail.com wrote:
I have just loaded tcomment plugin,
https://github.com/tomtom/tcomment_vim. I code in C and need to be able
to do line comments ( // ). For some
Is there any *native* (i.e. not programmed) way to access the column position
of the last match's \zs or \ze?
--
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Hi,
I am not aware how this is implemented in latex-suite, but you can set
the variables in Vim simply by:
:let $TEXINPUTS='/home/user/texmf'
You can see that it works in both Vim and gVim using the following
command:
:!echo $TEXINPUTS
This is how it works in http://atp-vim.sourceforge.net/
On Thursday, March 21, 2013 3:10:14 PM UTC-5, Christian Brabandt wrote:
Hi Ben!
On Do, 21 M�r 2013, Ben Fritz wrote:
On Thursday, March 21, 2013 8:14:03 AM UTC-5, ping wrote:
but looks I just find a new issue (maybe old/known?), this is
reproducible:
if the 2 buffer in
On Friday, March 22, 2013 7:42:41 AM UTC-5, Marco wrote:
Since vim has an understanding of
functions (determined by the outermost brace pair probably) why is
there no built in way to use this information for a motion?
I don't think Vim does have an understanding of functions. It knows about
On Friday, March 22, 2013 8:15:44 AM UTC-5, Axel Bender wrote:
Is there any *native* (i.e. not programmed) way to access the column position
of the last match's \zs or \ze?
You should be able to pass an empty string to the searchpos() function to
re-use the last used search pattern. See :help
@ben
Sorry, I was too unspecific. I want to use the \z[es] from the last match() to
prevent searching for the same - complicated - expression two times (once with
match() the second time with matchend()...).
matchlist() might come to the rescue, but I expect that having access to these
column
On 2013–03–22 Ben Fritz wrote:
I don't think Vim does have an understanding of functions.
You're totally right. But vim has a mechanism to navigate functions,
given they are formatted in a particular way. And that was what I
was referring to.
It knows about { or } in the first column (the [[
The set suffixes indeed order, but it doens't suggest the first
element of the list, which requires me to press tab twice. (I know
that sounds i'm completely lazy...). Perhaps 'set wildignore' is the
best vi can do at this moment.
Thanks anyway.
On Fri, Mar 22, 2013 at 7:23 AM, Tim Chase
On 2013-03-22 13:24, Leonardo Barbosa wrote:
The set suffixes indeed order, but it doens't suggest the first
element of the list, which requires me to press tab twice.
Perhaps you misunderstand the purpose of 'suffixes'? It's a way of
designating less-than-interesting files, so they always
On 13:47 Tue 12 Mar , Marc Weber wrote:
but if the package manager provide a uniform interface to handle this
job. it maybe more better.
If it was a plugin - all package managers could be used ..
1.2 some plugin need python support or set nocompatible，but unless
you
read the
Hi,
I wonder what's the reason why :vimgrep does not honour the gdefault
setting. I mean it's not a bug, the manual only mentions substitute
commands, not vimgrep.
This feels inconsistent to append “g” to vimgrep searches but not
ordinary searches.
Is there a vimgrep equivalent to gdefault?
On Friday, March 22, 2013 10:51:07 AM UTC-5, Axel Bender wrote:
@ben
Sorry, I was too unspecific. I want to use the \z[es] from the last match()
to prevent searching for the same - complicated - expression two times (once
with match() the second time with matchend()...).
matchlist()
I have the following code in my _vimrc
colorscheme xoria256
hi CursorLine gui=underline guibg=NONE term=underline cterm=underline
set cursorline
The issue that I'm having is that it doesn't work when vim is reopened or the
_vimrc is sourced. However if I manually set it using
hi CursorLine
On Friday, March 22, 2013 4:39:14 PM UTC-5, FlashBurn wrote:
I have the following code in my _vimrc
colorscheme xoria256
hi CursorLine gui=underline guibg=NONE term=underline cterm=underline
set cursorline
The issue that I'm having is that it doesn't work when vim is reopened or the
I notice that some settings use the format ':set name=value' and other
use ':name value'. For instance:
:set syntax=php
:syntax off
Can the string 'set ' always be safely elided? If not, then what are
the guidelines?
Thanks.
--
Dotan Cohen
http://gibberish.co.il
http://what-is-what.com
--
Selon FlashBurn rail.shafigu...@gmail.com:
I have the following code in my _vimrc
colorscheme xoria256
hi CursorLine gui=underline guibg=NONE term=underline cterm=underline
set cursorline
The issue that I'm having is that it doesn't work when vim is reopened or the
_vimrc is sourced.
Selon Dotan Cohen dotanco...@gmail.com:
I notice that some settings use the format ':set name=value' and other
use ':name value'. For instance:
:set syntax=php
:syntax off
Note that :syntax php doesn't work.
Can the string 'set ' always be safely elided?
No.
If not, then what are the
On 2013-03-23, Dotan Cohen wrote:
I notice that some settings use the format ':set name=value' and other
use ':name value'. For instance:
:set syntax=php
:syntax off
Can the string 'set ' always be safely elided? If not, then what are
the guidelines?
':name value' is not a setting, it is
Axel Bender wrote:
Sorry, I was too unspecific. I want to use the \z[es] from
the last match() to prevent searching for the same -
complicated - expression two times (once with match() the
second time with matchend()...).
I forget the details, but I sweated blood working out how to
avoid
Thanks for the feedback!
I had hoped that - like in Perl - there is a [(possibly) undocumented] feature
or a trick that lets you extract the start and the end positions (columns)
after a *single* call to match(), using both \zs and \ze.
I would prefer such a solution over having to determine
On Fri, Mar 22, 2013 at 6:18 PM, Ben Fritz fritzophre...@gmail.com wrote:
On Friday, March 22, 2013 4:39:14 PM UTC-5, FlashBurn wrote:
I have the following code in my _vimrc
colorscheme xoria256
hi CursorLine gui=underline guibg=NONE term=underline cterm=underline
set cursorline
On Friday, March 22, 2013 6:45:24 PM UTC-4, Paul Isambert wrote:
I have the following code in my _vimrc
colorscheme xoria256
hi CursorLine gui=underline guibg=NONE term=underline cterm=underline
set cursorline
The issue that I'm having is that it doesn't work when
On Friday, March 22, 2013 4:39:14 PM UTC-5, FlashBurn wrote:
colorscheme xoria256
hi CursorLine gui=underline guibg=NONE term=underline cterm=underline
set cursorline
what happens if you use in vimrc:
hi CursorLine NONE gui=underline term=underline cterm=underline
note the NONE at the
Yes, I can move one line up and down by using such ddkp Key combination
But, I made a plugin for doing this action more conveniently.
For one line,in NORMAL or INSERT mode,
ctrl-shift-j moving down
ctrl-shift-kmoving up
For block,(this is in VISUAL mode)
the same action
32 matches
Mail list logo
