Edward L. Fox wrote:
> Hi all Chinese, Taiwanese, Japanese and Korean users,
>
> (cross-posting to vim_multibyte)
>
> On 9/1/07, Bram Moolenaar <Bram@...> wrote:
>
>> [...]
>> Looks OK to me.
>>
>> Can we do the same for cp950, considering it equal to big5?
>>
>
> Please help me checking these:
>
> cp932 => "Shift_JIS" (Japanese)
> cp936 => "GBK" (Chinese)
> cp949 => "euc-kr" (Korean) ??? Is this correct?
> cp950 => "Big5" (Taiwanese)
>
> Are those above correct? If so, I'll make the "official" patch soon.
>
>
>> [...]
>>
>
> Regards,
>
> Edward
>
> >
>
>
>

I know on Windows cp936 is mostly the same as GBK.

--
                                                            Fan Decheng
                                                       dtsfan@...



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 9/1/07, ���³� <dtsfan@...> wrote:
> [...]
>
> I know on Windows cp936 is mostly the same as GBK.

Yes. In fact cp936 *is* GBK. I'm caring about the remaining code
pages' charset names, especially Korean, I'm quite uncertain about
that.

>
> --
>                                                            Fan Decheng
>                                                       dtsfan@...
>
>
>

Edward

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Edward L. Fox wrote:

> Hi all Chinese, Taiwanese, Japanese and Korean users,
>
> (cross-posting to vim_multibyte)
>
> On 9/1/07, Bram Moolenaar <Bram@...> wrote:
> > [...]
> > Looks OK to me.
> >
> > Can we do the same for cp950, considering it equal to big5?
>
> Please help me checking these:
>
> cp932 => "Shift_JIS" (Japanese)
> cp936 => "GBK" (Chinese)
> cp949 => "euc-kr" (Korean) ??? Is this correct?
> cp950 => "Big5" (Taiwanese)
>
> Are those above correct? If so, I'll make the "official" patch soon.

We already recognize cp949 and cp936.  cp932 was just added, I suggested
recognizing cp950 as "big5".

--
This is an airconditioned room, do not open Windows.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi gang,

I really love text objects. I wish there were more of them. In
particular, one for /-delimited strings. These come up a lot in Perl:

if ($foo =~ /blah blah blah/)
($hobbit = $lotr) =~ s/Bilbo/Frodo/g;
for (qw/foo bar baz/)
print q/ both ' kinds of " /;

So I wrote a new text object to match these kinds of strings. It was
literally a one line change. :)

I think I added all the necessary documentation, let me know if I
missed a spot. In the todo file there is an item for a different kind
of / text object, one that has to do with searches. I changed that
from 'a/' and 'i/' to 'an' and 'in'.

Shawn M Moore

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

sc wrote:

>charles--
>
>again i find myself struggling with netrw
>
>i used to love it for directory navigation and finding
>things, but have come to hate the way it mangles my session
>settings, specifically formatoptions
>
>

v112b shouldn't be changing your format options.

>i went the extra mile to get v112b off your web site,
>de-install the v110 that was giving me fits, and install
>v112b in my ~/.vim so it wouldn't get whacked
>
>that was several weeks ago
>
>what's happening now is that every time i build and install a
>new patch level, v110 gets put back in place on my
>/usr/local/share/vim/vim71, and vim searches that first when
>coming up, effectively making my v112b invisible to vim
>
>

Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its
first entry, as it should.  So I think you should figure out why your
runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile?
Normally the netrw in your ~/.vim should be loaded first and thereby
prevent the loading of the system netrw (ie. prevent the loading of
v110), so if you get your runtimepath issue worked out netrw v112b
should come up even though the /usr/local/share/vim/vim71 still has v110.

>do i need to write a script to whack the netrws on
>/usr/local/share and run it at the tail end of my install
>script, or do you have a better suggestion?
>
>

Fix your runtimepath!  Its probably the easiest.

Regards,
Chip Campbell



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sat, Sep 01, 2007 at 06:29:59PM -0400, Charles E. Campbell, Jr. wrote:
>
> sc wrote:
>
> >charles--
> >
> >again i find myself struggling with netrw
> >
> >i used to love it for directory navigation and finding
> >things, but have come to hate the way it mangles my session
> >settings, specifically formatoptions

> v112b shouldn't be changing your format options.

indeed, when i can get it to load, it works great, and i am
using it all the more now, but keeping an eye on it

> >i went the extra mile to get v112b off your web site,
> >de-install the v110 that was giving me fits, and install
> >v112b in my ~/.vim so it wouldn't get whacked
> >
> >that was several weeks ago
> >
> >what's happening now is that every time i build and install a
> >new patch level, v110 gets put back in place on my
> >/usr/local/share/vim/vim71, and vim searches that first when
> >coming up, effectively making my v112b invisible to vim

> Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its
> first entry, as it should.  So I think you should figure out why your
> runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile?

no, i do nothing to rtp or runtimepath in either .vimrc or
.gvimrc

> Normally the netrw in your ~/.vim should be loaded first and thereby
> prevent the loading of the system netrw (ie. prevent the loading of
> v110), so if you get your runtimepath issue worked out netrw v112b
> should come up even though the /usr/local/share/vim/vim71 still has v110.

> >do i need to write a script to whack the netrws on
> >/usr/local/share and run it at the tail end of my install
> >script, or do you have a better suggestion?

> Fix your runtimepath!  Its probably the easiest.

i am officially flummoxed

when i look at :set rtp? i see:

runtimepath=~/.vim,/usr/local/share/vim/vimfiles,/usr/local/share/vim/vim71,/usr\
/local/share/vim/vimfiles/after,~/.vim/after

yet before i wrote and ran my netrw whacker it was loading
v110 -- obviously, ~/.vim is the first thing in 'rtp', so i
too think it should have been grabbing v112b from there

it's as if something were steering it to /usr/local/share

--
sc

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Charles E. Campbell, Jr. wrote:
> sc wrote:
>
>> charles--
>>
>> again i find myself struggling with netrw
>>
>> i used to love it for directory navigation and finding
>> things, but have come to hate the way it mangles my session
>> settings, specifically formatoptions
>>
>>
>
> v112b shouldn't be changing your format options.
>
>> i went the extra mile to get v112b off your web site,
>> de-install the v110 that was giving me fits, and install
>> v112b in my ~/.vim so it wouldn't get whacked
>>
>> that was several weeks ago
>>
>> what's happening now is that every time i build and install a
>> new patch level, v110 gets put back in place on my
>> /usr/local/share/vim/vim71, and vim searches that first when
>> coming up, effectively making my v112b invisible to vim
>>
>>
>
> Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its
> first entry, as it should.  So I think you should figure out why your
> runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile?
> Normally the netrw in your ~/.vim should be loaded first and thereby
> prevent the loading of the system netrw (ie. prevent the loading of
> v110), so if you get your runtimepath issue worked out netrw v112b
> should come up even though the /usr/local/share/vim/vim71 still has v110.
>
>> do i need to write a script to whack the netrws on
>> /usr/local/share and run it at the tail end of my install
>> script, or do you have a better suggestion?
>>
>>
>
> Fix your runtimepath!  Its probably the easiest.
>
> Regards,
> Chip Campbell

On Linux, the default value is

	 ~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after

or its equivalent after expanding ~ $VIM and $VIMRUNTIME. Any 'runtimepath'
directory other than $VIMRUNTIME need only be created when you have something
to put into it; but in order to install a vimball you need file- and
directory-creation privileges to directories early in 'runtimepath' and their
immediate parent. Normally you ought to have all permissions over your $HOME
directory and anything below it, so that's no problem.

You (sc) need a _very_ good reason to change 'runtimepath'; and $VIMRUNTIME
should be in the middle, not at one end.

Full-fledged scripts other than those distributed together with Vim should go
early in 'runtimepath', either under $VIM/vimfiles/ (for system-wide use) or
under ~/.vim/ (for single-user use).


Best regards,
Tony.
--
Vote for ME -- I'm well-tapered, half-cocked, ill-conceived and
TAX-DEFERRED!

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sun, Sep 02, 2007 at 12:58:46AM +0200, Tony Mechelynck wrote:
>
> Charles E. Campbell, Jr. wrote:
> > sc wrote:
> >
> >> charles--
> >>
> >> again i find myself struggling with netrw
> >>
> >> i used to love it for directory navigation and finding
> >> things, but have come to hate the way it mangles my session
> >> settings, specifically formatoptions
> >
> > v112b shouldn't be changing your format options.
> >
> >> i went the extra mile to get v112b off your web site,
> >> de-install the v110 that was giving me fits, and install
> >> v112b in my ~/.vim so it wouldn't get whacked
> >>
> >> that was several weeks ago
> >>
> >> what's happening now is that every time i build and install a
> >> new patch level, v110 gets put back in place on my
> >> /usr/local/share/vim/vim71, and vim searches that first when
> >> coming up, effectively making my v112b invisible to vim

> > Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its
> > first entry, as it should.  So I think you should figure out why your
> > runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile?
> > Normally the netrw in your ~/.vim should be loaded first and thereby
> > prevent the loading of the system netrw (ie. prevent the loading of
> > v110), so if you get your runtimepath issue worked out netrw v112b
> > should come up even though the /usr/local/share/vim/vim71 still has v110.
> >
> >> do i need to write a script to whack the netrws on
> >> /usr/local/share and run it at the tail end of my install
> >> script, or do you have a better suggestion?

