s the asterisk. That does not seem part of the vertical bar. Status
lines seem to overlap it, but it cannot be controlled through status
line specifications. I also attach a couple of small pictures, I hope
they make it through.
Nicola
--
--
You received this message from the "vim_use" m
In article <20150506153730.ga6...@256bit.org>,
Christian Brabandt wrote:
> Hi Nicola!
>
> On Mo, 04 Mai 2015, Nicola wrote:
>
> > Hello,
> > my first post here, hope my question is not too trivial. Is there a way
> > to change the color for the one cha
chars', specifically a note about the stl/stlnc
suboption defaults.
Ah, thanks: I wouldn't have found it myself.
Nicola
--
--
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,
whether there is a better way to detect when the user
makes the active window the only visible one.
Nicola
--
--
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 http://www.vim.org/ma
On 2015-05-25 05:12:21 +, Nikolay Pavlov said:
2015-05-25 1:12 GMT+03:00 Justin M. Keyes :
On Sun, May 24, 2015 at 5:19 AM, Nicola wrote:
Hi,
am I right that does not trigger any event? I have a custom
status line, which does not get updated when I close all other windows. For
now, I
ys,
do this only if `BuildNewStatusLine()` function is called. At the
start set &g:statusline (note: ***global* option**) to
%!BuildNewStatusLine(). :h global-local
I think I don't understand this point. Would you mind to elaborate?
Nicola
--
--
You received this message fro
e one (I want different
status lines
for active and inactive windows)? I cannot use winnr() inside BuildStatusLine()
or in the context of %!.
2) When I open several windows and then I close them with o, I get
an out of bounds
error in WinNrFromID(). Why? Is the function being called for
closing/c
On 2015-05-26 09:04:39 +, Nicola said:
On 2015-05-26 04:59:00 +, Nikolay Pavlov said:
Default value from &l:statusline is &g:statusline (actually,
pseudo-value “no value set, fall back to &g:statusline”). If you set
&g:statusline to `%!BuildNewStatusLine()` and run
`Re
;m glad I have decided to implement my own status line instead of
using a plugin: I am learning a lot along the way.
Thanks,
Nicola
--
--
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 infor
part. See one of my previous posts.
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscri
ut in my (limited) benchmarks this seems
to perform
quite well.
So, in the end, I have a bi-colored collapsible status line highlighting the
current mode (and showing other information), which can be drawn in 1.5x-2x
time compared to a basic status line. My approach may not be general enough
to cove
On 2015-05-31 02:56:13 +, Rick Dooling said:
Have you ever tried vim-airline?
Sure, I have used it since not long ago, and it's very nice. But now I have
more or less the same amount of configuration code in my vimrc, and a
plugin less.
Nicola
--
--
You received this message fro
d=2142
https://github.com/jacquesbh/vim-showmarks
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You received this message beca
out. Toggling autoindent does not seem to
help either. I have formatoptions=tcqrnjo. Any suggestion?
Nicola
--
--
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 http://w
Whenever I am in the location list and hit Enter to jump to
the main buffer, the location list scrolls back to line 1.
Is it possible to avoid that and keep the list at its current
position?
I am using Syntastic, if that matters.
Nicola
--
--
You received this message from the "vi
m not
sure is a good thing (say, if I want to distribute the code as a plugin).
Is there a better way?
Nicola
--
--
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 http://www.vim.o
(and lexpr, too!) uses the global value of
errorformat.
or you could save and restore the global value like this:
let l:efm = &efm
set errorformat=%f:%l:%m
cexpr output
let &efm = l:efm
Thanks, I hadn't thought about that. This seems like the way to go.
Nicola
Christian: I'll try the patch on the weekend.
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You received this message bec
steps above. Can you suggest a fix?
Using Vim 7.4.963 on OS X.
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You received th
he dialect be loaded directly without requiring
the use to set g:sql_type_default?
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You
g file. In a dialect plugin one would then define:
au BufNewFile,BufRead *.pgsql let b:sql_type_default='pgsql' | setfiletype sql
Nicola
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mo
On 2016-01-09 10:24:08 +, Nicola said:
Is there a way to have the dialect be loaded directly without requiring
the use to set g:sql_type_default?
Is pgsql not a good choice as a default for you?
Yes, for me it is. But, in the perspective of making my plugin available
to a general
From time to time, upon exiting Vim an error message flashes on the screen, but
too quickly for me to read it. I'd like to understand why it happens. Is there
a way to log such errors or somehow pause Vim when an error appears?
Nicola
--
--
You received this message from the &qu
On 2016-01-21 18:58:24 +, Gary Johnson said:
On 2016-01-21, Ben Fritz wrote:
On Thursday, January 21, 2016 at 12:27:51 PM UTC-6, Nicola wrote:
From time to time, upon exiting Vim an error message flashes on the screen, but
too quickly for me to read it. I'd like to understand w
On 2016-01-23 06:56:13 +, bsta...@gmail.com said:
在 2016年1月22日星期五 UTC+8上午2:27:51，Nicola写道：
From time to time, upon exiting Vim an error message flashes on the screen, but
too quickly for me to read it. I'd like to understand why it happens. Is there
a way to log such errors or so
n the thesaurus .dat file (it is a text
file). I have taken a quick look at one of them, and it should not be
too hard to turn it into a format usable by Vim: removing the first
line and the parts in parentheses should be enough.
Hope this helps,
Nicola
--
--
You received this message from the &qu
On 2016-02-12 14:16:50 +, Nicola said:
Another possibility is to download an .oxt file, change the suffix to
.zip, uncompress it, and open the thesaurus .dat file (it is a text
file). I have taken a quick look at one of them, and it should not be
too hard to turn it into a format usable by
On 2016-02-12 18:04:09 +, Nicola said:
On 2016-02-12 14:16:50 +, Nicola said:
Another possibility is to download an .oxt file, change the suffix to
.zip, uncompress it, and open the thesaurus .dat file (it is a text
file). I have taken a quick look at one of them, and it should not be
Suppose % is
/path to/file.txt
I want to use the directory containing file.txt in makeprg. Say:
CompilerSet makeprg=mycmd\ --working-dir\ %:p:h:S
Now, %:p:h correctly gives me
/path to
But then, %:p:h:S results in
'/path to/file.txt'
(using Vim 7.4.1257). Is this a bu
Vim 7.4 1-1525
tmux 2.1
both installed with Homebrew.
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You received this message
should it be reported to tmux's maintainer?
I have no idea what reattach-to-user-namespace does to fix those messages.
Nicola
--
--
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 informatio
On 2016-03-18 14:08:33 +, Nicola said:
On 2016-03-18 12:23:25 +, Christian Brabandt said:
Hi Nicola!
On Mi, 16 Mär 2016, Nicola wrote:
In OS X, when I launch `vim`, or even `vim -u NONE`, within a tmux session,
the following messages are logged:
16/03/16 10:49:13,539 vim[11605
On 2016-03-18 12:23:25 +, Christian Brabandt said:
Hi Nicola!
On Mi, 16 Mär 2016, Nicola wrote:
In OS X, when I launch `vim`, or even `vim -u NONE`, within a tmux session,
the following messages are logged:
16/03/16 10:49:13,539 vim[11605]: LaunchServices: received
hing to do with your problem.)
OT, but I don't think reattach-to-user-namespace is needed any longer
(see the note in URL
you've pasted). I am not using it.
Nicola
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are
f YCM, which must
now be loaded manually. To do so, I need
:packadd youcompleteme
but also
:call youcompleteme#Enable()
because :packadd does not trigger VimEnter.
Does what I said make sense? Am I missing something?
Nicola
--
--
You received this message from the "vim_use" maillis
On 2016-03-25 19:15:59 +, Nicola said:
I would like to start using Vim's new package feature, but first I want to make
sure that I have understood how it is supposed to be used. Is it too early to
ask for tips about that?
First let me summarize what I have understood about packages (p
On 2016-03-26 17:56:34 +, Bram Moolenaar said:
Nicola wrote:
Then, everything should work as before, with the exception of YCM, which must
now be loaded manually. To do so, I need
:packadd youcompleteme
but also
:call youcompleteme#Enable()
because :packadd does not trigger VimEnter
On 2016-03-26 18:53:44 +, Andy Wokula said:
if has("vim_starting")
" init on VimEnter
else
" init immediately
endif
That works, thanks!
Nicola
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the
that a bug?
Using Vim 7.4.1655.
Nicola
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribe
On 2016-03-29 19:53:07 +, Bram Moolenaar said:
Nicola wrote:
Neocomplete's plugin folder is organized as follows:
plugin/
neocomplete.vim
neocomplete/
buffer.vim
dictionary.vim
tag.vim
No matter whether neocomplete is in pack/*/start/ or in pack/*/opt/,
only plugin/neocomplete.v
On 2016-03-30 04:43:56 +, Nicola said:
If that is the intended behaviour, maybe it should be noted more explicitly
in the help files. In `:h packages`, it is written that Vim:
Also note this difference: if pack/foo/opt/neocomplete is loaded during a
session with `:packadd neocomplete
ich a user may build its own package by putting
together loosely coupled plugins. Or a package that provides some optional
extensions, which are independent of each other. In those cases, a command like
the above might be convenient.
Nicola
--
--
You received this message from the "vim_use&qu
verything is fine again (until
the next modification). What's wrong with the code above?
Nicola
--
--
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 http://www.vim.org/ma
On 2016-03-31 20:53:34 +, Nicola said:
The following foldexpr is giving me headaches because it doesn't work
under all circumstances:
fun! s:outlinerFoldingRule(n)
return getline(a:n) =~ '^\s*:' ?
\ 20 : indent(a:n) < indent(a:n+1) ?
\ ('>&
On 2016-04-02 15:24:20 +, Richard Mitchell said:
On Saturday, April 2, 2016 at 2:17:22 AM UTC-4, Nicola wrote:
On 2016-03-31 20:53:34 +, Nicola said:
The following foldexpr is giving me headaches because it doesn't work
under all circumstances:
fun! s:outlinerFoldingRule(n)
r
On 2016-04-02 13:22:18 +, Bram Moolenaar said:
Nicola wrote:
What do you think about adding a command that loads all the plugins in an opt
directory at once? Something like:
:packaddall[!] {name} Search for a package directory in 'packpath' and source
all the plugin files fo
atter case?
This is a contrived example, but I have encountered this problem when trying to
define a mapping in a plugin, which builds the regex out of a variable (so I
need to use :exe).
Using Vim 7.4.1707.
Nicola
--
--
You received this message from the "vim_use" maillist.
Do not
arch('abc', 'bWz')
returns 0. Given the description above, I would expect the opposite. Am I
missing something?
Nicola
--
--
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,
been fixed a few weeks ago.
Would it be possible to merge the latest netrw into Vim?
Nicola
--
--
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 http://www.vim.org/maillist.php
On 2016-04-18 14:00:43 +, Charles E Campbell said:
Nicola wrote:
On 2016-02-29 22:55:13 +, Charles Campbell said:
gt.ma...@gmail.com wrote:
hello all,
On Vim 7.4.1401 (OS X 10.11.3), netrw’s :Explore is acting very
weirdly for me.
My workflow is to usually open some file, use
think about making all
or some them optional?
As a matter of personal taste, I'd like to see all of them in pack/dist/opt.
Nicola
--
--
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 inf
t_io": "file", "out_name": "/dev/null", "err_io": "null"})
Shouldn't this form be equivalent to the previous one? In general, if all I
want is launch a process, but I don't care about its output, is this the right
way?
Tangentially
On 2016-05-06 17:19:58 +, Nicola said:
Some time ago I had defined a thin wrapper around job_start() to run a LaTeX
job asynchronously. Recently, it has stopped working. For some reason, with Vim
7.4.1817, when I give the following command:
call job_start(['lualatex', 'foo.
On 2016-05-06 21:23:30 +, Bram Moolenaar said:
Nicola wrote:
On 2016-05-06 17:19:58 +, Nicola said:
Some time ago I had defined a thin wrapper around job_start() to run a LaTeX
job asynchronously. Recently, it has stopped working. For some reason, with Vim
7.4.1817, when I give the
On 2016-05-07 07:04:44 +, Nicola said:
call job_start(['lualatex', 'foo.tex', '>/dev/null', '2>&1'],
\ {"in_io": "null", "out_io": "null", "err_io": "null"})
This still
On 2016-05-07 10:28:43 +, Nicola said:
On 2016-05-07 07:04:44 +, Nicola said:
call job_start(['lualatex', 'foo.tex', '>/dev/null', '2>&1'],
\ {"in_io": "null", "out_io": "null", "
On 2016-05-07 14:21:15 +, Bram Moolenaar said:
Nicola wrote:
On 2016-05-07 07:04:44 +, Nicola said:
call job_start(['lualatex', 'foo.tex', '>/dev/null', '2>&1'],
\ {"in_io": "null", "out_io&quo
On 2016-05-08 15:30:01 +, Nicola said:
On 2016-05-07 14:21:15 +, Bram Moolenaar said:
Nicola wrote:
On 2016-05-07 07:04:44 +, Nicola said:
call job_start(['lualatex', 'foo.tex', '>/dev/null', '2>&1'],
\ {"in_
On 2016-05-08 19:49:01 +, Bram Moolenaar said:
Nicola wrote:
On 2016-05-07 07:04:44 +, Nicola said:
call job_start(['lualatex', 'foo.tex', '>/dev/null', '2>&1'],
\ {"in_io": "null", "out_io&quo
The following patterns both match up to column 17 included:
/.*\%17v
/.*\%17v.
If ^ is added, the two are no more equivalent:
/^.*\%17v <-- matches up to column 16
/^.*\%17v.<-- matches up to column 17
Is this a bug?
Seeing this with Vim 7.4 1-1864.
Nicola
--
--
You receive
On 2016-06-07 20:47:07 +, Nikolay Aleksandrovich Pavlov said:
2016-06-07 22:45 GMT+03:00 Nicola :
The following patterns both match up to column 17 included:
/.*\%17v
/.*\%17v.
If ^ is added, the two are no more equivalent:
/^.*\%17v <-- matches up to column 16
/^.*\%
packages have some best practices in mind.
You may search for the thread "Packages: best practices?" from last
March, where I outlined my ideas.
Nicola
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are r
finition is not reinstated because
syntax/vim.vim uses `hi def` rather than simply `hi` (and there are good
reasons for that, I'm told).
Is there a mechanism to permit the definition from the first colorscheme
to be activated again (something like completely deleting some highlight
groups)?
On 2016-09-06 17:15:35 +, Nicola said:
Hi,
sometimes, switching colorschemes seems to "corrupt" some colors and I am
trying to figure out if there's a way around it.
For example, if I start Vim with syntax on and the default color scheme to
edit my vimrc, then `:hi vimC
t way to jump to the desired
line is just to type something like 8j or 14k.
Last suggestion: if you don't mind installing plugins, there are
several extensions to built-in movements. The most popular is probably
EasyMotion, but my personal favourite is Sneak.
Nicola
--
--
You recei
Hello,
I can't figure out how to match a pattern with the following structure:
; http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vi
antly solved your own problem, so this may be a bit late, but…
using the commands and mappings described in :h preview-window might get
you close to your workflow. Off the top of my head, assuming you start from
a single window:
:ptag or } or g} (to open a tag in the preview window)
(to exchange w
Hi Ada,
You can record a macro using the q command and use ctrl-a to increment numbers.
I think this tutorial might help you do what you ask:
http://www.thegeekstuff.com/2009/01/vi-and-vim-macro-tutorial-how-to-record-and-play/
Cheers,
Nick
On Sat, Dec 4, 2010 at 6:42 PM, Ada wrote:
>
>
>
On Sat, Dec 4, 2010 at 8:30 PM, Nicola Paolucci wrote:
> Hi Ada,
>
> You can record a macro using the q command and use ctrl-a to increment
> numbers.
>
> I think this tutorial might help you do what you ask:
> http://www.thegeekstuff.com/2009/01/vi-and-vim-macro-tutorial-h
69 matches
Mail list logo
