I have no idea why, but it appears that the spam from
ad...@139.com to anyone who posts to vim_use has stopped. As I
mentioned, I have emailed everyone who receives vim_use asking
about the problem (in batches of 60 at a time). Thanks to those
who responded. I unsubscribed 60 members since some of
On 12/20/2012 08:02 AM, John Beckett wrote:
I have no idea why, but it appears that the spam from
ad...@139.com to anyone who posts to vim_use has stopped. As I
mentioned, I have emailed everyone who receives vim_use asking
about the problem (in batches of 60 at a time). Thanks to those
who
In some Windows (not all) installations the following VIM (vim.exe **and**
gvim) command fails with a segfault:
:python print type(sys.stdout)
It is discussed here:
https://github.com/davidhalter/jedi-vim/issues/27#issuecomment-11572332
Is there anyone who knows why this is happening? I think
On 12/20/2012 12:08 PM, ping wrote:
hi nico and other vim conquetermers:
I found this a (relatively) big issue:
say if you have your capture of output from a command you issued to
your remote machine from within conqterm,
the big advantage of using conqueterm is the ability to leverage
On 12/20/2012 12:11 PM, ping wrote:
On 12/20/2012 12:08 PM, ping wrote:
hi nico and other vim conquetermers:
I found this a (relatively) big issue:
say if you have your capture of output from a command you issued to
your remote machine from within conqterm,
the big advantage of using
On Thu, Dec 20, 2012 at 9:02 AM, John Beckett johnb.beck...@gmail.comwrote:
I have no idea why, but it appears that the spam from
ad...@139.com to anyone who posts to vim_use has stopped. As I
mentioned, I have emailed everyone who receives vim_use asking
about the problem (in batches of 60
hi nico and other vim conquetermers:
I found this a (relatively) big issue:
say if you have your capture of output from a command you issued to your
remote machine from within conqterm,
the big advantage of using conqueterm is the ability to leverage the
existing vim search knowledge you
My .gvimrc resource file only contains a few custom modifications like:
set ...
set guifont=...
highlight Normal guibg=black
colorscheme slate
noremap ...
I believe I have the default automatic filetype and syntax coloring VIM
configuration settings, since there are no syntax-relevant commands
On 2012-12-20, analogsix wrote:
My .gvimrc resource file only contains a few custom modifications like:
set ...
set guifont=...
highlight Normal guibg=black
colorscheme slate
noremap ...
I believe I have the default automatic filetype and syntax
coloring VIM configuration settings,
result of running that command is:
filetype=
You hit the nail on the head. Namely, when the buffer(s) are first loaded onto
gVIM, the filetype(s) aren't recognized (as we can see the 'filetype' option is
set to blank).
As a quick fix to get gVIM to properly load and recognize my *.sv files,
Can you supply your output from :ver.
--
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 2012-12-20, analogsix wrote:
result of running that command is:
filetype=
You hit the nail on the head. Namely, when the buffer(s) are first
loaded onto gVIM, the filetype(s) aren't recognized (as we can see
the 'filetype' option is set to blank).
As a quick fix to get gVIM to
Is there a way to reload the vimrc (and other files), so that the changes in
the vimrc take immediate effect. :e doesn't seem to do the trick.
I'm editing my vimrc a lot, and I'm hoping there is an easier way than
constantly closing and reopening everything.
Any help and suggestions are
I encounter the same problem.
At 2012-12-21 03:23:10,analogsix adi...@gmail.com wrote:
result of running that command is:
filetype=
You hit the nail on the head. Namely, when the buffer(s) are first loaded onto
gVIM, the filetype(s) aren't recognized (as we can see the 'filetype' option
is set
On 21 Dec 2012, at 6:52, stillLearningVim wrote:
Is there a way to reload the vimrc (and other files), so that the
changes in the vimrc take immediate effect. :e doesn't seem to do the
trick.
:source PATH_TO_FILE
i.e.: :source ~/.vimrc
Niels
--
You received this message from the vim_use
On 21 Dec 2012 07:16, Niels Kobschätzki ni...@kobschaetzki.net wrote:
On 21 Dec 2012, at 6:52, stillLearningVim wrote:
Is there a way to reload the vimrc (and other files), so that the
changes in the vimrc take immediate effect. :e doesn't seem to do the trick.
:source PATH_TO_FILE
i.e.:
16 matches
Mail list logo