> > Fix your runtimepath!  Its probably the easiest.
> >
> > Regards,
> > Chip Campbell
>
> On Linux, the default value is
>
>  ~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after
>
> or its equivalent after expanding ~ $VIM and $VIMRUNTIME. Any 'runtimepath'
> directory other than $VIMRUNTIME need only be created when you have something
> to put into it; but in order to install a vimball you need file- and
> directory-creation privileges to directories early in 'runtimepath' and their
> immediate parent. Normally you ought to have all permissions over your $HOME
> directory and anything below it, so that's no problem.
>
> You (sc) need a _very_ good reason to change 'runtimepath'; and $VIMRUNTIME
> should be in the middle, not at one end.

waaaa!  i'm NOT!  i swear!!  there's something truly weird
that was causing vim to find netrw on /usr/local/share, in
spite of my

  
runtimepath=~/.vim,/usr/local/share/vim/vimfiles,/usr/local/share/vim/vim71,/usr\
/local/share/vim/vimfiles/after,~/.vim/after

--
sc

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

sc wrote:
> On Sun, Sep 02, 2007 at 12:58:46AM +0200, Tony Mechelynck wrote:
>> Charles E. Campbell, Jr. wrote:
>>> sc wrote:
>>>
>>>> charles--
>>>>
>>>> again i find myself struggling with netrw
>>>>
>>>> i used to love it for directory navigation and finding
>>>> things, but have come to hate the way it mangles my session
>>>> settings, specifically formatoptions
>>> v112b shouldn't be changing your format options.
>>>
>>>> i went the extra mile to get v112b off your web site,
>>>> de-install the v110 that was giving me fits, and install
>>>> v112b in my ~/.vim so it wouldn't get whacked
>>>>
>>>> that was several weeks ago
>>>>
>>>> what's happening now is that every time i build and install a
>>>> new patch level, v110 gets put back in place on my
>>>> /usr/local/share/vim/vim71, and vim searches that first when
>>>> coming up, effectively making my v112b invisible to vim
>
>>> Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its
>>> first entry, as it should.  So I think you should figure out why your
>>> runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile?
>>> Normally the netrw in your ~/.vim should be loaded first and thereby
>>> prevent the loading of the system netrw (ie. prevent the loading of
>>> v110), so if you get your runtimepath issue worked out netrw v112b
>>> should come up even though the /usr/local/share/vim/vim71 still has v110.
>>>
>>>> do i need to write a script to whack the netrws on
>>>> /usr/local/share and run it at the tail end of my install
>>>> script, or do you have a better suggestion?
>
>>> Fix your runtimepath!  Its probably the easiest.
>>>
>>> Regards,
>>> Chip Campbell
>> On Linux, the default value is
>>
>>  ~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after
>>
>> or its equivalent after expanding ~ $VIM and $VIMRUNTIME. Any 'runtimepath'
>> directory other than $VIMRUNTIME need only be created when you have something
>> to put into it; but in order to install a vimball you need file- and
>> directory-creation privileges to directories early in 'runtimepath' and their
>> immediate parent. Normally you ought to have all permissions over your $HOME
>> directory and anything below it, so that's no problem.
>>
>> You (sc) need a _very_ good reason to change 'runtimepath'; and $VIMRUNTIME
>> should be in the middle, not at one end.
>
> waaaa!  i'm NOT!  i swear!!  there's something truly weird
> that was causing vim to find netrw on /usr/local/share, in
> spite of my
>
>  
runtimepath=~/.vim,/usr/local/share/vim/vimfiles,/usr/local/share/vim/vim71,/usr\
/local/share/vim/vimfiles/after,~/.vim/after
>

Yes, that's the default value.

Is the more recent version installed in the plugin/ and autoload/ subdirs of
one of the above? Not under ~/.vim for a different user (which would have a
different home dir)? Nor in an after-directory? And you _do_ have read/write
permission on the files and their directories, don't you?

Oh, and, you aren't overriding $VIM and/or $VIMRUNTIME are you? (I suppose
not, but trying to cover all bases). You ought to see

	 :echo $VIM
/usr/local/share/vim
	 :echo $VIMRUNTIME
/usr/local/share/vim/vim71


Best regards,
Tony.
--
The economy depends about as much on economists as the weather does on
weather forecasters.
		 -- Jean-Paul Kauffmann

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

charles--

again i find myself struggling with netrw

i used to love it for directory navigation and finding
things, but have come to hate the way it mangles my session
settings, specifically formatoptions

i went the extra mile to get v112b off your web site,
de-install the v110 that was giving me fits, and install
v112b in my ~/.vim so it wouldn't get whacked

that was several weeks ago

what's happening now is that every time i build and install a
new patch level, v110 gets put back in place on my
/usr/local/share/vim/vim71, and vim searches that first when
coming up, effectively making my v112b invisible to vim

