Gary Johnson | 1 Mar 01:21 2007

Re: Subject: Re: vim on cygwin using win32 clipboard

On 2007-02-28, Frodak Baksik <frodak17 <at> gmail.com> wrote:
> On 2/27/07, Gary Johnson wrote:
> > On 2007-02-15, Frodak Baksik wrote:
> >
> > > Here are all the changes in a single patch.
> > > I'm also posting this to the cygwin-apps mailing list, so if anyone
> > > over there could try it out would be nice.
> >
> > I just applied this patch to the latest Cygwin vim source package,
> > vim-7.0.122-1, and configured it with
> >
> >     ./configure --prefix=/usr/local --without-x --enable-gui=no
> >
> > However, after successfully building a number of .o files, make
> > fails as follows:
> >
> >     $ make
> >     Starting make in the src directory.
> >     If there are problems, cd to the src directory and run make there
> >     cd src && make first
> >     make[1]: Entering directory `/usr/src/vim-7.0.122-1/src'
> >     make[1]: *** No rule to make target `proto/winclip.pro', needed by 
> >     `objects/winclip.o'.  Stop.
> >     make[1]: Leaving directory `/usr/src/vim-7.0.122-1/src'
> >     make: *** [first] Error 2
> >
> > I'm sorry I don't have time to look into it further before I leave
> > for the day.  I hope it's obvious to someone what I've done wrong.
> >
> > Regards,
(Continue reading)

Matthew Woehlke | 1 Mar 01:25 2007
Picon
Picon

Re: Subject: Re: vim on cygwin using win32 clipboard

Gary Johnson wrote:
> It appears that I may need to install the ncurses package and
> reconfigure vim in order to get color.

That would be likely; ncurses is (AFAIK) *much* better than termcap.

--

-- 
Matthew
Obscurity: +5

Michael Schaap | 1 Mar 17:32 2007

Re: Bug: ":confirm w" only works once

On 28-Feb-2007 22:38, Bram Moolenaar wrote:
> Michael Schaap wrote:
>
>   
>> When editing a read-only file, ":confirm w" only works the first time 
>> you use it in a session. The second time you try to use it, you simply 
>> get an error message, as if you didn't use ":confirm".
>> The same problem occurs when using ":set confirm".
>>
>> To recreate:
>>
>> $ echo Hello > hello.txt
>> $ chmod 400 hello.txt
>> $ vim -u NONE hello.txt
>> :set nocompatible " or you won't be able to overwrite at all
>> A, World<Esc>
>> :confirm w
>> 'readonly' option is set for "qq".
>> Do you wish to write anyway?
>> (Y)es, [N]o: y
>> A!<Esc>
>> :confirm w
>> E505: "qq" is read-only (add ! to override)
>>
>> This is using 7.0.203, but it has been happening for quite a while. An 
>> old 6.3 does the same thing.
>>
>> – Michael
>>     
>
(Continue reading)

edfyoungsmor | 1 Mar 17:33 2007
Picon

Re: Bug: ":confirm w" only works once

Die von Ihnen genutzte eMail-Adresse (* <at> youngs.de) existiert nicht oder existiert nicht mehr.

thomas | 1 Mar 18:11 2007
Picon

Bug report: mapping fails with a few characters (i.e.: « :imap ’ foo » fails)

Hi

Mapping seems to be buggy with some characters.
For instance:

:imap ' foo

does not work (the apostrophe is U+2019). If the mapped string
contains this apostrophe but does not begin with it, there is no
problem. For instance, this works:

:imap x' foo

But it is impossible to map a string beginning with this apostrophe,
and the <Char-0x2019> construct does not help. This is weird, because
there is no problem with mapping the usual apostrophe U+0027. Other
paradoxes can be found : It is possible to map the no-break space
(U+00A0) but not its thin version (U+202F), the usual minus sign
(U+002D) but not the en-dash (U+2013) and the em-dash (U+2014).

I first thought vim had a problem with mapping multibyte characters
but it actually deals well with most of them. Any explanation, why the
mapping does not work with some characters?

Thanks for your help

Thomas

Frodak Baksik | 1 Mar 18:13 2007
Picon

Re: Subject: Re: vim on cygwin using win32 clipboard

On 2/28/07, Matthew Woehlke <mw_triad <at> users.sourceforge.net> wrote:
> Gary Johnson wrote:
> > It appears that I may need to install the ncurses package and
> > reconfigure vim in order to get color.
>
> That would be likely; ncurses is (AFAIK) *much* better than termcap.
>
> --
> Matthew
> Obscurity: +5
>
>

Try getting ncurses and gettext libraries.  Both are available
packages in cygwin.

:-)
Frodak

Gary Johnson | 1 Mar 20:57 2007

