public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ping <songpingemail@gmail.com>
To: Tony Mechelynck <antoine.mechelynck@gmail.com>
Cc: vim_use@googlegroups.com, cygwin@cygwin.com,
	 Vlad Irnov <vlad.irnov@gmail.com>
Subject: Re: vim/cygwin: python support
Date: Sun, 01 Jul 2012 05:11:00 -0000	[thread overview]
Message-ID: <4FEFDBE6.5060804@gmail.com> (raw)
In-Reply-To: <4FEF77E4.5060700@gmail.com>

On 6/30/2012 6:04 PM, Tony Mechelynck wrote:
> On 30/06/12 23:32, ping wrote:
>> Thanks
>> I just got it recompiled under cygwin with python support
>> At least Voom that is based on python runs smoothly now
>> I can post detailed steps if anyone is interested
> [...]
>
> Maybe you should create a tip at http://vim.wikia.com/ ?
>
>
> Best regards,
> Tony.

sure I'll seriously do it later..
but currently, I'm still testing it -- trying to move all my linux-based 
works (whole .vim including all plugins!) on this new build.

so Voom (python based) works perfect:

[1] bash.exe - 1 [2] tech-tips2.txt_VOOM2 
    close
2  161   . . |c-s mod>     4570 === arp
2  162   . . |smc          4571
2  163   . . |swap         4572 ==== ##arp
2+ 164   . . |coredump     4573 in.arpd
2+ 166   . . |NFS   /1     4574 /etc/inet/hosts <-      /etc/hosts
2+ 181   . . |autoFS       4575
2+ 188   . . |RAID & v     4576 /etc/ethers
2+ 192   . . |config v     4577
2+ 196   . . |name ser     4578 arp     -a
-  198   . |book3          4579         -s
2  199   . . |etherne>     4580         -d
-  200 = . . |arp          4581
3  201   . . . |##arp      4582
3  202   . . . |##rarp     4583 ==== ##rarp



and ... I do find some minor (maybe not that minor) issue in here, e.g:

1)sometime (not everytime, roughly half chances) follow warning/errors 
prompt, press <enter> it will go away and laugh vim.

[ping@ping-new-laptop ~]$ vim
       1 [main] vim 6740 child_info_fork::abort: address space needed by 
'fcntl.dll' (0x320000) is already occupied

Cannot fork


Press ENTER or type command to continue


2) if 1) happened, then ConqueTerm plugin crash vim; otherwise it works 
fine.

#when it crashes:

   ~
   ~
   ~
:ConqueTerm bash.exe

Error detected while processing function 231..conque_term#set_mappings:
line  150:
E31: No such mapping
Vim: Caught deadly signal HUPo continue

Vim: Finished.
Hangup


#when it works (inside vim buffer):

[ping@ping-new-laptop ~]$
[ping@ping-new-laptop ~]$ ls
c  doc  Dropbox  fuf  living files  n  vim  win-home  win-programfile
[ping@ping-new-laptop ~]$
~
~
~
-- INSERT --                                                  20,27 
     All


overall I feel there is still some hopes that it can be a production tool...

regards
ping

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-07-01  5:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1198556727-1341091933-cardhu_decombobulator_blackberry.rim.net-741837253-@b12.c30.bise6.blackberry>
2012-06-30 22:04 ` Tony Mechelynck
2012-07-01  5:11   ` ping [this message]
2012-07-01 23:20     ` Andrey Repin
     [not found] <4FEDBA31.4060104@gmail.com>
2012-06-29 14:26 ` ping
2012-06-29 15:06   ` Ryan Johnson
2012-06-29 15:43     ` ping
2012-06-29 20:50       ` ping
2012-06-30 13:09 ` Tony Mechelynck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FEFDBE6.5060804@gmail.com \
    --to=songpingemail@gmail.com \
    --cc=antoine.mechelynck@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=vim_use@googlegroups.com \
    --cc=vlad.irnov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).