do i need to write a script to whack the netrws on
/usr/local/share and run it at the tail end of my install
script, or do you have a better suggestion?

--
sc

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sun, Sep 02, 2007 at 01:32:52AM +0200, Tony Mechelynck wrote:
>
> sc wrote:
> > On Sun, Sep 02, 2007 at 12:58:46AM +0200, Tony Mechelynck wrote:
> >> Charles E. Campbell, Jr. wrote:
> >>> sc wrote:
> >>>
> >>>> charles--
> >>>>
> >>>> again i find myself struggling with netrw
> >>>>
> >>>> i used to love it for directory navigation and finding
> >>>> things, but have come to hate the way it mangles my session
> >>>> settings, specifically formatoptions
> >>> v112b shouldn't be changing your format options.
> >>>
> >>>> i went the extra mile to get v112b off your web site,
> >>>> de-install the v110 that was giving me fits, and install
> >>>> v112b in my ~/.vim so it wouldn't get whacked
> >>>>
> >>>> that was several weeks ago
> >>>>
> >>>> what's happening now is that every time i build and install a
> >>>> new patch level, v110 gets put back in place on my
> >>>> /usr/local/share/vim/vim71, and vim searches that first when
> >>>> coming up, effectively making my v112b invisible to vim
> >
> >>> Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its
> >>> first entry, as it should.  So I think you should figure out why your
> >>> runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile?
> >>> Normally the netrw in your ~/.vim should be loaded first and thereby
> >>> prevent the loading of the system netrw (ie. prevent the loading of
> >>> v110), so if you get your runtimepath issue worked out netrw v112b
> >>> should come up even though the /usr/local/share/vim/vim71 still has v110.
> >>>
> >>>> do i need to write a script to whack the netrws on
> >>>> /usr/local/share and run it at the tail end of my install
> >>>> script, or do you have a better suggestion?
> >
> >>> Fix your runtimepath!  Its probably the easiest.
> >>>
> >>> Regards,
> >>> Chip Campbell
> >> On Linux, the default value is
> >>
> >>  ~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after
> >>
> >> or its equivalent after expanding ~ $VIM and $VIMRUNTIME. Any 'runtimepath'
> >> directory other than $VIMRUNTIME need only be created when you have
something
> >> to put into it; but in order to install a vimball you need file- and
> >> directory-creation privileges to directories early in 'runtimepath' and
their
> >> immediate parent. Normally you ought to have all permissions over your
$HOME
> >> directory and anything below it, so that's no problem.
> >>
> >> You (sc) need a _very_ good reason to change 'runtimepath'; and $VIMRUNTIME
> >> should be in the middle, not at one end.
> >
> > waaaa!  i'm NOT!  i swear!!  there's something truly weird
> > that was causing vim to find netrw on /usr/local/share, in
> > spite of my
> >
> >  
runtimepath=~/.vim,/usr/local/share/vim/vimfiles,/usr/local/share/vim/vim71,/usr\
/local/share/vim/vimfiles/after,~/.vim/after
> >
>
> Yes, that's the default value.
>
> Is the more recent version installed in the plugin/ and autoload/ subdirs of
> one of the above? Not under ~/.vim for a different user (which would have a
> different home dir)? Nor in an after-directory? And you _do_ have read/write
> permission on the files and their directories, don't you?

/home/scott/.vim> find . -name "*netrw*" -print
./doc/pi_netrw.txt
./netrw.vba
./syntax/netrw.vim
./autoload/netrw.vim
./autoload/netrwSettings.vim
./autoload/netrwFileHandlers.vim
./plugin/netrwPlugin.vim

which is indeed v112b, as witness the fact that after running
my:

/home/scott/.build/vim> cat wobn
#!/bin/bash
##
##  whack old buggy netrw -- must run as root
##
for f in $(find /usr/local/share/vim/vim71 -name "*netrw*" -print)
do
     rm -i $f
done

then v112b is what comes up when i try to :Explore

i am the only user on this box:

/home> ls -Al
total 24
drwx------  2 root  root  16384 Apr 11 14:29 lost+found
drwxr-xr-x 89 scott users  4096 Sep  1 18:46 scott
/home>

now what else did you ask?  read/write permissions on the
files and their directories?

files first:

/home/scott/.vim> for f in $(find . -name "*netrw*" -print)
> do
> ls -l $f
> done
-rw-r--r-- 1 scott users 103511 Aug 22 15:58 ./doc/pi_netrw.txt
-rw-r--r-- 1 scott users 365991 Aug 22 15:28 ./netrw.vba
-rw-r--r-- 1 scott users 3152 Aug 22 15:58 ./syntax/netrw.vim
-rw-r--r-- 1 scott users 231897 Aug 22 15:58 ./autoload/netrw.vim
-rw-r--r-- 1 scott users 8069 Aug 22 15:58 ./autoload/netrwSettings.vim
-rw-r--r-- 1 scott users 10226 Aug 22 15:58 ./autoload/netrwFileHandlers.vim
-rw-r--r-- 1 scott users 8875 Aug 22 15:58 ./plugin/netrwPlugin.vim