Re: Subject: Re: vim on cygwin using win32 clipboard

On 2007-03-01, Frodak Baksik <frodak17 <at> gmail.com> wrote:
> On 2/28/07, Matthew Woehlke <mw_triad <at> users.sourceforge.net> wrote:
> > Gary Johnson wrote:
> > > It appears that I may need to install the ncurses package and
> > > reconfigure vim in order to get color.
> >
> > That would be likely; ncurses is (AFAIK) *much* better than termcap.

> Try getting ncurses and gettext libraries.  Both are available
> packages in cygwin.

There are several ncurses packages to choose from, but I finally 
figured out that I needed libncurses-devel, so I installed that, 
reconfigured and rebuilt vim and voila:  color!

It's not as clear to me what I need to resolve these differences:

    36c36
    < +gettext
    ---
    > -gettext
    111c111
    < Linking: gcc   -L/usr/local/lib -o vim.exe       -lncurses  -liconv -lintl        
    ---
    > Linking: gcc   -L/usr/local/lib -o vim.exe       -lncurses  -liconv        

My Cygwin installation already has

    /usr/include/libintl.h
    /usr/lib/libintl.a
(Continue reading)

A.J.Mechelynck | 2 Mar 03:03 2007
Picon

Re: Bug report: mapping fails with a few characters (i.e.: « :imap ’ foo » fails)

thomas wrote:
> Hi
> 
> Mapping seems to be buggy with some characters.
> For instance:
> 
> :imap ' foo
> 
> does not work (the apostrophe is U+2019). If the mapped string
> contains this apostrophe but does not begin with it, there is no
> problem. For instance, this works:
> 
> :imap x' foo
> 
> But it is impossible to map a string beginning with this apostrophe,
> and the <Char-0x2019> construct does not help. This is weird, because
> there is no problem with mapping the usual apostrophe U+0027. Other
> paradoxes can be found : It is possible to map the no-break space
> (U+00A0) but not its thin version (U+202F), the usual minus sign
> (U+002D) but not the en-dash (U+2013) and the em-dash (U+2014).
> 
> I first thought vim had a problem with mapping multibyte characters
> but it actually deals well with most of them. Any explanation, why the
> mapping does not work with some characters?
> 
> Thanks for your help
> 
> Thomas
> 

(Continue reading)

Guopeng Wen | 2 Mar 03:18 2007
Picon

Re: Subject: Re: vim on cygwin using win32 clipboard

On 2/15/07, Frodak Baksik <frodak17 <at> gmail.com> wrote:
> On 2/15/07, Chris Sutcliffe wrote:
> > > > Also, is there anything I can do to help get the original patch accepted?
> > >
> > > Ask a few people to try it out and report their results here.
> >
> > I'll give it a shot.  Is there somewhere I can grab the patch from, or
> > should I go through the list archives to find it?
> >
> > Chris
> >
> > --
> > Chris Sutcliffe
> > http://ir0nh34d.googlepages.com
> > http://ir0nh34d.blogspot.com
> > http://emergedesktop.org
> >
>
> Here are all the changes in a single patch.
> I'm also posting this to the cygwin-apps mailing list, so if anyone
> over there could try it out would be nice.
>
> Thanks,
> Frodak

Frodak,

I just checked the patch on SVN revision 223, it works as expected.

I usually perform some shell related tasks using vim on cygwin.
(Continue reading)

Frodak Baksik | 2 Mar 12:53 2007
Picon

Re: Subject: Re: vim on cygwin using win32 clipboard

On 3/1/07, Gary Johnson <garyjohn <at> spk.agilent.com> wrote:
> On 2007-03-01, Frodak Baksik <frodak17 <at> gmail.com> wrote:
> > On 2/28/07, Matthew Woehlke <mw_triad <at> users.sourceforge.net> wrote:
> > > Gary Johnson wrote:
> > > > It appears that I may need to install the ncurses package and
> > > > reconfigure vim in order to get color.
> > >
> > > That would be likely; ncurses is (AFAIK) *much* better than termcap.
>
> > Try getting ncurses and gettext libraries.  Both are available
> > packages in cygwin.
>
> There are several ncurses packages to choose from, but I finally
> figured out that I needed libncurses-devel, so I installed that,
> reconfigured and rebuilt vim and voila:  color!
>
> It's not as clear to me what I need to resolve these differences:
>
>     36c36
>     < +gettext
>     ---
>     > -gettext
>     111c111
>     < Linking: gcc   -L/usr/local/lib -o vim.exe       -lncurses  -liconv -lintl
>     ---
>     > Linking: gcc   -L/usr/local/lib -o vim.exe       -lncurses  -liconv
>
> My Cygwin installation already has
>
>     /usr/include/libintl.h
(Continue reading)


Gmane