` Ben Fritz wrote:
On Oct 12, 6:47 pm, Linda W v...@tlinx.org wrote:
Jürgen Krämer wrote:(at least when I launch from explorer...)...so if it
finds my .vim and .gvim, why doesn't it find .vim/colors/.vim?did you
change the 'runtimepath' option? On Windows the directory for
On Fri, Oct 21, 2011 at 6:21 AM, Thilo Six t@gmx.de wrote:
Peng Yu wrote the following on 21.10.2011 03:00
Hello,
Suppose that I open 3 .R files with gvim -o. All the three .R files
are correctly syntax highlighted. However, if I use :bd to close one
window, the next window's syntax
On Oct 24, 10:40 am, Bernhard Heijstek bernhard.heijs...@yahoo.com
wrote:
I want it in such a way that on double clicking an already opened file, or a
new file, gVim uses the same window. From this question asked previously on
Stackoverflow
On Oct 25, 2:52 am, Linda W v...@tlinx.org wrote:
Comments:
1) that .vim isn't searched for in the same way with 'vimfiles', is a
rather glaring BUG, given the above. It's incompatible with the
documented procedures for checking the names of .vimrc, .gvimrc, and .exrc.
But, unlike the
On Oct 25, 10:23 am, Peng Yu pengyu...@gmail.com wrote:
On Fri, Oct 21, 2011 at 6:21 AM, Thilo Six t@gmx.de wrote:
Peng Yu wrote the following on 21.10.2011 03:00
Hello,
Suppose that I open 3 .R files with gvim -o. All the three .R files
are correctly syntax highlighted. However,
Ben Fritz wrote:
On Oct 25, 2:52 am, Linda W v...@tlinx.org wrote:
Comments:
1) that .vim isn't searched for in the same way with 'vimfiles', is a
rather glaring BUG, given the above. It's incompatible with the
documented procedures for checking the names of .vimrc, .gvimrc,
Hello Ben,
-- snip --
I'm glad it works, but something is wrong here.
Syntax highlight is local to a buffer. If you have 3 separate buffers
opened in 3 separate Windows, deleting one buffer (and closing its
window) should have no effect on the other buffers/windows.
I suspected that but
On 2011-10-25, Linda W wrote:
Ben Fritz wrote:
The only reason Vim uses vimfiles at all on Windows, is that on
Windows, 'runtimepath' defaults to including vimfiles instead of .vim.
We could default to include BOTH, however this could easily break a
lot of systems already out
Thilo Six wrote the following on 25.10.2011 19:37
Hello
-- snip --
I'm glad it works, but something is wrong here.
Syntax highlight is local to a buffer. If you have 3 separate buffers
opened in 3 separate Windows, deleting one buffer (and closing its
window) should have no effect on the
On Oct 25, 11:39 am, Linda W v...@tlinx.org wrote:
Ben Fritz wrote:On Oct 25, 2:52 am, Linda Wv...@tlinx.orgwrote:Comments: 1)
that .vim isn't searched for in the same way with 'vimfiles', is a rather
glaring BUG, given the above. It's incompatible with the documented
procedures for
On Tue, Oct 25, 2011 at 1:06 PM, Thilo Six t@gmx.de wrote:
Thilo Six wrote the following on 25.10.2011 19:37
Hello
-- snip --
I'm glad it works, but something is wrong here.
Syntax highlight is local to a buffer. If you have 3 separate buffers
opened in 3 separate Windows, deleting
Ben Fritz wrote:
And I'm sure we can safely assume that Unix users everywhere would be
angry for years if Bram decided one day to use vimfiles rather
than .vim for the default Unix Vim config.
Grrr.
--
You received this message from the vim_use maillist.
Do not top-post! Type
George V. Reilly wrote:
On Fri, Oct 14, 2011 at 2:50 PM, Alessandro Antonello wrote:
On Fri,
Oct 14, 2011, at 9:41 AM, Ben Fritz wrote:
The default Windows setting, to hide the extension for known file
types, will probably make matters worse. I expect, though I have not
Wow. So many issues to choose from.
On 2011-10-25, Linda W wrote:
But lately, win7 and samba threw 2 more curve balls at me:
Sometimes randomly, windows would set my home to be:
C:\users\lindaw
and, other times:
i:\\
It depended on whether or not (I think) it managed to
`
Ben Fritz wrote:
On Oct 25, 11:39 am, Linda W v...@tlinx.org wrote:
Ben Fritz wrote:On Oct 25, 2:52 am, Linda Wv...@tlinx.orgwrote:Comments: 1) that .vim isn't searched for in the same way with 'vimfiles', is a rather glaring BUG, given the above. It's incompatible with
On Wed, Oct 26, 2011 at 9:23 AM, Linda W v...@tlinx.org wrote:
But I asked how it would be incompat if it looked for .vim, if found, then
don't look for vimfiles.?
You always have multiple runtimepath, at least you have ~/.vim and
/usr/share/vim/vim73 as the runtimepath.
If you ignore any
Hi,
Ben Fritz wrote:
This is pretty much what I was proposing. I would extend it further.
Something like this could be placed in vimrc_example.vim, which AFAIK
is sourced by default in a brand-new Windows installation:
check for $HOME/.vim existing INSTEAD of $HOME/vimfiles, in case Vim
Hi,
Linda W wrote:
I Can say one thing for certain. The PC Version hasn't been a correct
path since Win98 (if then).
HOME isn't a a system defined var. HOMEDRIVE/HOMEPATH, yes...but not
HOME. So unless someone set it, it won't it won't exist.
there's no need for the user to set $HOME
18 matches
Mail list logo