owned by me and writable by me

now for the directories:

/home/scott/.vim> ls -ld * | grep '^d'
drwxr-xr-x 2 scott users   4096 Sep  1 13:07 autoload
drwxr-xr-x 2 scott users   4096 Aug 22 15:58 doc
drwxr-xr-x 2 scott users   4096 Sep  1 13:04 plugin
drwxr-xr-x 2 scott users   4096 Sep  1 13:05 syntax

> Oh, and, you aren't overriding $VIM and/or $VIMRUNTIME are you? (I suppose
> not, but trying to cover all bases). You ought to see
>
>  :echo $VIM
> /usr/local/share/vim
>  :echo $VIMRUNTIME
> /usr/local/share/vim/vim71

indeed -- :echo $VIM yeilds:

/usr/local/share/vim

and :echo $VIMRUNTIME yeilds:

/usr/local/share/vim/vim71

this is a true mystery, but one i hope no-one loses any sleep
over -- i've put 'wobn' in my install script, which i run as
root, so i've got a painless work-around -- i may even get to
trust it enough to take the '-i' off the 'rm' -- not soon,
but eventually -- maybe

--
sc

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 31/08/07, sc <toothpik@...> wrote:

> any time i see one of those i don't already know (more rare
> all the time) i google for it

True


> if you want vim embedded for email, you want mutt

From everything I have seen of both pine and mutt, i prefer the
former. What benevit does embedded vim have in mutt over pine?



Richard

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 31/08/07, krischik <krischik@...> wrote:

> On Aug 30, 2:46 pm, hermi...@... wrote:

> > PS: As "mode" already means something in Vim context, I do not really
> > like this new use of the term.
>
> Got an alternative name?

Environment? Framework? Package? Helper?


Richard

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sep 2, 4:58 pm, "Richard Hartmann" <richih.mailingl...@...>
wrote:
> On 31/08/07, krischik <krisc...@...> wrote:
>
> > On Aug 30, 2:46 pm, hermi...@... wrote:
> > > PS: As "mode" already means something in Vim context, I do not really
> > > like this new use of the term.
>
> > Got an alternative name?
>
> Environment? Framework? Package? Helper?

I like "Framework" best.

Martin


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi Matsumoto and Bram,

On 9/1/07, Bram Moolenaar <Bram@...> wrote:
>
> Edward L. Fox wrote:
>
> > Hi all Chinese, Taiwanese, Japanese and Korean users,
> >
> > (cross-posting to vim_multibyte)
> >
> > On 9/1/07, Bram Moolenaar <Bram@...> wrote:
> > > [...]
> > > Looks OK to me.
> > >
> > > Can we do the same for cp950, considering it equal to big5?
> >
> > Please help me checking these:
> >
> > cp932 => "Shift_JIS" (Japanese)
> > cp936 => "GBK" (Chinese)
> > cp949 => "euc-kr" (Korean) ??? Is this correct?
> > cp950 => "Big5" (Taiwanese)
> >
> > Are those above correct? If so, I'll make the "official" patch soon.
>
> We already recognize cp949 and cp936.  cp932 was just added, I suggested
> recognizing cp950 as "big5".

Here is a quite-simple-and-small patch according to your request.

--- 2html.vim   2007-05-09 12:06:26.000000000 +0800
+++ /tmp/2html.vim      2007-09-02 23:35:55.000000000 +0800
@@ -162,9 +162,9 @@
      let s:html_encoding = 'iso-8859-1'
    elseif s:vim_encoding =~ "^cp12"
      let s:html_encoding = substitute(s:vim_encoding, 'cp', 'windows-', '')
-  elseif s:vim_encoding == 'sjis'
+  elseif s:vim_encoding == 'sjis' || s:vim_encoding == 'cp932'
      let s:html_encoding = 'Shift_JIS'
-  elseif s:vim_encoding == 'big5'
+  elseif s:vim_encoding == 'big5' || s:vim_encoding == 'cp950'
      let s:html_encoding = "Big5"
    elseif s:vim_encoding == 'euc-cn'
      let s:html_encoding = 'GB_2312-80'


>
> --
> This is an airconditioned room, do not open Windows.
>
>  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
> ///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\        download, build and distribute -- http://www.A-A-P.org        ///
>  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///
>

Best regards,

