On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
On windows 7 64-bit I get this behaviour both in gvim and vim.
The options I have in the vimrc file are read, so this seems like a bug.
Regards
Andreas Stabel
Does your
On Tuesday, July 30, 2013 1:07:20 AM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 11:39:11 AM UTC-5, Stephen Lee wrote:
On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote:
On Monday, July 29, 2013 4:16:49 AM UTC-5, anst wrote:
On windows 7 64-bit I get this behaviour both
On Wednesday, January 1, 2014 6:15:18 AM UTC+8, LiTuX wrote:
Since msys-bash has the same issue, while msysgit's bash fixed it, I think
there must be some way to fix this issue. So will anyone post a patch?
Actually the mechanism is like that:
IME(unicode) -- Console(CP936) -- vim(any codepage
On Wednesday, January 1, 2014 8:16:12 PM UTC+8, Andre Sihera wrote:
On 01/01/14 19:59, Stephen Lee wrote:
On Wednesday, January 1, 2014 6:15:18 AM UTC+8, LiTuX wrote:
Since msys-bash has the same issue, while msysgit's bash fixed it, I think
there must be some way to fix this issue. So
Hello
For you reference, I am using Simplified Chinese Windows xp sp3.
Windows imposes a lot of limitations on console (DOS mode): The
internal encoding has to be in codepages while the output can be in
codepages or in unicode. I think problems happened during encoding
conversion. Gvim hence
other characters can.
On Wed, Dec 7, 2011 at 7:29 AM, Stephen Lee stephenletter...@gmail.comwrote:
Hello
For you reference, I am using Simplified Chinese Windows xp sp3.
Windows imposes a lot of limitations on console (DOS mode): The
internal encoding has to be in codepages while
Hello
Just would like to report that gvim build 782 complains when exiting:
E245: Illegal char ',' in font name WenQuanYi Zen Hei
Mono:h12,WenQuanYiZenHeiMono:h12
My vimrc config is:
set guifontwide=WenQuanYi\ Zen\ Hei\ Mono:h12,WenQuanYiZenHeiMono:h12
It does not happen before patch 773
My
Hello I just join discussion because I love vim and want to give a
small suggestion:
Is it possible to put a parameter in .vimrc like:
set keymap=byte-queue, structured, etc..
(default is byte-queue)
so that both sets of mapping could be kept...
sorry if I see the problem too surface.
On Feb
Would it be better to have a new folder called Keyboard, putting all
the key mapping definition files like dvorak.vim, 101-keyboard.vim,
etc. and let people set in .vimrc?
It may be more flexible than just new or old term mode...
On Feb 18, 6:07 am, Paul LeoNerd Evans leon...@leonerd.org.uk
Therefore I propose letting users choose their preferred keyboard
layouts instead of forcing any specific one to them.
In your case it seems you are talking about QWERTY and QWERTZ (from
wiki), so the following would be keyboard layouts in the new directory
called Keyboard
(General keyboard
Sorry Ben
This is my first time joining a discussion, I had a hard time just to
open an account and send my suggestion. I use the default reply
function and I don't mean to upset anyone. Hopefull now this reply is
well-edited (I removed the quote).
About vim, I misunderstood that it was a
Hello
I am trying to expand the command window a bit so that it becomes a
simple option selector (I put set cmdheight=5 in vimrc). I echo
those options like:
(they are longer than the window)
1. Option 1 -- ..Long
Explanation.
2. Option 2 --
Sorry the scrollbar is for the main window and not for the command
window.
Anyway if anyone knows please tell me how to nowrap the echoes.
Thankyou
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information,
Rather than reinventing the wheel, have you tried using the :options
command?
I think I tried the :options by directly edit the vimrc files and test
the followings as well:
:setlocal nowrap
:echo long text (longer then window)
Also I seach a lot of books about echo and echohl, etc, but I
14 matches
Mail list logo
