I figured out  what was causing the compiler errors  with the NEW Motif 2.1 
libs on z/OS 1.11

The  "Xauth.h"  header file  in Motif 2.1   adds a reference to  "Xfuncs.h"
and   that conflicts  with   "strings.h"

I added the following to fix the compiler errors >>>

/* Define if strings.h cannot be included when strings.h already is */
#define NO_STRINGS_WITH_STRING_H 1
/* #undef NO_STRINGS_WITH_STRING_H */

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

But now I am getting  LINK errors, and I am quite perplexed  because I do not
know where these missing lib references are coming from

>>>>>>>>

cc  -Wl,EDIT=NO -W l,dll,xplink  -o vim objects/buffer.o  objects/blowfish.o 
objects/charset.o  objects/diff.o  objects/digraph.o  objects/edit.o 
objects/eval.o  objects/ex_cmds.o  objects/ex_cmds2.o  objects/ex_docmd.o 
objects/ex_eval.o  objects/ex_getln.o  objects/fileio.o  objects/fold.o 
objects/getchar.o  objects/hardcopy.o  objects/hashtab.o    objects/if_cscope.o 
objects/if_xcmdsrv.o  objects/mark.o  objects/memline.o  objects/menu.o 
objects/message.o  objects/misc1.o  objects/misc2.o  objects/move.o 
objects/mbyte.o  objects/normal.o  objects/ops.o  objects/option.o 
objects/os_unix.o  objects/pathdef.o  objects/popupmnu.o  objects/quickfix.o 
objects/regexp.o  objects/screen.o  objects/search.o  objects/sha256.o 
objects/spell.o  objects/syntax.o    objects/tag.o  objects/term.o  objects/ui.o
objects/undo.o  objects/version.o  objects/window.o  objects/gui.o
objects/gui_motif.o objects/gui_x11.o  objects/pty.o objects/gui_beval.o 
objects/gui_xmdlg.o objects/gui_xmebw.o  objects/main.o  objects/memfile.o  
-lXmu -lXext  -lXm -lXt    -lXt -lX11  -loldX -lSM -lICE -lXp  -lm -lcurses
  IEW2456E 9207 SYMBOL XShapeQueryExtension UNRESOLVED.  MEMBER COULD NOT BE
           INCLUDED FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XShapeCombineRectangles UNRESOLVED.  MEMBER COULD NOT BE
           INCLUDED FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XShapeCombineMask UNRESOLVED.  MEMBER COULD NOT BE
           INCLUDED FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XextRemoveDisplay UNRESOLVED.  MEMBER COULD NOT BE
           INCLUDED FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XMissingExtension UNRESOLVED.  MEMBER COULD NOT BE
           INCLUDED FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XextAddDisplay UNRESOLVED.  MEMBER COULD NOT BE INCLUDED
           FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XextFindDisplay UNRESOLVED.  MEMBER COULD NOT BE INCLUDED
           FROM THE DESIGNATED CALL LIBRARY.
  IEW2456E 9207 SYMBOL XextCreateExtension UNRESOLVED.  MEMBER COULD NOT BE
           INCLUDED FROM THE DESIGNATED CALL LIBRARY.
FSUM3065 The LINKEDIT step ended with return code 8.
FSUM8226 make: Error code 3
make: 'vim' removed.
$

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Any suggestions would be greatly appreciated


--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

I can confirm that mattn's patch does appear to fix this problem; the dot
register works again.

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

I had mistake in the patch.
Please look newer in same URL.

On Wednesday, May 2, 2012 10:35:12 PM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
> > It seems that gtk_init connect to dbus session. Currently, it is
> > called before fork, i.e. parent process.
> > Parent process quit after the checking gui enable. So dbus session
> > become disconnected.
> >
> > https://bugs.launchpad.net/ubuntu/+source/vim/+bug/987707
> >
> > I moved call of gtk_init to child process.
> >
> > https://gist.github.com/2576464
> >
> > It seens good to me.
>
> Thanks.  I just upgraded to 12.04 thus I should be able to verify this
> soon.
>
> --
> It is illegal to rob a bank and then shoot at the bank teller with a water
> pistol.
> 	 [real standing law in Louisana, United States of America]
>
>  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
> ///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org        ///
>  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Mon, May 07, 2012 at 01:36:44PM -0700, Stanislav Kondratyev wrote:
> My Vim is
>
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
> MS-Windows 32-bit GUI version with OLE support
> Included patches: 1-46
> Compiled by Bram@KIBAALE
> Big version with GUI.
>
> I¡¦ve set the encoding to utf-8 in the vimrc.
>
> Sorry, is cp936 a multibyte encoding?