Edward L. Fox

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 9/2/07, krischik <krischik@...> wrote:
>
> On Sep 2, 4:58 pm, "Richard Hartmann" <richih.mailingl...@...>
> wrote:
> > On 31/08/07, krischik <krisc...@...> wrote:
> >
> > > On Aug 30, 2:46 pm, hermi...@... wrote:
> > > > PS: As "mode" already means something in Vim context, I do not really
> > > > like this new use of the term.
> >
> > > Got an alternative name?
> >
> > Environment? Framework? Package? Helper?
>
> I like "Framework" best.

Why not use some geeky expression to make the name *unique*?

I suggest calling it "superior".

>
> Martin
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hello fellow Vimmers,

I know you can set the amount of time that a character-pair match is
highlighted using the "matchtime" variable, but I am wondering if there is a
way to set a delay that would expire *before* the pair is highlighted.  The
reason I ask is the following use case:

When using an XML file, I add <:> to matchpairs.  But when navigating
line-by-line in a large series like --

	 <.../>
	 <.../>
	 <.../>

Etc -- Vim gets laggy because it's continually looking for and highlighting
the matching angle brackets.  So I was wondering if there was a delay
anywhere that could be set before the search and highlight is actually
attempted, which would make single-line navigation in this kind of situation
much faster.

--
Taylor Venable
taylor@...
http://www.metasyntax.net/

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sat 1-Sep-07 1:39pm -0600, sc wrote:

> again i find myself struggling with netrw

This may be unrelated to sc's problem, but happened to me in
my Windows installation.

I removed all *netrw* files from my $vimruntime and
installed the latest (112b) there.  It worked fine.
However, I later updated my runtime files from the ftp site
(the update only copies new files and only overwrites
existing files if the ftp file has a newer date).

After the update, I noticed that I was back to 110.

Looking around at the ftp site, I noticed that there are two
very similar versions of the autoload file netrw.vim on the
ftp site.  One is in the autoload/ directory and starts
with:

" netrw.vim: Handles file transfer and remote directory listing across
"            AUTOLOAD SECTION
" Date:         Jun 20, 2007
" Version:      110k    NOT RELEASED

The other is in the plugin/ directory and starts with:

" netrw.vim: Handles file transfer and remote directory listing across
"            AUTOLOAD SECTION
" Date:         Jun 21, 2007
" Version:      110

These two files are identical, except for the differences in
those lines and the line starting with: let g:loaded_netrw =

So this second version is getting written to the plugin\
directory of my runtime files and gives me the version 110
announcement.

The netrw.vim file should be removed from the plugin/
directory of the ftp site.

A working solution, until this is done, is to create a
current dated empty file called netrw.vim in the plugin
directory of your runtime.  That way the rouge netrw.vim
will not be written there when you update your runtime.

--
Best regards,
Bill


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Bill McCarthy wrote:
> On Sat 1-Sep-07 1:39pm -0600, sc wrote:
>
>> again i find myself struggling with netrw
>
> This may be unrelated to sc's problem, but happened to me in
> my Windows installation.
>
> I removed all *netrw* files from my $vimruntime and
> installed the latest (112b) there.  It worked fine.
> However, I later updated my runtime files from the ftp site
> (the update only copies new files and only overwrites
> existing files if the ftp file has a newer date).
>
> After the update, I noticed that I was back to 110.
>
> Looking around at the ftp site, I noticed that there are two
> very similar versions of the autoload file netrw.vim on the
> ftp site.  One is in the autoload/ directory and starts
> with:
>
> " netrw.vim: Handles file transfer and remote directory listing across
> "            AUTOLOAD SECTION
> " Date:         Jun 20, 2007
> " Version:      110k    NOT RELEASED
>
> The other is in the plugin/ directory and starts with:
>
> " netrw.vim: Handles file transfer and remote directory listing across
> "            AUTOLOAD SECTION
> " Date:         Jun 21, 2007
> " Version:      110
>
> These two files are identical, except for the differences in
> those lines and the line starting with: let g:loaded_netrw =
>
> So this second version is getting written to the plugin\
> directory of my runtime files and gives me the version 110
> announcement.
>
> The netrw.vim file should be removed from the plugin/
> directory of the ftp site.
>
> A working solution, until this is done, is to create a
> current dated empty file called netrw.vim in the plugin
> directory of your runtime.  That way the rouge netrw.vim

s/rouge/rogue
" this is not about cosmetics, jewellery or Canadian football

> will not be written there when you update your runtime.
>

On Unix-like systems, rsync (with --delete) will make the destination tree
identical to the source tree regardless of anteriority, so the above won't
work there. The following will (after $VIMRUNTIME/plugin/netrw.vim is deleted
once by hand):

#!/bin/bash
rsync -avzcP --delete --exclude="/dos/" ftp.nluug.nl::Vim/runtime/ ./runtime/
2>&1 | tee rsync.log
rm -vf runtime/plugin/netrw.vim 2>&1 | tee -a rsync.log
vim -es -u NONE -c '%s/^.*\r//' -cx rsync.log
make -C src installruntime 2>&1 | tee instrt.log

