Hello!
2020-03-10 오후 11:30에 Christian Brabandt 이(가) 쓴 글:
>
> On Di, 10 Mär 2020, Franklin, Jason wrote:
>
>> Greetings:
>>
>> I have a simple question. What is the future of the man.vim plugin
>> (that supplies the :Man command)?
There's no future loadmap. I think of it as performing basic
2018-07-25 오후 2:32에 Yegappan Lakshmanan 이(가) 쓴 글:
Hi,
On Tue, Jul 24, 2018 at 11:59 AM, Josh Triplett
wrote:
:vertical Man somemanpage still does a horizontal split. It uses the new
command internally, but :vertical doesn't seem to affect it.
VIM - Vi IMproved 8.1 (2018 May 17, compiled Jun
2018-05-02 오후 2:28에 goweol (Vim Github Repository) 이(가) 쓴 글:
Because man.vim used such as 'norm ggdd', if you remap 'g' or 'd', the
result is unpredictable.
Because I don't see your patch, I just changed and tested.
Please let me know if you don't agree with my patch.
I will send full man.vim
2017-12-08 오전 9:01에 SungHyun Nam 이(가) 쓴 글:
Hello,
2017-11-26 오후 10:56에 Bram Moolenaar 이(가) 쓴 글:
Patch 8.0.1343
Problem: MS-Windows: does not show colored emojis.
Solution: Implement colored emojis. Improve drawing speed. Make
'taamode'
work. (Taro Muraoka, Yasuhiro
Hello,
2017-11-26 오후 10:56에 Bram Moolenaar 이(가) 쓴 글:
Patch 8.0.1343
Problem:MS-Windows: does not show colored emojis.
Solution: Implement colored emojis. Improve drawing speed. Make 'taamode'
work. (Taro Muraoka, Yasuhiro Matsumoto, Ken Takata, close #2375)
Files:
GMT+09:00 Kazunobu Kuriyama
> <kazunobu.kuriy...@gmail.com <mailto:kazunobu.kuriy...@gmail.com>>:
>
> 2016-03-10 15:47 GMT+09:00 SungHyun Nam <gow...@gmail.com
> <mailto:gow...@gmail.com>>:
>
> 2016-03-10 오후 12:58에 Kazunobu Kuriyama 이(가) 쓴 글:
>
> From: *Kazunobu Kuriyama* <kazunobu.kuriy...@gmail.com
> <mailto:kazunobu.kuriy...@gmail.com>>
> Date: 2016-03-10 10:57 GMT+09:00
> Subject: Re: [gtk3vim] cannot select with mouse if cmdline is active
> To: SungHyun Nam <gow...@gmail.
ne.
>
> Is it OK for you?
I think you are a boss for gtk3 part. No problem! ^_^
Thanks!
>
> 2016-03-10 14:46 GMT+09:00 SungHyun Nam <gow...@gmail.com
> <mailto:gow...@gmail.com>>:
>
> 2016-03-10 오후 2:37에 SungHyun Nam 이(가) 쓴 글:
> > 2016-03-10 오후 2
2016-03-10 오후 2:37에 SungHyun Nam 이(가) 쓴 글:
> 2016-03-10 오후 2:17에 Kazunobu Kuriyama 이(가) 쓴 글:
>> Then, could you try this one, please?
>>
>> When you see the gtk2 color inversion carefully (in particular, the dots
>> along the color boundary), you'll find it's not reall
noticed background color for gtk2vim and gtk3vim is
different with a same syntax setting, I'm trying to check the gtk
theme. Now I decide I will live with this patch without further
investigating.
Thanks for your super-fast suport.
namsh
> 2016-03-10 14:05 GMT+09:00 SungHyun Nam <gow...
2016-03-10 오후 12:58에 Kazunobu Kuriyama 이(가) 쓴 글:
> Judging from the dates of the tar balls in the official repos,
> gtk+-3.0.0 was released on 2011-02-10 and cairo-1.10.0 (perhaps, a
> release version corresponding to the develop version 1.9.2) on 2010-09-06.
>
> It looks we can safely assume
2016-03-10 오전 11:13에 Kazunobu Kuriyama 이(가) 쓴 글:
> 2016-03-10 8:41 GMT+09:00 SungHyun Nam <gow...@gmail.com
> <mailto:gow...@gmail.com>>:
>
> I use up-to-dated ubuntu-14.04.
>
> IIRC, you used a relatively old gtk3, didn't you? So I'm wondering
> which
Hello,
With gtk3vim, I cannot use mouse to select a string if command
line is active. gtk2vim has no problem.
$ gtk3vim -u NONE -U NONE --noplugin main.c
:echo 'test'
Don't type ENTER key after typing 'test'. But try to select some
string with a mouse. I cannot select any string in window,
2016-03-04 오전 9:09에 SungHyun Nam 이(가) 쓴 글:
> 2016-03-03 오후 7:45에 Bram Moolenaar 이(가) 쓴 글:
>>
>> Patch 7.4.1475
>> Problem:When using hangulinput with utf-8 a CSI character is
>> misintepreted.
>> Solution: Convert CSI to K_CSI. (Sung
2016-03-03 오후 7:45에 Bram Moolenaar 이(가) 쓴 글:
>
> Patch 7.4.1475
> Problem:When using hangulinput with utf-8 a CSI character is
> misintepreted.
> Solution: Convert CSI to K_CSI. (SungHyun Nam)
> Files: src/ui.c
If a user use euc-kr, then hangul_string
Hello,
if utf-8 encoding is used, converted string can include CSI.
Thanks,
namsh
diff --git a/src/ui.c b/src/ui.c
index be5d8c5..0f6502e 100644
--- a/src/ui.c
+++ b/src/ui.c
@@ -1691,8 +1691,16 @@ push_raw_key(char_u *s, int len)
if (tmpbuf != NULL)
s = tmpbuf;
-while (len--)
2016-02-19 오후 4:21에 Marius Gedminas 이(가) 쓴 글:
> On Thu, Feb 18, 2016 at 08:57:07PM +0900, Kazunobu Kuriyama wrote:
>> Patch updated, made against v7.4.1345.
>>
>> With this patch, I addressed the cursor issue, aiming at smooth
>> cursor draw and low cpu usage.
>>
>> Hopefully, this resolves all
Hello,
First of all, many thanks for your effort.
I followed your every patch.
And I used 'gtk3-v7.4.1317' this whole day with NO PROBLEM.
To me, it seems gtk3-v7.4.1317 is same as gtk2 version (or maybe
even better (*1*)).
Now, I tested gtk3-v7.4.1320. It seems it almost work fine.
Maybe one
2016-02-05 오후 4:20에 Christian Brabandt 이(가) 쓴 글:
> Hi SungHyun!
>
> On Fr, 05 Feb 2016, SungHyun Nam wrote:
>
>> Hello,
>>
>> For the attached test file, only the line "title 3" is folded with
>> a command below:
>> $ vim -u NONE -U NONE
Hello,
For the attached test file, only the line "title 3" is folded with
a command below:
$ vim -u NONE -U NONE --noplugin -c 'set fen fdm=marker' test.txt
Maybe the only lines which exceeds 80 columns are folded?
BTW, I have a text file which contains many long lines
(30~1024 characters per
Hello,
I successfully installed vim-gtk3.
My system is ubuntu-14.04 and gtk lib is:
$ pkg-config --modversion gtk+-3.0
3.10.8
I have a rendering(refresh?) problem with vim-gtk2.
So that, I tried vim-gtk3 with a hope.
Unfortunely, vim-gtk3 is worse than vim-gtk2. :-(
For example, I cannot
2016-01-26 오후 8:04에 Christian Brabandt 이(가) 쓴 글:
> Hi Marius!
>
> I can confirm the redraw glitches. Those look a little bit like issue
> #91 (https://github.com/vim/vim/issues/91). Yes, if I modify the source
> and force some additional redraws, it works. However as noted in the
> issue, this
2015-11-06 오전 11:24에 SungHyun Nam 이(가) 쓴 글:
> 2015-11-06 오전 6:48에 Bram Moolenaar 이(가) 쓴 글:
>>
>> Namsh wrote:
>>
>>> 2015-11-03 오후 4:41에 Tony Mechelynck 이(가) 쓴 글:
>>>> On Tue, Nov 3, 2015 at 8:22 AM, SungHyun Nam <gow...@gmail.com> wrote:
>>&
2015-11-06 오전 6:48에 Bram Moolenaar 이(가) 쓴 글:
>
> Namsh wrote:
>
>> 2015-11-03 오후 4:41에 Tony Mechelynck 이(가) 쓴 글:
>>> On Tue, Nov 3, 2015 at 8:22 AM, SungHyun Nam <gow...@gmail.com> wrote:
>>>> Hello,
>>>>
>>>> I used hangulin fe
2015-11-03 오후 4:41에 Tony Mechelynck 이(가) 쓴 글:
> On Tue, Nov 3, 2015 at 8:22 AM, SungHyun Nam <gow...@gmail.com> wrote:
>> Hello,
>>
>> I used hangulin feature nowadays, because it does not support
>> utf-8 encoding, I always ran vim with 'set encoding=cp949'.
&g
2015-11-03 오후 4:41에 Tony Mechelynck 이(가) 쓴 글:
> On Tue, Nov 3, 2015 at 8:22 AM, SungHyun Nam <gow...@gmail.com> wrote:
>> Hello,
>>
>> I used hangulin feature nowadays, because it does not support
>> utf-8 encoding, I always ran vim with 'set encoding=cp949'.
&g
Hello,
I used hangulin feature nowadays, because it does not support
utf-8 encoding, I always ran vim with 'set encoding=cp949'.
But it gave me a pain whenever I open utf-8 encoded file.
So that, today I made a patch. Any feedback is welcome!
Thanks,
namsh
--
--
You received this message
On 2013-11-05 오후 4:22, Christian J. Robinson wrote:
On the 2nd I built 7.3.054 under cygwin, then some new patches came down
and when I tried to build again I got this:
In file included from /usr/lib/../include/w32api/minwindef.h:146:0,
from
Hello,
I noticed ftplugin/man.vim has problem if user set nu or rnu.
I'm not sure disabling the nu/rnu is a good idea.
I just follow the rule of VIM's help page.
If someone wants to set nu/rnu in man page, we can change like:
let $MANWIDTH = winwidth(0) - nu - rnu
I'm not sure 'nofen' is
Hello,
$ cat test
a
b
c
$ vim -u NONE --noplugin test
/a\n\(^b$\n\)\{1,2}c
The search failed with re=0. If I set 're=1', search works.
Thanks,
namsh
$ LANG= vim --version | head -2
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 13 2013 09:51:39)
Included patches: 1-1182
--
--
You
MikeM wrote:
It's been a while since I reported a problem with the patch here and no
further comment has been made. I guess the majority of users out there
are probably using one of the pre-packaged versions of vim 7.3 and so
this problem hasn't come down the pipeline to hit them yet. I have
Gary Johnson wrote:
On 2011-01-04, SungHyun Nam wrote:
Gary Johnson wrote:
On 2011-01-04, SungHyun Nam wrote:
Ben Fritz wrote:
On Jan 2, 7:01 pm, SungHyun Namgow...@gmail.comwrote:
Hello,
There is always a message:
CTIME - 2011-01-03 09:57:57
And vim detects it as error
Bram Moolenaar wrote:
Namsh wrote:
There is always a message:
CTIME - 2011-01-03 09:57:57
And vim detects it as error message.
Can vim ignore this message? starting with CTIME...
Or ignore a message if it cannot find a file in message.
This is mainly caused by the %f item in
Ben Fritz wrote:
On Jan 2, 7:01 pm, SungHyun Namgow...@gmail.com wrote:
Hello,
There is always a message:
CTIME - 2011-01-03 09:57:57
And vim detects it as error message.
Can vim ignore this message? starting with CTIME...
Or ignore a message if it cannot find a file in message.
Gary Johnson wrote:
On 2011-01-04, SungHyun Nam wrote:
Ben Fritz wrote:
On Jan 2, 7:01 pm, SungHyun Namgow...@gmail.com wrote:
Hello,
There is always a message:
CTIME - 2011-01-03 09:57:57
And vim detects it as error message.
Can vim ignore this message? starting with CTIME
Hello,
There is always a message:
CTIME - 2011-01-03 09:57:57
And vim detects it as error message.
Can vim ignore this message? starting with CTIME...
Or ignore a message if it cannot find a file in message.
Regards,
namsh
--
You received this message from the vim_dev maillist.
Do
Hello,
I Uses vim-7.3.69.
If I undo 'do' or 'dp', I cannot do 'do' or 'dp' for that hunk
again. I have to exit gvimdiff and re-run it.
If I typed 'do', and then if I realize I should do 'dp', what is the
best way?
Regards,
namsh
--
You received this message from the vim_dev maillist.
Do not
Bram Moolenaar wrote:
SungHyun Nam wrote:
Yuriy Kaminskiy wrote:
SungHyun Nam wrote:
2010-09-23 AM 12:49, Young Ho Park wrote:
Hello. I am a Vim user from South Korea. I seem to find the bug about
cut(or copy) and paste. Let me explain steps to a paste fail.
I use Vim7.2 in Gnome2.3
Yuriy Kaminskiy wrote:
SungHyun Nam wrote:
2010-09-23 AM 12:49, Young Ho Park wrote:
Hello. I am a Vim user from South Korea. I seem to find the bug about
cut(or copy) and paste. Let me explain steps to a paste fail.
I use Vim7.2 in Gnome2.3 of Fedora13 or Ubuntu10.04 and my locale
2010-09-23 AM 12:49, Young Ho Park wrote:
Hello. I am a Vim user from South Korea. I seem to find the bug about
cut(or copy) and paste. Let me explain steps to a paste fail.
I use Vim7.2 in Gnome2.3 of Fedora13 or Ubuntu10.04 and my locale is
ko_KR.utf8 0. I executed Vim. 1. I wrote Alphabet
Hello,
If I edit and write '/etc/hosts', vim died. I can edit other
files in /etc. And I found /etc/hosts is a symbolic link.
$ l /etc/hosts
lrwxrwxrwx 1 37 2009-09-07 14:48 /etc/hosts -
/c/WINDOWS/system32/drivers/etc/hosts
$ gdb ./vim.exe
(gdb) r -u NONE --noplugin /etc/hosts
Goescdd:wcr
James Vega wrote:
On Fri, Nov 13, 2009 at 5:39 PM, Bram Moolenaarb...@moolenaar.net wrote:
Tim Starling wrote:
GtkFileChooser is disabled in gvim, because gvim exits gtk_main() level
1 every time an event is received, causing GTK to write to the disk
excessively.
[snip]
That turns out to be
Hello,
I tested it with vim-6.3.82 and vim-7.3beta.
And run vim as:
git grep code | vim -u NONE --noplugin -
'gf' opens a file for the line below:
somedir/somefile.c: code...
somedir/somefile.c:#include code...
somedir/somefile.c:/* code...
But, 'gf' generates error for the line
SungHyun Nam wrote:
I tested it with vim-6.3.82 and vim-7.3beta.
And run vim as:
git grep code | vim -u NONE --noplugin -
'gf' opens a file for the line below:
somedir/somefile.c: code...
somedir/somefile.c:#include code...
somedir/somefile.c:/* code...
But, 'gf' generates error for the line
Dominique Pellé wrote:
AM, SungHyun Nam wrote:
hg changeset: 2255:0e27866cea99
VIM-7.3 BETA died with sequence below:
vim newfile.sh
:w
:!chmod 0755 %
:e
[snip...]
I can't reproduce it. In your stack, I see that it's reading
/home/namsh/tmp/ex.sh
and /home/namsh/.vim
Bram Moolenaar wrote:
SungHyun Nam wrote:
hg changeset: 2255:0e27866cea99
VIM-7.3 BETA died with sequence below:
vim newfile.sh
:w
:!chmod 0755 %
:e
I cannot reproduce it. Looks like a problem that was fixed in changeset
2253:772bfca06c18, but you should have
Hello,
hg changeset: 2255:0e27866cea99
VIM-7.3 BETA died with sequence below:
vim newfile.sh
:w
:!chmod 0755 %
:e
Regards,
namsh
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
Hello,
With vim-7.2, I did ':e' to purge undo history to start new
'edit session'(?).
With vim-7.3 (+ 'undofile'):
I guess I could remove a undofile and run ':e' to do this. Maybe
I can make a mapping with some vim script, but...
Is there any easy way to purge 'persistence undo' history?
Dominique Pellé wrote:
Christian Brabandt wrote:
Hi SungHyun!
On Do, 03 Jun 2010, SungHyun Nam wrote:
With vim-7.3 (+ 'undofile'):
I guess I could remove a undofile and run ':e' to do this. Maybe
I can make a mapping with some vim script, but...
Is there any easy way to purge 'persistence
Hello,
With the attached files (vimrc and mb.txt), if I open the mb.txt
and just type A,
gvim -u vimrc -U NONE --noplugin mb.txt
A,
Now, I should saw (X = cursor):
,X
But, I saw
, X
It occurs on 3 different versions of gvim,
win32/cygwin-gtk2/linux-gtk2. I
Steve Hall wrote:
From: Bram Moolenaar, Wed, February 24, 2010 9:48 am
Patch 7.2.374
Problem: Ruby eval() doesn't understand Vim types.
Solution: Add the vim_to_ruby() function. (George Gensure)
Files: src/eval.c, src/if_ruby.c
I'm still seeing build errors with Windows/Cygwin related to
Bram Moolenaar wrote:
Dominique Pelle wrote:
I notice that I cannot compile latest Vim-7.2.166 with +hangul_input
feature on Linux x86.
In :help hangul it says to configure Vim as follows:
./configure --with-x --enable-multibyte --enable-fontset --enable-hangulinput
But when doing
Hello,
Adding fillowing lines to a makefile broke syntax highlighting.
a := $(subst ',,$(flags))
b := $(subst ,,$(flags))
Can this be fixed?
Regards,
namsh
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit
PM, SungHyun Nam [EMAIL PROTECTED] wrote:
mattn wrote:
Yes, my solution is the fixing of above. CursorIM is getting
status of
IM from im_get_status().
But vim should set status of preediting for CursorIM. My roughly
patch
is fixing this.
I am somewhat confused. Did you
Tony Mechelynck wrote:
On 02/07/08 06:23, SungHyun Nam wrote:
Hello,
My settings are:
---
$ echo $LANG
$ echo $GTK_IM_MODULE
hangul2
$ echo $XMODIFIERS
$
I think LANG does not affect cygwin. Instead windows's current
codepage
Tony Mechelynck wrote:
On 02/07/08 11:50, mattn wrote:
At the first, I explain the current state of Vim and IM.
Vim is supporting some GUI interface.
* Windows
* Mac
* Xaw
* GTK
* etc...
And Vim is supporting some IM on the above.
* Windows - WindowsIME
* Mac - MacIME
mattn wrote:
Yes, my solution is the fixing of above. CursorIM is getting status of
IM from im_get_status().
But vim should set status of preediting for CursorIM. My roughly patch
is fixing this.
I am somewhat confused. Did you check my patch I sent out?
I read your mail that your
Hello,
I noticed the Cursor and CursorIM color is not displayed correctly in
VIM 7.2a.
VIM 7.1.xxx (Last xxx was 330) worked as expected.
For the VIM 7.2a;
1. run gvim - 'Cursor' color
2. type 'i' - 'Cursor' color
3. type imak (s-space) - 'CursorIM' color
I can
Bram Moolenaar wrote:
SungHyun Nam wrote:
I noticed the Cursor and CursorIM color is not displayed correctly in
VIM 7.2a.
VIM 7.1.xxx (Last xxx was 330) worked as expected.
For the VIM 7.2a;
1. run gvim - 'Cursor' color
2. type 'i' - 'Cursor' color
3. type imak (s-space
/share/locale
Regards.
namsh
mattn wrote:
SungHyun Nam, more question.
what $LANG?
what $GTK_IM_MODULE?
what $XMODIFIERS
Thanks.
On Wed, Jul 2, 2008 at 10:28 AM, SungHyun Nam [EMAIL PROTECTED]
wrote:
mattn wrote:
Hmm, it seems that current code was broken for japanese also
Tony Mechelynck wrote:
Frodak Baksik wrote:
On 8/24/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
Sorry if you see this twice: after more than 3 hours I'm not seeing it (nor
any reply to it) on the group.
Frodak Baksik wrote:
[...]
These types of issues have been discussed before on the
61 matches
Mail list logo