Yes.

I think you need to get a newer Vim. This was fixed around patch number 200.

--
Best regards,
lilydjwg

Linux Vim Python §Úªº³Õ«È:
http://lilydjwg.is-programmer.com/
--
A: Because it obfuscates the reading.
Q: Why is top posting so bad?

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On 08/05/12 07:13, lilydjwg wrote:
> On Mon, May 07, 2012 at 01:36:44PM -0700, Stanislav Kondratyev wrote:
>> My Vim is
>>
>> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
>> MS-Windows 32-bit GUI version with OLE support
>> Included patches: 1-46
>> Compiled by Bram@KIBAALE
>> Big version with GUI.
>>
>> I’ve set the encoding to utf-8 in the vimrc.
>>
>> Sorry, is cp936 a multibyte encoding?
>
> Yes.
>
> I think you need to get a newer Vim. This was fixed around patch number 200.
>


FYI, the latest source is 7.3.515.

Best regards,
Tony.
--
Cigarette, n.:
	 A fire at one end, a fool at the other, and a bit of tobacco in
between.

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Many thanks for the tips! Now it works.

I failed to found a recent Windows installer with python 3 enabled, so I had to
build gvim myself (and I’m especially proud of it. :)

In case someone googles the same issue, I’d like to summarize my experience:
http://vim.wikia.com/wiki/Build_Python-enabled_Vim_on_Windows_with_MinGW
I edited Make_ming.mak and Makefile in their part concerning python. One can
build gvim with the following command:
mingw32-make -f Make_ming.mak gvim.exe

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Monday, May 7, 2012 4:37:20 AM UTC-5, Christian Brabandt wrote:
> On Sun, May 6, 2012 15:22, Zroutik wrote:
> > Dear vim devs,
> >
> > thank you for the great editing tool!
> >
> > Recently I was editing my R scripts (R Project statistical software)
> > and I came across the following strange behaviour: Jumping between
> > parenthesis is not as expected, if an unpaired closing parenthesis
> > appears in-between in comments.
> >
> > OS: windows XP,
> >
> > vim: VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Apr 30 2012
> > 14:21:53)
> > MS-Windows 32-bit GUI version with OLE support
> > Included patches: 1-514
> > Compiled by digitectNO@...
> >
> >
> > A 2-line minimal example:
> > ( #)
> > )
> >
> > In this example, three parenthesis are present. One opening
> > parenthesis, and two closing. But one of the closing is in the
> > comment.
> > 1) When placing the pointer before the text, no text portion is
> > highlighted.
> > 2) When placing the pointer at the first parenthesis, the second one
> > within the pair is correctly highlighted. The parenthesis in the
> > comment is ignored.
> > 3) Now, jumping to the paired parenthesis (using a keystroke %) makes
> > the pointer jump to the open parenthesis in the comment. And back,
> > too, when the keystroke is repeated.
> > 4) After placing the pointer to the correct paired parenthesis,
> > pressing % does not evoke any jump.
> > I have a collection of screenshots, that I can supply per email, if
> > requested, please.
> >
> > I believe this behaviour is not expected. The parenthesis in the
> > comments should be ignored by highlighting (correct in the example
> > above), and within motion, too (incorrect in the example above).
> >
> > Let me know, if I should supply more information, please.
>
> The builtin % motion of Vim does not take comments into consideration.
> If you like this behaviour, activate the bundled matchit-plugin that comes
> with vim, see :h matchit-activation and :h matchit-install, but you should
> possibly read the whole document (:h matchit.txt)
>

I don't see a R ftplugin file in my Vim installation. Check that yours includes
an appropriate setting of the b:match_words variable for use by matchit, or you
may see problematic behavior with % still.

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic <gostrc@...> wrote:
>> It looks like this was caused by
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
>>
>
> I will try to see if this was the problem once the next gcc snapshot
> comes out (this weekend or next week) and try to report back here.