Notes:
1. In case your mailer or mine added spurious line breaks: the long line
starting "rsync" includes everything up to but not including the line starting
"rm".
2. the "vim" step cleans up the log by removing "nonspacing" lines --
temporary "progress reports" which were overwritten on the screen
3. the "make installruntime" step only needs to be done when:
    a) there are changed files other than doc/tags and plugin/netrw.vim, and
    b) you aren't about to compile a new patchlevel of Vim (in which case the
"make install" which follows it will take care of runtime files anyway).


Best regards,
Tony.
--
Did you know ...

That no-one ever reads these things?

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hello,

krischik <krischik@...> wrote:

> On Aug 30, 2:46 pm, hermi...@... wrote:
>
> > compiler plugins are a bit independent of the filetype.
> > For instance, there are several C&C++ compilers that produce errors in
> > different formats.  And I'm quite sure this is also true with other
> > languages. Moreover, sometimes we must filter the outputs because of
> > intermediary tools that have nothing to do with the language (-> Cygwin,
> > ant, ...)
>
> Less independed then you think. The Ada-Mode comes with two compiler
> plugin (GNAT and DecAda) and depending on the setting of
> g:ada_default_compiler one of them is loaded when an Ada source is
> edited.

> I see this an an improvement to the default behaviour where by default
> no compiler plugin is loaded and you have to do it all yourself by
> automcd magic in your .vimrc. After all you don't want to load a
> compiler setup when you are working on unrelated files.

I use some automagic commands (and two plugins of mine) to load compiler plugins
according to the project (defined as directories on the disk) I'm working on.

> > syntax+indent+fold+completion plugins can, and should, be distributed
> > with vim.
>
> [...]
> > Regarding ftplugins, well a minimum is to be distributed with vim as it
> > already is today.
>
> But they still need to be maintained and improved.

Indeed. Just out of curiousity, how often do they change between two versions of
Vim ?

> > PS: As "mode" already means something in Vim context, I do not really
> > like this new use of the term.
>
> Got an alternative name?

I wish I had :-(
It would be something with "filetype" I guess.

--
Luc Hermitte

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

hermitte@... wrote:
> Hello,
>
> krischik <krischik@...> wrote:
>
>> On Aug 30, 2:46 pm, hermi...@... wrote:
>>> PS: As "mode" already means something in Vim context, I do not really
>>> like this new use of the term.
>> Got an alternative name?
>
> I wish I had :-(
> It would be something with "filetype" I guess.

The TextMate editor on OS X uses the term "bundle" for this kind of
thing.  Apple defines a bundle[1] as "a directory in the file system
that contains executable code and related resources".  I don't know if
it would be confusing to OS X developers to reuse the term "bundle" for
your proposed "Mode" concept in Vim; but then again, Mac users are in
the minority (especially Mac developers).

Other possibilities, in no particular order:

- filetype kit
- filetype package
- filetype pack
- filetype suite

I've been using the following sentence in my head to see how these sound:

      "Download and install the ADA (blank)."

Michael Henry

[1]: See "Bundles" section on this page:
http://developer.apple.com/documentation/Porting/Conceptual/win32porting/Article\
s/intern.html


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 03/09/07, Michael Henry <vim@...> wrote:

> - filetype suite

I think filetype suite or filetype suite or, even better,
filetype bundle have a nice ring to them.

'Perl filetype bundle' - I like that.

The other thing is environment..

'[VIM] Perl environment' - that also tells you at a glance what it is
about


Richard

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sep 1, 6:56 pm, Sartak <sar...@...> wrote:
> Hi gang,
>
> I really love text objects. I wish there were more of them. In
> particular, one for /-delimited strings. These come up a lot in Perl:
>
> if ($foo =~ /blah blah blah/)
> ($hobbit = $lotr) =~ s/Bilbo/Frodo/g;
> for (qw/foo bar baz/)
> print q/ both ' kinds of " /;
>
> So I wrote a new text object to match these kinds of strings. It was
> literally a one line change. :)
>
> I think I added all the necessary documentation, let me know if I
> missed a spot. In the todo file there is an item for a different kind
> of / text object, one that has to do with searches. I changed that
> from 'a/' and 'i/' to 'an' and 'in'.
>
> Shawn M Moore
>
>  slash-object.diff
> 3KDownload

My opinion : Why hardcode something, which is easily done with a
mapping ?
Also, '/' is just one of many possible perl delimiter.

-ap


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 9/3/07, ap <politza@...> wrote:
>
>
>
> On Sep 1, 6:56 pm, Sartak <sar...@...> wrote:
> > Hi gang,
> >
> > I really love text objects. I wish there were more of them. In
> > particular, one for /-delimited strings. These come up a lot in Perl:
> >
> > if ($foo =~ /blah blah blah/)
> > ($hobbit = $lotr) =~ s/Bilbo/Frodo/g;
> > for (qw/foo bar baz/)
> > print q/ both ' kinds of " /;
> >
> > So I wrote a new text object to match these kinds of strings. It was
> > literally a one line change. :)
> >
> > I think I added all the necessary documentation, let me know if I
> > missed a spot. In the todo file there is an item for a different kind
> > of / text object, one that has to do with searches. I changed that
> > from 'a/' and 'i/' to 'an' and 'in'.
> >
> > Shawn M Moore
> >
> >  slash-object.diff
> > 3KDownload
>
> My opinion : Why hardcode something, which is easily done with a
> mapping ?

