What gets displayed?
Does this happen on gVim as well?
Do Chinese characters appear correctly in the console window when using
other programs?
-Original Message-
From: Mike Li [mailto:[EMAIL PROTECTED]
Sent: Monday, March 05, 2007 10:04 PM
To: vim-dev@vim.org
Subject: Re: bug: gvim
Hi,
I've searched for this for some time now but it's either not available
or I have to hone my search skills a lot.
Most of the time I have multiple xterms opened, running vim sessions
within the same project. The files are tagged and I'm using :ta and :tj
a lot. It happens often that I'm
for big-endian, the following is displayed:
[EMAIL PROTECTED]@
for little-endian, the following is displayed:
8l^M^@
^@
^@ and ^M are control characters.
this definitely happens on gvim as well as console vim under windows
xp. i'm not sure if it happens with other programs in the console
one point of clarification: the correcly functioning fedora console
vim binaries were run under x11 (rxvt-unicode) with appropriate
truetype fonts.
-x
On 3/5/07, Mike Li [EMAIL PROTECTED] wrote:
gvim 7.0 (patches 1-205) under windows xp, built with the mingw
compiler under cygwin (gcc
So, the bottom line is, I'm looking for is a way to open a file
automatically in r/o mode if I'm going to jump to a tag in that file
and the file is opened in another session.
hi,
I've thought about the same feature. I think there are three solutions now:
1. use one xterm with tabs instead
one more update: if i add the following two lines to my _vimrc, then
the ucs-2le text file works:
set fileencodings+=ucs-2le
set encoding=utf-8
note that both need to be set before i edit the file. once i load the
file, setting them no longer helps.
-x
On 3/6/07, Mike Li [EMAIL PROTECTED]
On Mar 6 11:54, Milan Vancura wrote:
So, the bottom line is, I'm looking for is a way to open a file
automatically in r/o mode if I'm going to jump to a tag in that file
and the file is opened in another session.
hi,
I've thought about the same feature. I think there are three
Mike Li wrote:
one more update: if i add the following two lines to my _vimrc, then
the ucs-2le text file works:
set fileencodings+=ucs-2le
set encoding=utf-8
note that both need to be set before i edit the file. once i load the
file, setting them no longer helps.
-x
Of course:
- Vim needs
Patch 7.0.208 (after 7.0.171 and 7.0.180)
Problem:VMS: changes to path handling cause more trouble than they solve.
Solution: Revert changes.
Files: src/buffer.c, src/memline.c, src/os_unix.c
*** ../vim-7.0.207/src/buffer.c Tue Nov 28 17:44:51 2006
--- src/buffer.cMon Mar 5
Using gVim, if I load your file normally, I do get ASCII instead of Unicode.
But if I then type:
:e ++enc=ucs-2
it appears to work. I don't have a Chinese font, so I get a box, but it is a
single character and it is double-width, so it appears to be interpreted
correctly by Vim. The same thing
much thanks to Doug and A.J. -- i now see that it wasn't a bug at all.
sorry for the noise.
-x
On 3/6/07, Doug Cook [EMAIL PROTECTED] wrote:
Using gVim, if I load your file normally, I do get ASCII instead of Unicode.
But if I then type:
:e ++enc=ucs-2
it appears to work. I don't have a
Hi Gary,
On 3/6/07, Gary Johnson [EMAIL PROTECTED] wrote:
If I open a new window, read into it the results of a grep command,
e.g.,
:r !grep -nH somepattern somefileset
and then try to use that buffer as a quickfix list or location list
with either the :cb or :lb commands, respectively, I
12 matches
Mail list logo