Just tried out the latest gcc snapshot 4.7-20120505
This segfault still exists so it wasn't caused by gcc bug #53084.
Also, here is a fedora bug report for the same thing:
https://bugzilla.redhat.com/show_bug.cgi?id=817196

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Hi Thomas!

On Mi, 09 Mai 2012, Thomas Dziedzic wrote:

> On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic <gostrc@...> wrote:
> >> It looks like this was caused by
> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
> >>
> >
> > I will try to see if this was the problem once the next gcc snapshot
> > comes out (this weekend or next week) and try to report back here.
>
> Just tried out the latest gcc snapshot 4.7-20120505
> This segfault still exists so it wasn't caused by gcc bug #53084.
> Also, here is a fedora bug report for the same thing:
> https://bugzilla.redhat.com/show_bug.cgi?id=817196

Shouldn't patch 497 avoid the crash?

regards,
Christian

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Wed, May 09, 2012 at 01:48:59AM -0500, Thomas Dziedzic wrote:
> On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic <gostrc@...> wrote:
> >> It looks like this was caused by
> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
> >>
> >
> > I will try to see if this was the problem once the next gcc snapshot
> > comes out (this weekend or next week) and try to report back here.
>
> Just tried out the latest gcc snapshot 4.7-20120505
> This segfault still exists so it wasn't caused by gcc bug #53084.
> Also, here is a fedora bug report for the same thing:
> https://bugzilla.redhat.com/show_bug.cgi?id=817196

The day before I posted that email, Debian got an updated gcc-4.7 which
cherry-picked a few fixes from upstream.  With that update, I wasn't
able to reproduce the crash anymore.  #53084 was the upstream bug that
looked like it was most relevant, but maybe that was only part of the
fix.  If you want to dig into it, here's the full list of fixes that
were pulled into the updated package:

    * Update to SVN 20120424 (r186746) from the gcc-4_7-branch.
      - Fix PR libstdc++/52924, PR libstdc++/52591, PR middle-end/52894,
        PR testsuite/53046, PR libstdc++/53067, PR libstdc++/53027,
        PR libstdc++/52839, PR bootstrap/52840, PR libstdc++/52689,
        PR libstdc++/52699, PR libstdc++/52822, PR libstdc++/52942,
        PR middle-end/53084, PR middle-end/52999, PR c/53060,
        PR tree-optimizations/52891, PR target/53033, PR target/53020,
        PR target/52932, PR middle-end/52939, PR tree-optimization/52969,
        PR c/52862, PR target/52775, PR tree-optimization/52943, PR c++/53003,
        PR c++/38543, PR c++/50830, PR c++/50303, PR c++/52292, PR c++/52380,
        PR c++/52465, PR c++/52824, PR c++/52906.

Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@...>

Hi Dominique!

On Mi, 02 Mai 2012, Dominique Pellé wrote:

> Christian Brabandt <cblists@...> wrote:
>
> > Hi
> >
> > On Di, 01 Mai 2012, Axel wrote:
> >
> >> When using the spell correction feature ("set spelllang=de_de spell") a
word containing a german "ß" (0xDF) is displayed incorrectly if it is found to
be misspelled:
> >>
> >> Wir wohnen nicht in der >>>Georgenkirchstraße<<<, sondern in der
>>>Hauptstraße<<<.
> >>
> >> In this sample "Georgenkirchstraße" is flagged as misspelled (as opposed to
"Hauptstraße") - which would be ok - but the "ß" in the flagged word is not
considered as a valid word character; hence the word cannot be directly added
(w/o creating a selection) to the exception list with e.g. "zg".
> >>
> >
> > While I can't say anything about it, I noticed that this crashes my vim
> > with a slight variation of the above sentence:
> >
> > gdb --args ./vim -u NONE -U NONE -N -c ":put ='Wir wohnen nicht in der
>>>Georgenkirch straße<<<, sondern in der >>>Hauptstraße<<<'" -c 'set spell
spelllang=de
> >
> > [Vim starts and puts that sentence in the buffer]
> > :norm! fsz=
> >
> >  SIGSEGV, Segmentation fault.
>
> ...snip...
>
> I also see the German eszett not being highlighted by the
> spelling checker (bug). However, I don't see any crash using
> Linux x86 or Linux x86_64 with Vim-7.3.515.  I used the latest
> German dictionary which Vim downloaded automatically
> when setting ':set spelllang=de'.