Because hardcoding was one new line of code. :) And it wasn't even a
particularly difficult line, just adding "case '/'".

> Also, '/' is just one of many possible perl delimiter.

Oh, I'm well aware, but I use /.../ a lot.

>
> -ap
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sep 3, 11:34 pm, Sartak <sar...@...> wrote:
> On 9/3/07, ap <poli...@...> wrote:
>
>
>
> > On Sep 1, 6:56 pm, Sartak <sar...@...> wrote:
> > > Hi gang,
>
> > > I really love text objects. I wish there were more of them. In
> > > particular, one for /-delimited strings. These come up a lot in Perl:
>
> > > if ($foo =~ /blah blah blah/)
> > > ($hobbit = $lotr) =~ s/Bilbo/Frodo/g;
> > > for (qw/foo bar baz/)
> > > print q/ both ' kinds of " /;
>
> > > So I wrote a new text object to match these kinds of strings. It was
> > > literally a one line change. :)
>
> > > I think I added all the necessary documentation, let me know if I
> > > missed a spot. In the todo file there is an item for a different kind
> > > of / text object, one that has to do with searches. I changed that
> > > from 'a/' and 'i/' to 'an' and 'in'.
>
> > > Shawn M Moore
>
> > >  slash-object.diff
> > > 3KDownload
>
> > My opinion : Why hardcode something, which is easily done with a
> > mapping ?
>
> Because hardcoding was one new line of code. :) And it wasn't even a
> particularly difficult line, just adding "case '/'".
>
> > Also, '/' is just one of many possible perl delimiter.
>
> Oh, I'm well aware, but I use /.../ a lot.
I mostly use '+' , I want that patched too, please. ;-)
>
> > -ap


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hello Vim users,

So far we only had the possibility to search for scripts on the Vim
website.  Of course you could use your favorite search engine, but then
you would find any type of file, not just Vim scripts.

I have now added a search box to the search page on www.vim.org where
you can specifically search for Vim scripts, anywhere on the internet.
This uses Google Code Search.  It not only finds individual "*.vim"
files but also scripts inside archives.  E.g., in the Vim distribution.

There is one extra special thing: You search with a regexp pattern.
Thus what you type in the search box are not keywords, it is different
from a normal Google search.  For example, you can search for
"python.*indent" and find matches in "Python indent", "GetPythonIndent"
and "python_highlight_indent_errors".  The regexp synax used is Posix,
it's different from Vim regexp.

Try it out on the Vim search page (second box from the top):
        http://www.vim.org/search.php

Happy Vimming!

--
A successful man is one who makes more money than his wife can spend.
A successful woman is one who can find such a man.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi!

> I have now added a search box to the search page on www.vim.org where
> you can specifically search for Vim scripts, anywhere on the internet.
> This uses Google Code Search.  It not only finds individual "*.vim"
> files but also scripts inside archives.  E.g., in the Vim distribution.

This is really great! Thank you very much!

Best wishes,
Georg




--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 9/4/07, Bram Moolenaar <Bram@...> wrote:
<snip>

> I have now added a search box to the search page on www.vim.org where
> you can specifically search for Vim scripts, anywhere on the internet.
> This uses Google Code Search.

Excellent! Thanks Bram.

Regards,
Doug

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

> The MozEx Firefox extension lets you edit textareas with an external editor
> (e.g. vim). I'm a fan.

I've found another FF extension called It's All Text - it allows the same and
it handles character encoding and cooperates nicely with FF. And it works with
FF 1.5 and 2.0

Great for editing wiki pages (for example). I can't imagine my work in wiki
without that extension.

Milan Vancura

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Fri, Aug 31, 2007 at 04:18:57PM +0200, Richard Hartmann wrote:
>
> On 31/08/2007, Tony Mechelynck <antoine.mechelynck@...> wrote:
[...]
> (not as painful as using the GMail interface without fixed width fonts or
> tw=72 which means I need to guess the formatting..) when replying to more
> complex mails.

The MozEx Firefox extension lets you edit textareas with an external editor
(e.g. vim). I'm a fan.

> Richard
--Greg


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---