When will 7.2 come out?
Hi Bram, There are already more than 200 patches. When will 7.2 come out? Any plans? Regards, Edward Leap Fox --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: --remote-tab-silent not mentioned in --help
> Ted Pavlic mentioned on the vim-mac list that --remote-tab-silent is > not mentioned in the --help output and suggests to add it. I think > that's a good idea. What do you think? There has been some positive feedback on this, so here's a patch to implement it. Bye, Nico --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~--- help.patch Description: Binary data
Re: Patch 7.1.215
Bram Moolenaar wrote: >Patch 7.1.215 >Problem:It is difficult to figure out what syntax items are nested at a > certain position. >Solution: Add the synstack() function. >Files: runtime/doc/eval.txt, src/eval.c, src/proto/syntax.pro, > src/syntax.c > > If you'd like to see this patch in operation, you could try hilinks.vim, available at: http://mysite.verizon.net/astronaut/vim/index.html#HILINKS Then :HLT! will turn on highlighting-links-trace on -- and will display the trace as you move your cursor about. Of course, to see synstack() working, you do have to have installed the patch! :) Regards, Chip Campbell --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch 7.1.215
On 10/01/2008, Ben Schmidt <[EMAIL PROTECTED]> wrote: > > > Andy Wokula wrote: > > Bram Moolenaar schrieb: > >> Patch 7.1.215 > >> Problem:It is difficult to figure out what syntax items are nested > at a > >> certain position. > >> Solution: Add the synstack() function. > >> Files: runtime/doc/eval.txt, src/eval.c, > src/proto/syntax.pro, > >> src/syntax.c > > > > Oh yeah, a very useful addition!! > > I was thinking exactly the same! > > Three cheers for Bram! -- Erik Falor Registered Linux User #445632 http://counter.li.org --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Repost: [PATCH] Enable cross-compiling
> Although according the Ben's earlier posting, we're both "in the pipeline". > > So I guess we just sit tight a little longer... If you haven't seen Bram's post to you now (that should comt to you directly and via the vim_dev list), let me know and I will forward its text only to you. Seems he has been having trouble reaching you (emails bouncing). If ones he sends to you via the mailing list bounce too, it could get tricky! Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch 7.1.215
Andy Wokula wrote: > Bram Moolenaar schrieb: >> Patch 7.1.215 >> Problem:It is difficult to figure out what syntax items are nested at a >> certain position. >> Solution: Add the synstack() function. >> Files: runtime/doc/eval.txt, src/eval.c, src/proto/syntax.pro, >> src/syntax.c > > Oh yeah, a very useful addition!! I was thinking exactly the same! Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch 7.1.215
Bram Moolenaar schrieb: > Patch 7.1.215 > Problem:It is difficult to figure out what syntax items are nested at a > certain position. > Solution: Add the synstack() function. > Files:runtime/doc/eval.txt, src/eval.c, src/proto/syntax.pro, > src/syntax.c Oh yeah, a very useful addition!! -- Andy --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch for Unix filename expansion to try out
Bram Moolenaar wrote:
>A couple of problems were detected when the Unix shell is used to expand
>file names containing characters such as a single quote. This applies
>to completion on the command line and glob().
>
>I made a patch that defines a function to echo each file name
>separately. Inspired by a patch that Dasn made, but staying on the safe
>side.
>
>The patch for ex_docmd.c changes detecting the end of the file name when
>doing command line completion. This specifically fixes a file name
>containing "&".
>
>Please try it out and let me know if there are any new problems.
>
>
Verhoef sent me a directory structure:
a & b/
one
two
a's & b's/
three
four
Netrw works for the first "a & b", and does so with the new patch.
However, it does not work for the second set ("a's & b's"); the glob()
for it returns the empty string:
...netrw debugging info..
glob(dirname)=
...more netrw debugging info
I used ksh under Fedora Core Linux and a vim compiled with the patch.
Regards,
Chip Campbell
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Patch 7.1.215
Patch 7.1.215
Problem:It is difficult to figure out what syntax items are nested at a
certain position.
Solution: Add the synstack() function.
Files: runtime/doc/eval.txt, src/eval.c, src/proto/syntax.pro,
src/syntax.c
*** ../vim-7.1.214/runtime/doc/eval.txt Sun Jan 6 20:05:36 2008
--- runtime/doc/eval.txtThu Jan 10 22:20:31 2008
***
*** 1,4
! *eval.txt* For Vim version 7.1. Last change: 2008 Jan 06
VIM REFERENCE MANUALby Bram Moolenaar
--- 1,4
! *eval.txt* For Vim version 7.1. Last change: 2008 Jan 10
VIM REFERENCE MANUALby Bram Moolenaar
***
*** 1786,1791
--- 1786,1792
synIDattr( {synID}, {what} [, {mode}])
String attribute {what} of syntax ID {synID}
synIDtrans( {synID}) Number translated syntax ID of {synID}
+ synstack({lnum}, {col}) Liststack of syntax IDs at {lnum}
and {col}
system( {expr} [, {input}]) String output of shell command/filter {expr}
tabpagebuflist( [{arg}]) Listlist of buffer numbers in tab page
tabpagenr( [{arg}]) Number number of current or last tab page
***
*** 4962,4967
--- 4966,4989
highlight the character. Highlight links given with
":highlight link" are followed.
+ synstack({lnum}, {col}) *synstack()*
+ Return a |List|, which is the stack of syntax items at the
+ position {lnum} and {col} in the current window. Each item in
+ the List is an ID like what |synID()| returns.
+ The stack is the situation in between the character at "col"
+ and the next character. Note that a region of only one
+ character will not show up, it only exists inside that
+ character, not in between characters.
+ The first item in the List is the outer region, following are
+ items contained in that one. The last one is what |synID()|
+ returns, unless not the whole item is highlighted or it is a
+ transparent item.
+ This function is useful for debugging a syntax file.
+ Example that shows the syntax stack under the cursor: >
+ for id in synstack(line("."), col("."))
+ echo synIDattr(id, "name")
+ endfor
+
system({expr} [, {input}])*system()* *E677*
Get the output of the shell command {expr}.
When {input} is given, this string is written to a file and
*** ../vim-7.1.214/src/eval.c Sun Jan 6 20:05:36 2008
--- src/eval.c Wed Jan 9 13:42:56 2008
***
*** 651,656
--- 651,657
static void f_synID __ARGS((typval_T *argvars, typval_T *rettv));
static void f_synIDattr __ARGS((typval_T *argvars, typval_T *rettv));
static void f_synIDtrans __ARGS((typval_T *argvars, typval_T *rettv));
+ static void f_synstack __ARGS((typval_T *argvars, typval_T *rettv));
static void f_system __ARGS((typval_T *argvars, typval_T *rettv));
static void f_tabpagebuflist __ARGS((typval_T *argvars, typval_T *rettv));
static void f_tabpagenr __ARGS((typval_T *argvars, typval_T *rettv));
***
*** 7252,7257
--- 7253,7259
{"synID", 3, 3, f_synID},
{"synIDattr", 2, 3, f_synIDattr},
{"synIDtrans",1, 1, f_synIDtrans},
+ {"synstack", 2, 2, f_synstack},
{"system",1, 2, f_system},
{"tabpagebuflist",0, 1, f_tabpagebuflist},
{"tabpagenr", 0, 1, f_tabpagenr},
***
*** 15843,15848
--- 15845,15890
id = 0;
rettv->vval.v_number = id;
+ }
+
+ /*
+ * "synstack(lnum, col)" function
+ */
+ /*ARGSUSED*/
+ static void
+ f_synstack(argvars, rettv)
+ typval_T *argvars;
+ typval_T *rettv;
+ {
+ #ifdef FEAT_SYN_HL
+ long lnum;
+ long col;
+ int i;
+ int id;
+ #endif
+
+ rettv->v_type = VAR_LIST;
+ rettv->vval.v_list = NULL;
+
+ #ifdef FEAT_SYN_HL
+ lnum = get_tv_lnum(argvars); /* -1 on type error */
+ col = get_tv_number(&argvars[1]) - 1; /* -1 on type error */
+
+ if (lnum >= 1 && lnum <= curbuf->b_ml.ml_line_count
+ && col >= 0 && col < (long)STRLEN(ml_get(lnum))
+ && rettv_list_alloc(rettv) != FAIL)
+ {
+ (void)syn_get_id(curwin, lnum, (colnr_T)col, FALSE, NULL);
+ for (i = 0; ; ++i)
+ {
+ id = syn_get_stack_item(i);
+ if (id < 0)
+ break;
+ if (list_append_number(rettv->vval.v_list, id) == FAIL)
+ break;
+ }
+ }
+ #endif
}
/*
*** ../vim-7.1.214/src/proto/syntax.pro Tue Jul 24 14:32:44 2007
--- src/pro
Re: Repost: [PATCH] Enable cross-compiling
Marc Haisenko wrote: > On Wednesday 09 January 2008, Marc Haisenko wrote: > >> Hi folks, >> a few weeks back I posted a patch that helps enabling cross-compiling by >> adding the necessary stuff in configure.in to tell "configure" the necessary >> values when cross-compiling. The patch also includes a README explaining >> everything. >> >> As people asked me about it I'd like to know if there's anything to fix in >> that patch before it can get accepted or if there are any other problems to >> resolve first. >> >> Thanks a lot, >> Marc >> > > PING. Could I please get a comment about this, even if it's "go away" ? > > I second the patch. :-) Although according the Ben's earlier posting, we're both "in the pipeline". So I guess we just sit tight a little longer... -Philip --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: [PATCH] Cross-compilation patch to avoid looking for /usr/local at compile time
Philip Prindeville wrote: > This is simple enough: suppress the detecting of /usr/local and > putting it into the load path (etc) if we're cross-compiling. > > Please review this and if it looks reasonable, signal to whomever to > commit it to the source tree (as a patch, obviously) or cast a > positive vote or whatever is necessary to bless it and assure its > commission. > > I sent it out-of-band a couple of times to Bram but it hasn't been > approved (or rejected for that matter), so I figure I should be > sending it to someone else (but don't know who that would be). The reason you don't hear from me is that most of my emails to you bounce back. What I tried to say: excluding /usr/local/[include|lib] is not specific for cross compiling. This should be a separate setting. Then it can also be set for cross compiling. Most configure features are explained in the Makefile. Or in the INSTALL file. I prefer the Makefile, there you can uncomment a line to have it used, no need to type it (configure doesn't warn for unrecognized arguments). -- Michael: There is no such thing as a dump question. Bernard: Sure there is. For example "what is a core dump?" /// Bram Moolenaar -- [EMAIL PROTECTED] -- 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 -~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
> I was thinking of RFC 1738 (Uniform Resource Locators) but it also > mentions that parentheses are reserved characters and can be escaped > unless they're being used for a reserved purpose. And whether they have a reserved purpose is dictated by the URL scheme, isn't it, not the browser/software. So a web browser shouldn't serve different pages, as brackets don't have a reserved purpose in http URIs. Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
On Thu, Jan 10, 2008 at 02:51:26PM -0500, Matt Wozniski wrote: > > On Jan 10, 2008 2:39 PM, James Vega <[EMAIL PROTECTED]> wrote: > > On Thu, Jan 10, 2008 at 08:28:14PM +0100, Tony Mechelynck wrote: > > > The parentheses should have been percent-escaped, i.e., replaced by a > > > percent > > > sign and their hex value (00-FF) as in > > > > > > http://www.vim.org/%28test%29 > > > > While it's true that the URL RFC dictates that such characters should be > > hex-escaped, most user interfaces accept the non-escaped version so > > people don't have to remember character codes for everything. This does > > make it more difficult to perform proper highlighting/selection of a URL > > but it's a give and take for user simplicity vs. developer hardship. > > This is also why angle brackets are specified for use as URL delimiters > > in text, since it vastly simplifies parsing. > > Actually, RFC 2616 (Hypertext Transfer Protocol -- HTTP/1.1) says at > 3.2.3 (URI Comparison) that parentheses, being in the reserved set, > are not required to evaluate as equal to the %XX forms. I was thinking of RFC 1738 (Uniform Resource Locators) but it also mentions that parentheses are reserved characters and can be escaped unless they're being used for a reserved purpose. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: Bug in syntax/mail.vim
On Jan 10, 2008 2:39 PM, James Vega <[EMAIL PROTECTED]> wrote: > On Thu, Jan 10, 2008 at 08:28:14PM +0100, Tony Mechelynck wrote: > > The parentheses should have been percent-escaped, i.e., replaced by a > > percent > > sign and their hex value (00-FF) as in > > > > http://www.vim.org/%28test%29 > > While it's true that the URL RFC dictates that such characters should be > hex-escaped, most user interfaces accept the non-escaped version so > people don't have to remember character codes for everything. This does > make it more difficult to perform proper highlighting/selection of a URL > but it's a give and take for user simplicity vs. developer hardship. > This is also why angle brackets are specified for use as URL delimiters > in text, since it vastly simplifies parsing. Actually, RFC 2616 (Hypertext Transfer Protocol -- HTTP/1.1) says at 3.2.3 (URI Comparison) that parentheses, being in the reserved set, are not required to evaluate as equal to the %XX forms. So, a standards conforming web server could send you to a different page depending on whether you use http://vim.org/%28test%29 or http://vim.org/(test) ... Though that may or may not be relevant to the conversation at hand. ~Matt --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
On Thu, Jan 10, 2008 at 08:28:14PM +0100, Tony Mechelynck wrote: > The parentheses should have been percent-escaped, i.e., replaced by a percent > sign and their hex value (00-FF) as in > > http://www.vim.org/%28test%29 While it's true that the URL RFC dictates that such characters should be hex-escaped, most user interfaces accept the non-escaped version so people don't have to remember character codes for everything. This does make it more difficult to perform proper highlighting/selection of a URL but it's a give and take for user simplicity vs. developer hardship. This is also why angle brackets are specified for use as URL delimiters in text, since it vastly simplifies parsing. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: Bug in syntax/mail.vim
Richard Hartmann wrote: > On Jan 10, 2008 4:20 PM, Ben Schmidt <[EMAIL PROTECTED]> wrote: > > >> I suspect it is deliberate. URLs rarely contain parentheses, but are often >> written >> inside them in sentences, e.g. >> >> There is interesting information on the web (for example, at >> http://vim.org/). > > That is true. In case there is an opening bracket in the URL, I do think > highlighting the closing bracket as well would make sense, though. > > > Richard The parentheses should have been percent-escaped, i.e., replaced by a percent sign and their hex value (00-FF) as in http://www.vim.org/%28test%29 Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 225. You sign up for free subscriptions for all the computer magazines --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
On Fri, Jan 11, 2008 at 02:20:05AM +1100, Ben Schmidt wrote:
> > to reproduce:
> >
> > vim -u NONE -U NONE
> > :set syntax
>
> Presuming you mean :syntax enable.
>
> > :set ft=mail
> > i " this newline is for readability
> > http://vim.org/(test)
> >
> > The closing bracket will not be highlighted.
>
> I suspect it is deliberate. URLs rarely contain parentheses, but are
> often written inside them in sentences, e.g.
>
> There is interesting information on the web (for example, at
> http://vim.org/).
Yes, it is deliberate (I wrote it a long time ago, for exactly the
purpose you point out above). If you notice, even a period at the end of
a URL will not be highlighted as in www.vim.org.
If you like you can modify the current URL regexp so that it that
matches URLs which includes the ")" at the end provided the URL contains
a "(". Send it to me, and I'll include it :).
GI
--
'Code Orange' -- Eat dessert first.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: Wish: enable :subst-expr with 'n' flag
ap schrieb:
>
>
> On Jan 9, 6:06 pm, Andy Wokula <[EMAIL PROTECTED]> wrote:
>> I tried to write a function that collects all the matches for a given
>> pattern in the text.
>>
>> For that purpose, it would be very nice if the following worked:
>> :%s/{pattern}/\=MyAddMatch(submatch(0))/gn
>
>
> I agree, this could be easier.
>
> Doing it with search() seems a bit tricky.
>
> -it needs 2 calls to search()
> -the startposition needs special care
> ( there could be a match in the first column of
> the first line one wants to search )
>
> --%<--
> "Could be improved by handling the startpos differently
> "and avoid the 3rd search.
> func! CollectWords( pat, first_line, last_line )
> let result = []
> call cursor(a:first_line,1)
> while search(a:pat,'cW',a:last_line)
> normal! ms
> call search(a:pat,'ceW')
> normal! me
> normal! `sv`ey
> call add(result,@")
> call search('.','W')
> endwhile
> return result
> endfun
> --%<--
>
>
> Maybe someone has a better idea, apart from source modification.
>
> -ap
Thanks for your try. Right, two search()es are much effort just for
getting the contents of a single match.
I first tried to use
//^M
y//e^M
in a loop, but this fails for matches of length 1.
Your function does it right.
Since in most cases I have a pattern that matches on a single line and
I only want matches for the last search pattern, I'll go with this:
func! CollectMatches()
let matches = []
let patq = substitute(@/, "'", "''", "g")
exec 'sil g//call substitute(getline("."),'''.patq
\.''', "\\=add(matches, submatch(0))", "g")'
return matches
endfunc
--
Andy
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
Richard Hartmann wrote: > On Jan 10, 2008 4:20 PM, Ben Schmidt <[EMAIL PROTECTED]> wrote: > > >> I suspect it is deliberate. URLs rarely contain parentheses, but are often >> written >> inside them in sentences, e.g. >> >> There is interesting information on the web (for example, at >> http://vim.org/). > > That is true. In case there is an opening bracket in the URL, I do think > highlighting the closing bracket as well would make sense, though. Yeah. I think it would make sense, too, but it's horrible to code nicely and reliably. Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
On Jan 10, 2008 4:20 PM, Ben Schmidt <[EMAIL PROTECTED]> wrote: > I suspect it is deliberate. URLs rarely contain parentheses, but are often > written > inside them in sentences, e.g. > > There is interesting information on the web (for example, at http://vim.org/). That is true. In case there is an opening bracket in the URL, I do think highlighting the closing bracket as well would make sense, though. Richard --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Wish: enable :subst-expr with 'n' flag
On Jan 9, 6:06 pm, Andy Wokula <[EMAIL PROTECTED]> wrote:
> I tried to write a function that collects all the matches for a given
> pattern in the text.
>
> For that purpose, it would be very nice if the following worked:
> :%s/{pattern}/\=MyAddMatch(submatch(0))/gn
I agree, this could be easier.
Doing it with search() seems a bit tricky.
-it needs 2 calls to search()
-the startposition needs special care
( there could be a match in the first column of
the first line one wants to search )
--%<--
"Could be improved by handling the startpos differently
"and avoid the 3rd search.
func! CollectWords( pat, first_line, last_line )
let result = []
call cursor(a:first_line,1)
while search(a:pat,'cW',a:last_line)
normal! ms
call search(a:pat,'ceW')
normal! me
normal! `sv`ey
call add(result,@")
call search('.','W')
endwhile
return result
endfun
--%<--
Maybe someone has a better idea, apart from source modification.
-ap
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: Bug in syntax/mail.vim
Richard Hartmann wrote: > Hi all, > > to reproduce: > > vim -u NONE -U NONE > :set syntax Presuming you mean :syntax enable. > :set ft=mail > i " this newline is for readability > http://vim.org/(test) > > The closing bracket will not be highlighted. I suspect it is deliberate. URLs rarely contain parentheses, but are often written inside them in sentences, e.g. There is interesting information on the web (for example, at http://vim.org/). Cheers, Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Bug in syntax/mail.vim
Hi all, to reproduce: vim -u NONE -U NONE :set syntax :set ft=mail i " this newline is for readability http://vim.org/(test) The closing bracket will not be highlighted. Richard --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Respects From Pakistan
Dearly Friend, May His Grace and Peace be with you Friend. I hope that this letter finds you in the best of yours health and spirit. We are also keeping well by the grace of God. We feel truly blessed by God, having the privilege to work in His service. We work as a ministry in Pakistan called Christ Fellowship Ministries Pakistan. Our goals are to help ease the suffering endured by persecuted Christians at the hands of the religious extreme fundamentalists and to work to restore a peace between the peoples. We also do what we can to educate the poor, to give them strength and hope to carry out their lives. Christ Fellowship Ministries wants to help to educate the young children in reading, writing and arithmetic. We want to see them grow up educated and ready to face any challenge life may throw their way. We also want to see their parents and the elderly benefit from the Holy Scriptures being read in their homes to give them strength and courage to face the day. We are confident that we can return pride back to those who have lost everything, just because they long to serve Jesus Christ. Jesus commanded us with the beatitudes to care for those less fortunate than us. It is not enough to see the scourge of Satan across the backs of the hurting, but to do something about it. Join with us, and we will change what we can together! ON GOING ACTIVITIES (1)FORMAL CHILDREN SCHOOL: We do need your support in our Orphanages and formal education schools as every children in the school are studying free of cost and getting books, note books, stationeries, uniform, shoes and Etc .. (2)SUNDAY SCHOOLS: This ministry is handling with Sunday schools in Toba Tek Singh , Shore Kot, Arif Wala and Okara where Christ Fellowship Ministries teaching about Bible and Christ. Sunday school manages to show the Christian Movies and provide them with Christian Story Books to make the learning easy and comprehendible. Sunday Schools also have choirs. Children learn about new Christian Songs in native Language. Choirs some times perform in conventions and in churches as well. (4)FREE DISPENSARY: Children on the streets are very much likely to risk their lives indulging into drugs and the ministries wishes them to lead health lives after getting treated. (5)HANDICAPPED CENTRE: Our visitation group is sharing the love of Christ with the handicapped children and adults. We are weekly arranging seminars and programs to share the word of God with these people and children. (6)OPERATION SOUL WINNING: Operation soul winning is a special outreach programme to win many souls and share the love of God in summer & Holidays in Rural &urban areas, with Literature distribution, film ministries, open air meetings, crusades etc.. (7) Orphan: We are working with Orphans, Semi Orphans and Street Children. OPEN INVITATION TO YOU " THE HARVEST TRULY IS GREAT BUT THE LABOURERS ARE FEW " We invite the Mission partners to come here in Pakistan join us and reach these souls. We monthly and weekly organize prayer meetings in the communities and there is open platform for International Preachers, Church Pastors, Evangelistic and Missionary brethren to come and Labour with us in the harvest of the Lord. Please keep us in your mission fields and areas of Ministries and to uphold us in prayer & financial support. If you are willing, we will send you mission news updates through Email or post. We can send you invitation letter if you are interested to visit and preach in Pakistan among thirsty souls. Mission partners are requested to start prayer groups (if possible) to pray for our ministries. WR NEED PARTNERS TO SUPPOR: Our formal Education Schools Our Sunday Schools Our Handicapped Centre Our Free Dispensaries Operation Soul Winning Prayer Meetings May God richly bless and keep you. May Face His smile upon you and His light keep burning yours heart. May His Love, Peace and Joy be with you. We hope that we will more communication with you. In Christs Merits, Pastor Asim Saddique Christ Fellowship Ministries Pakistan website: http://cf.ministriespk.tripod.com Office Phone: +92 462 515247 Mobile :+92 346 4877701 Head Office Christ Fellowship Ministries Pakistan Pastor Asim Saddique Street address: Street# 01 House# 02 Mubarik Abad Christian Colony, Shor Kot Road City : Toba Tek Singh Zip Code : 36050 Province : Punjab Country: Pakistan - Never miss a thing. Make Yahoo your homepage. --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Repost: [PATCH] Enable cross-compiling
On Wednesday 09 January 2008, Marc Haisenko wrote: > Hi folks, > a few weeks back I posted a patch that helps enabling cross-compiling by > adding the necessary stuff in configure.in to tell "configure" the necessary > values when cross-compiling. The patch also includes a README explaining > everything. > > As people asked me about it I'd like to know if there's anything to fix in > that patch before it can get accepted or if there are any other problems to > resolve first. > > Thanks a lot, > Marc PING. Could I please get a comment about this, even if it's "go away" ? -- Marc Haisenko Comdasys AG Rüdesheimer Str. 7 80686 München Germany Tel.: +49 (0)89 548 433 321 --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