I guess, *smp got invalid somehow. This patch prevents, that it gets
overwritten:

diff --git a/src/spell.c b/src/spell.c
--- a/src/spell.c
+++ b/src/spell.c
@@ -14766,6 +14766,9 @@
             z = 0;
             k = 0;
         }
+       /* prevent overwriting of *smp pointer */
+       if (smp != slang->sl_sal.ga_data)
+           smp = (salitem_T *)slang->sl_sal.ga_data;
      }


Mit freundlichen Grüßen
Christian
--

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Wed, May 9, 2012 at 4:29 AM, Christian Brabandt <cblists@...> wrote:
> Hi Thomas!
>
> On Mi, 09 Mai 2012, Thomas Dziedzic wrote:
>
>> On Wed, Apr 25, 2012 at 10:56 PM, Thomas Dziedzic <gostrc@...> wrote:
>> >> It looks like this was caused by
>> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53084.
>> >>
>> >
>> > I will try to see if this was the problem once the next gcc snapshot
>> > comes out (this weekend or next week) and try to report back here.
>>
>> Just tried out the latest gcc snapshot 4.7-20120505
>> This segfault still exists so it wasn't caused by gcc bug #53084.
>> Also, here is a fedora bug report for the same thing:
>> https://bugzilla.redhat.com/show_bug.cgi?id=817196
>
> Shouldn't patch 497 avoid the crash?
>

yes, but as the commit message suggests: "Avoid the crash, doesn't
really fix the problem."

http://code.google.com/p/vim/source/detail?r=e34c620007be9fd805556c43fe848de521f\
3b64c

> regards,
> Christian
>
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Hi there!

After I upgraded my ubuntu to 12.0.4, vim version 7.3.429 behaves
kinda weird.
1. vim file1;
2. :vsp ./    browse and open file2 --- everything is cool;
3. move cursor to window file1;
4. :vsp ./    try to split and browse again, new browsing window
opened, good, but the cursor is moved to window file2 and file2 is not
modifiable.
"i.e. E21: Cannot make changes, 'modifiable' is off" if you try to
edit it.

I suppose it should be the newly opened directory browsing window set
to unmodifiable. not the old file editing window.

/stone

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On May 10, 2012 7:11 AM, "stone" <zmstone@...> wrote:
>
> Hi there!
>
> After I upgraded my ubuntu to 12.0.4, vim version 7.3.429 behaves
> kinda weird.
> 1. vim file1;
> 2. :vsp ./    browse and open file2 --- everything is cool;
> 3. move cursor to window file1;
> 4. :vsp ./    try to split and browse again, new browsing window
> opened, good, but the cursor is moved to window file2 and file2 is not
> modifiable.
> "i.e. E21: Cannot make changes, 'modifiable' is off" if you try to
> edit it.

This has been fixed in a newer version of NetRW.

On May 10, 2012 1:11 PM, "Bovy, Stephen" <Stephen.Bovy@...> wrote:
>
> Further Clarification
>
>  
>
> :hi StatusLine guibg=darkblue                                        
>
>  
>
> StatusLine  HighLighting is only working when the window is split

See ":help 'laststatus'".

Hi

Attached patch adds @Spell to the runtime/syntax/cmake.vim file
so that Vim only highlights spelling mistakes in comments when
editing a CMakeFile with those settings:

   :syntax on
   :set spell

There are still several syntax files which do not contain support
for spelling checker yet. It would be nice to improve them.
I can send other patches for other syntax files (at least for
those I am sufficiently familiar with) if there is an interest.

Regards
-- Dominique

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Hello Dominique,


Excerpt from Dominique Pellé:

> Hi
>
> Attached patch adds @Spell to the runtime/syntax/cmake.vim file
> so that Vim only highlights spelling mistakes in comments when
> editing a CMakeFile with those settings:
>
>   :syntax on
>   :set spell
>
> There are still several syntax files which do not contain support
> for spelling checker yet. It would be nice to improve them.
> I can send other patches for other syntax files (at least for
> those I am sufficiently familiar with) if there is an interest.

I would support such an initiative. I have a liking for bugs that get fixed.
BUT
as one of those who has done such a initiative in the past already i can tell
that there are (imho) bugs in the current model of maintainership of
runtimefiles. This might make such an initiative sadly to a decent degree a
waste of time.
This you should be aware of.


> Regards
> -- Dominique
>

--
Regards,
Thilo

4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6  7C18 89A4 A2A0 C70B 1A8F


--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

I apologize for posting a usage question to this forum

But I do not have the time bandwidth and recourses to monitor two mailing lists

I have searched using  google and  looked at various vim   comments  here and
there

And I cannot figure this out

I have tried using this  >>

source $VIMRUNTIME/mswin.vim

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

But I cannot get the  copy and cut to  put anything on the clipboard

I see the following NOTE:

Under Windows, the * and + registers are equivalent.
For X11 systems, though, they differ. For X11 systems, * is the selection, and +
is the cut buffer (like clipboard).

Does that mean the following settings  in mswin.vim will not work  under Xming
with gvim  and X11 >>

" CTRL-X and SHIFT-Del are Cut
vnoremap <C-X> "+x
vnoremap <S-Del> "+x

" CTRL-C and CTRL-Insert are Copy
vnoremap <C-C> "+y
vnoremap <C-Insert> "+y

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\
>>>>>>

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

This issue is related to
7.3.418(https://groups.google.com/forum/#!topic/vim_dev/_w4mI5MQITs/discussion)
changes.

If completefunc returns -2, Vim is still in Ctrl-X mode.
This behavior some affectons(ex: conflicts IM behavior and flicks "^X
mode" in command line).
So, I added below patch.

This patch is :
If completefunc returns -2, cancel completefunc silently(but still in
Ctrl-X mode).
If completefunc returns -3, exit Ctrl-X mode silently.

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Hi,

I wanted less.vim and less.sh to behave more like 'less'.
The attached patch changes the following behavior:

1. Do not quit Vim automatically at the end of file. (less.vim)
    'more' quits at the end of file, but 'less' does not.

2. Do not wait the input of user, if no arguments were given
    and stdin was not redirected. (less.sh)
    If there is nothing to show, just show an error message and quit.

3. Add a batch file for Windows users. (less.bat)
    This is an alternative of less.sh.

Thanks.
--
Ken Takata

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

cc  -Wl,EDIT=NO,xplink -W l,dll  -o vim objects/buffer.o  objects/blowfish.o 
objects/charset.o  objects/diff.o  objects/digraph.o  objects/edit.o 
objects/eval.o  objects/ex_cmds.o  objects/ex_cmds2.o  objects/ex_docmd.o 
objects/ex_eval.o  objects/ex_getln.o  objects/fileio.o  objects/fold.o 
objects/getchar.o  objects/hardcopy.o  objects/hashtab.o    objects/if_cscope.o 
objects/if_xcmdsrv.o  objects/mark.o  objects/memline.o  objects/menu.o 
objects/message.o  objects/misc1.o  objects/misc2.o  objects/move.o 
objects/mbyte.o  objects/normal.o  objects/ops.o  objects/option.o 
objects/os_unix.o  objects/pathdef.o  objects/popupmnu.o  objects/quickfix.o 
objects/regexp.o  objects/screen.o  objects/search.o  objects/sha256.o 
objects/spell.o  objects/syntax.o    objects/tag.o  objects/term.o  objects/ui.o
objects/undo.o  objects/version.o  objects/window.o  objects/gui.o
objects/gui_motif.o objects/gui_x11.o  objects/pty.o objects/gui_beval.o 
objects/gui_xmdlg.o objects/gui_xmebw.o  objects/main.o  objects/memfile.o    
/usr/lib/Xm_31.x /usr/lib/Xaw_31.x /usr/lib/X11_31.x /usr/lib/SM_31.x
/usr/lib/ICE_31.x -lm -lcurses
link.sh: Linked fine with a few libraries omitted
$ vim -g
Vim: Caught deadly signal SEGV
E852: The child process failed to start the GUI
Press ENTER or type command to continue

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Bram, I reviewed this patch in few weeks ago, and confirmed this patch is
working well.

On Friday, May 11, 2012 8:39:11 AM UTC+9, Shougo wrote:
> This issue is related to
>
7.3.418(https://groups.google.com/forum/#!topic/vim_dev/_w4mI5MQITs/discussion)
> changes.
>
> If completefunc returns -2, Vim is still in Ctrl-X mode.
> This behavior some affectons(ex: conflicts IM behavior and flicks "^X
> mode" in command line).
> So, I added below patch.
>
> This patch is :
> If completefunc returns -2, cancel completefunc silently(but still in
> Ctrl-X mode).
> If completefunc returns -3, exit Ctrl-X mode silently.

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Bovy, Stephen wrote:
> I have tried using this
>
> source $VIMRUNTIME/mswin.vim
>
> But I cannot get the  copy and cut to  put anything on the
> clipboard

First step is to check output of :version to see if you have
+clipboard (feature supported) or -clipboard (not enabled
during build).

I do not know anything about your environment but simple checks
would be, in another application, to copy something and to
select something (leaving it selected).

Then in Vim use commands like:
     "+p
     "*p

John

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Thanks John

Actually  Paste works  great

I can  copy something  into the clip-board    using "note-pad"

And I can past it into  vim

The problem Is I  cannot  copy/cut from vim  and past it into  notepad

>>>>>>>>>>>>>>>>>>

And  for  reference purpose   ( I have verified that this is not an Xming
problem )

I can   copy / paste back and forth     with  ( nedit )  nooo- prooblemo


-----Original Message-----
From: vim_dev@googlegroups.com [mailto:vim_dev@googlegroups.com] On Behalf Of
John Beckett
Sent: Thursday, May 10, 2012 4:55 PM
To: vim_dev@googlegroups.com
Subject: RE: Remote Motif X11 gvim on windows using Xming ( copy cut ) >>
ClipBoard <<<

Bovy, Stephen wrote:
> I have tried using this
>
> source $VIMRUNTIME/mswin.vim
>
> But I cannot get the  copy and cut to  put anything on the clipboard

First step is to check output of :version to see if you have
+clipboard (feature supported) or -clipboard (not enabled
during build).

I do not know anything about your environment but simple checks would be, in
another application, to copy something and to select something (leaving it
selected).

Then in Vim use commands like:
     "+p
     "*p

John

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Hi.

helptags_one extract help tag like '*foo*'. it's used vim_strchr() to find
second '*'. But vim_strchr() depend on current &encoding. Help file should be
latin-1 or utf-8 encoding. So if DBCS is used for &encoding, it may not extract
second '*'.
Below is a patch. Please check and include.

https://gist.github.com/2656714

- Yasuhiro Matsumoto

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Let me clarify >>

Further  research  has uncovered the following

I can  copy   something  to the clip-board with vim   ( but I can only paste the
result into WORD !!!  )  And each line gets an extra blank line added

I cannot  paste the result into  Microsoft  Notepad   Or  into  notepad++

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Ahh ( now nedit  is also  mis-behaving )  maybe it is an Xming bug   (
unfortunately The public version of Xming  is very old )

-----Original Message-----
From: vim_dev@googlegroups.com [mailto:vim_dev@googlegroups.com] On Behalf Of
Bovy, Stephen
Sent: Thursday, May 10, 2012 5:02 PM
To: vim_dev@googlegroups.com
Subject: RE: Remote Motif X11 gvim on windows using Xming ( copy cut ) >>
ClipBoard <<<

Thanks John

Actually  Paste works  great

I can  copy something  into the clip-board    using "note-pad"

And I can past it into  vim

The problem Is I  cannot  copy/cut from vim  and past it into  notepad

>>>>>>>>>>>>>>>>>>

And  for  reference purpose   ( I have verified that this is not an Xming
problem )

I can   copy / paste back and forth     with  ( nedit )  nooo- prooblemo


-----Original Message-----
From: vim_dev@googlegroups.com [mailto:vim_dev@googlegroups.com] On Behalf Of
John Beckett
Sent: Thursday, May 10, 2012 4:55 PM
To: vim_dev@googlegroups.com
Subject: RE: Remote Motif X11 gvim on windows using Xming ( copy cut ) >>
ClipBoard <<<

Bovy, Stephen wrote:
> I have tried using this
>
> source $VIMRUNTIME/mswin.vim
>
> But I cannot get the  copy and cut to  put anything on the clipboard

First step is to check output of :version to see if you have
+clipboard (feature supported) or -clipboard (not enabled
during build).

I do not know anything about your environment but simple checks would be, in
another application, to copy something and to select something (leaving it
selected).

Then in Vim use commands like:
     "+p
     "*p

John

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php