Re: Set mouse=a causes Vim to hang in screen.
On Fri, Jan 11, 2008 at 08:51:56PM -0500, James Vega wrote: > > The following caused Vim to hang: > > > > 1. Create /tmp/vimrc with the following lines: > > > > set nocp > > set mouse=a > > > > 2. Run screen, and then do > > > > $ vim -u /tmp/vimrc > > > > Vim hangs before starting up. > > But it does finish starting? Nope! Just hangs for ever. However when I kill it (using "kill" -- Ctrl-C is ignored), it leaves the intro message drawn on the screen. > Sounds like you have a $DISPLAY environment variable which is > incorrect and Vim is (unsuccessfully) attempting to connect to the X > server. Well, the same problem is caused when I do "vim -X". Also, "env TERM=rxvt vim" connects to the X server just fine (in fact, even gvim runs). Can anyone else reproduce this? GI PS: The target host system is Scientific Linux, and I'm running Vim-7.1 with patches 1--215. -- The Geek shall inherit the earth. - Linus 5:5 --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Set mouse=a causes Vim to hang in screen.
On Jan 11, 2008 8:08 PM, Gautam Iyer <[EMAIL PROTECTED]> wrote: > The following caused Vim to hang: > > 1. Create /tmp/vimrc with the following lines: > > set nocp > set mouse=a > > 2. Run screen, and then do > > $ vim -u /tmp/vimrc > > Vim hangs before starting up. But it does finish starting? Sounds like you have a $DISPLAY environment variable which is incorrect and Vim is (unsuccessfully) attempting to connect to the X server. James --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Set mouse=a causes Vim to hang in screen.
Hi All, The following caused Vim to hang: 1. Create /tmp/vimrc with the following lines: set nocp set mouse=a 2. Run screen, and then do $ vim -u /tmp/vimrc Vim hangs before starting up. GI PS: Note -- doing "env TERM=rxvt vim -u /tmp/vimrc" works perfectly even under screen. -- All wiyht. Rho sritched mg kegtops awound? --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: vm71 can not be compiled on opensolaris
jiandong lu wrote: > vm71 can not be compiled on opensolaris (solaris > express developer edition ,9/07,b70).The key error > message is : > > Undefined first referenced > symbol in file > XmeXpmReadFileToPixmap > objects/gui_xmebw.o > XmeXpmFreeAttributes > objects/gui_xmebw.o > XmeXpmCreatePixmapFromData > objects/gui_xmebw.o > ld: fatal: Symbol referencing errors. No output > written to vim > *** Error code 1 > The following command caused the error: > LINK=" gcc -L/usr/dt/lib -R /usr/dt/lib > -L/usr/openwin/lib -R/usr/openwin/lib \ > -o vim objects/buffer.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.oobjects/if_cscope.o > objects/if_xcmdsrv.o objects/main.o objects/mark.o > objects/memfile.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/spell.o objects/syntax.o > objects/tag.o objects/term.o objects/ui.o > objects/undo.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.oobjects/netbeans.o > objects/version.o -lXp -lXmu -lXext -lXm -lXt -lSM > -lICE -lXpm -lXt -lX11 -lSM -lICE -lw -ldl -ltermlib > -lelf -lnsl -lsocket " \ > MAKE="make" sh ./link.sh > make: Fatal error: Command failed for target `vim' > Current working directory > /export/home/jiandong/Desktop/vim71/src > *** Error code 1 > make: Fatal error: Command failed for target `first' > > > hope that the problem be addressed in the next > release. > > > > ___ > 雅虎邮箱传递新年祝福，个性贺卡送亲朋！ > http://cn.mail.yahoo.com/gc/index.html?entry=5&souce=mail_mailletter_tagline > > > > Hmm... three symbols whose names start with XmeXpm, used in gui_xmebw.c "Enhanced Motif PushButton widget with move over behavior"... apparently in an include file since the C file itself doesn't include those words... 1. Try removing the file auto/link.sed and recompiling. This might work if a library which wasn't needed before (and had been removed via auto/link.sed) is needed now. The file will be recreated if not found and the link proceeds OK. 2. If that doesn't work, try re-running configure (e.g., using "make reconfig"). This may get you a different message about what is wrong with your software installation. 3. If that doesn't work, and you have GTK2 installed (with "development" package including C headers etc.), maybe you could try building with that? (this also requires a reconfig, but possibly with different configure arguments). Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 230. You spend your Friday nights typing away at your keyboard --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
vm71 can not be compiled on opensolaris
vm71 can not be compiled on opensolaris (solaris express developer edition ,9/07,b70).The key error message is : Undefined first referenced symbol in file XmeXpmReadFileToPixmap objects/gui_xmebw.o XmeXpmFreeAttributes objects/gui_xmebw.o XmeXpmCreatePixmapFromData objects/gui_xmebw.o ld: fatal: Symbol referencing errors. No output written to vim *** Error code 1 The following command caused the error: LINK=" gcc -L/usr/dt/lib -R /usr/dt/lib -L/usr/openwin/lib -R/usr/openwin/lib \ -o vim objects/buffer.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.oobjects/if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o objects/memfile.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/spell.o objects/syntax.o objects/tag.o objects/term.o objects/ui.o objects/undo.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.oobjects/netbeans.o objects/version.o -lXp -lXmu -lXext -lXm -lXt -lSM -lICE -lXpm -lXt -lX11 -lSM -lICE -lw -ldl -ltermlib -lelf -lnsl -lsocket " \ MAKE="make" sh ./link.sh make: Fatal error: Command failed for target `vim' Current working directory /export/home/jiandong/Desktop/vim71/src *** Error code 1 make: Fatal error: Command failed for target `first' hope that the problem be addressed in the next release. ___ 雅虎邮箱传递新年祝福，个性贺卡送亲朋！ http://cn.mail.yahoo.com/gc/index.html?entry=5&souce=mail_mailletter_tagline --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Patch 7.1.218
Patch 7.1.218
Problem:A syntax region without a "keepend", containing a region with
"extend" could be truncated at the end of the containing region.
Solution: Do not call syn_update_ends() when there are no keepend items.
Files: src/syntax.c
*** ../vim-7.1.217/src/syntax.c Thu Jan 10 22:23:22 2008
--- src/syntax.cWed Jan 9 15:17:47 2008
***
*** 2495,2501
if (current_state.ga_len == 0)
break;
! if (had_extend)
{
syn_update_ends(FALSE);
if (current_state.ga_len == 0)
--- 2493,2499
if (current_state.ga_len == 0)
break;
! if (had_extend && keepend_level >= 0)
{
syn_update_ends(FALSE);
if (current_state.ga_len == 0)
*** ../vim-7.1.217/src/version.cFri Jan 11 21:00:49 2008
--- src/version.c Fri Jan 11 21:25:46 2008
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 218,
/**/
--
The Law of VIM:
For each member b of the possible behaviour space B of program P, there exists
a finite time t before which at least one user u in the total user space U of
program P will request b becomes a member of the allowed behaviour space B'
(B' <= B).
In other words: Sooner or later everyone wants everything as an option.
-- Vince Negri
/// 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: [PATCH] Cross-compilation patch to avoid looking for /usr/local at compile time
Marc Haisenko wrote: > On Thursday 10 January 2008, Bram Moolenaar wrote: > > The reason you don't hear from me is that most of my emails to you > > bounce back. > > Ouch, that's bad... don't know why that happens. > > > 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. > > Philip's patch is independent of mine, I think... the problem it addresses > just happened to bite him while 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). > > What about the main "configure.in fixes for cross-compiling" patch by > me ? Is there anything I need to tweak so you can accept it or is > there some reason why you'd say the patch wouldn't be necessary ? When adding a new argument to configure it's always good to document this in the appropriate places. > Don't get me wrong, I wouldn't be mad if you'd declined it, I just want a > definitive "accepted" or "declined". I still need to look into this. Configure patches are always tricky. -- If "R" is Reverse, how come "D" is FORWARD? /// 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 -~--~~~~--~~--~--~---
Patch 7.1.217
Patch 7.1.217
Problem:The "help-tags" tag may be missing from runtime/doc/tags when it
was generated during "make install".
Solution: Add the "++t" argument to ":helptags" to force adding the tag.
Files: runtime/doc/Makefile, runtime/doc/various.txt, src/ex_cmds.c,
src/ex_cmds.h
*** ../vim-7.1.216/runtime/doc/Makefile Sat May 5 19:14:15 2007
--- runtime/doc/MakefileFri Jan 11 20:55:34 2008
***
*** 301,307
# Use Vim to generate the tags file. Can only be used when Vim has been
# compiled and installed. Supports multiple languages.
vimtags: $(DOCS)
! $(VIMEXE) -u NONE -esX -c "helptags ." -c quit
# Use "doctags" to generate the tags file. Only works for English!
tags: doctags $(DOCS)
--- 301,307
# Use Vim to generate the tags file. Can only be used when Vim has been
# compiled and installed. Supports multiple languages.
vimtags: $(DOCS)
! $(VIMEXE) -u NONE -esX -c "helptags ++t ." -c quit
# Use "doctags" to generate the tags file. Only works for English!
tags: doctags $(DOCS)
*** ../vim-7.1.216/runtime/doc/various.txt Sat May 12 17:05:26 2007
--- runtime/doc/various.txt Fri Jan 11 20:45:45 2008
***
*** 1,4
! *various.txt* For Vim version 7.1. Last change: 2007 Jan 14
VIM REFERENCE MANUALby Bram Moolenaar
--- 1,4
! *various.txt* For Vim version 7.1. Last change: 2008 Jan 11
VIM REFERENCE MANUALby Bram Moolenaar
***
*** 748,754
*:helpt* *:helptags*
*E154* *E150* *E151* *E152* *E153* *E670*
! :helpt[ags] {dir} Generate the help tags file(s) for directory {dir}.
All "*.txt" and "*.??x" files in the directory are
scanned for a help tag definition in between stars.
The "*.??x" files are for translated docs, they
--- 754,761
*:helpt* *:helptags*
*E154* *E150* *E151* *E152* *E153* *E670*
! :helpt[ags] [++t] {dir}
! Generate the help tags file(s) for directory {dir}.
All "*.txt" and "*.??x" files in the directory are
scanned for a help tag definition in between stars.
The "*.??x" files are for translated docs, they
***
*** 756,761
--- 763,771
The generated tags files are sorted.
When there are duplicates an error message is given.
An existing tags file is silently overwritten.
+ The optional "++t" argument forces adding the
+ "help-tags" tag. This is also done when the {dir} is
+ equal to $VIMRUNTIME/doc.
To rebuild the help tags in the runtime directory
(requires write permission there): >
:helptags $VIMRUNTIME/doc
*** ../vim-7.1.216/src/ex_cmds.cWed Jan 9 22:39:55 2008
--- src/ex_cmds.c Fri Jan 11 20:47:13 2008
***
*** 6091,6097
}
#if defined(FEAT_EX_EXTRA) || defined(PROTO)
! static void helptags_one __ARGS((char_u *dir, char_u *ext, char_u *lang));
/*
* ":helptags"
--- 6091,6097
}
#if defined(FEAT_EX_EXTRA) || defined(PROTO)
! static void helptags_one __ARGS((char_u *dir, char_u *ext, char_u *lang, int
add_help_tags));
/*
* ":helptags"
***
*** 6110,6115
--- 6110,6123
char_ufname[8];
int filecount;
char_u**files;
+ int add_help_tags = FALSE;
+
+ /* Check for ":helptags ++t {dir}". */
+ if (STRNCMP(eap->arg, "++t", 3) == 0 && vim_iswhite(eap->arg[3]))
+ {
+ add_help_tags = TRUE;
+ eap->arg = skipwhite(eap->arg + 3);
+ }
if (!mch_isdir(eap->arg))
{
***
*** 6192,6198
ext[1] = fname[5];
ext[2] = fname[6];
}
! helptags_one(eap->arg, ext, fname);
}
ga_clear(&ga);
--- 6200,6206
ext[1] = fname[5];
ext[2] = fname[6];
}
! helptags_one(eap->arg, ext, fname, add_help_tags);
}
ga_clear(&ga);
***
*** 6200,6214
#else
/* No language support, just use "*.txt" and "tags". */
! helptags_one(eap->arg, (char_u *)".txt", (char_u *)"tags");
#endif
}
static void
! helptags_one(dir, ext, tagfname)
! char_u*dir; /* doc directory */
! char_u*ext; /* suffix, ".txt", ".itx", ".frx", etc. */
! char_u*tagfname;/* "tags" for English, "tags-it" for Italian. */
{
FILE *fd_tags;
FILE *fd;
--- 6208,6223
#else
/* No language support, just
Re: --remote-tab-silent not mentioned in --help
Nico Weber wrote: > > 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. Thanks. I had actually already done something like this but haven't sent out the patch yet. -- Q: How do you tell the difference between a female cat and a male cat? A: You ask it a question and if HE answers, it's a male but, if SHE answers, it's a female. /// 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: Patch for Unix filename expansion to try out
Charles Campbell wrote:
> 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.
I can reproduce the problem. Only with ksh, it works fine with tcsh,
bash and sh.
--
TALL KNIGHT: When you have found the shrubbery, then you must cut down the
mightiest tree in the forest ... with a herring.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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
-~--~~~~--~~--~--~---
Patch 7.1.216
Patch 7.1.216
Problem:Variants of --remote-tab are not mentioned for "vim --help".
Solution: Display optional -wait and -silent.
Files: src/main.c
*** ../vim-7.1.215/src/main.c Tue Sep 25 17:54:41 2007
--- src/main.c Sun Dec 30 15:09:11 2007
***
*** 3081,3087
main_msg(_("--remote-wait As --remote but wait for files to have
been edited"));
main_msg(_("--remote-wait-silent Same, don't complain if there
is no server"));
# ifdef FEAT_WINDOWS
! main_msg(_("--remote-tab As --remote but open tab page for each
file"));
# endif
main_msg(_("--remote-send \tSend to a Vim server and exit"));
main_msg(_("--remote-expr \tEvaluate in a Vim server and
print result"));
--- 3081,3087
main_msg(_("--remote-wait As --remote but wait for files to have
been edited"));
main_msg(_("--remote-wait-silent Same, don't complain if there
is no server"));
# ifdef FEAT_WINDOWS
! main_msg(_("--remote-tab[-wait][-silent] As --remote but use tab
page per file"));
# endif
main_msg(_("--remote-send \tSend to a Vim server and exit"));
main_msg(_("--remote-expr \tEvaluate in a Vim server and
print result"));
*** ../vim-7.1.215/src/version.cThu Jan 10 22:23:22 2008
--- src/version.c Fri Jan 11 20:25:14 2008
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 216,
/**/
--
TIM: But follow only if you are men of valour. For the entrance to this cave
is guarded by a monster, a creature so foul and cruel that no man yet has
fought with it and lived. Bones of full fifty men lie strewn about its
lair ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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: When will 7.2 come out?
Edward L. Fox wrote: >There are already more than 200 patches. When will 7.2 come out? Any plans? > > > Well, I'm not Bram, but I believe that the todo list still has over 100 items on it. Chip Campbell --~--~-~--~~~---~--~~ 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
On Thursday 10 January 2008, Bram Moolenaar wrote: > The reason you don't hear from me is that most of my emails to you > bounce back. Ouch, that's bad... don't know why that happens. > 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. Philip's patch is independent of mine, I think... the problem it addresses just happened to bite him while 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). What about the main "configure.in fixes for cross-compiling" patch by me ? Is there anything I need to tweak so you can accept it or is there some reason why you'd say the patch wouldn't be necessary ? Don't get me wrong, I wouldn't be mad if you'd declined it, I just want a definitive "accepted" or "declined". Bye, Marc -- 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 -~--~~~~--~~--~--~---
Re: Repost: [PATCH] Enable cross-compiling
> Sorry, haven't received anything. Could you please forward it to me ? > Thank you, > Marc I think the note was for Philip Prindeville, but it is relevant to all contributors to the patch, I'm sure. I'll send it to all you guys while I'm at it. It's so frustrating when email systems decide to be grumpy and drop mail like this. Ben. Bram wrote: 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). -- 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: Repost: [PATCH] Enable cross-compiling
On Thursday 10 January 2008, Ben Schmidt wrote: > > > 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. Sorry, haven't received anything. Could you please forward it to me ? Thank you, Marc -- 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 -~--~~~~--~~--~--~---
Re: [PATCH] Cross-compilation patch to avoid looking for/usr/local at compile time
On Thu, 2008-01-10 at 22:10 +0100, Bram Moolenaar wrote:
> Philip Prindeville wrote:
> 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.
Thank you for the trigger to rework my old patch
http://www.mail-archive.com/[EMAIL PROTECTED]/msg02896.html
to check gcc if it already uses the wanted local-dir.
/haubi/
--
13. - 14. Februar 2008
Salomon Automation am 6. Hamburger Logistiktag, Kreuzfahrtterminal Hamburg,
Deutschland
19. - 21. Februar 2008
Salomon Automation auf der LogiMAT 2008, Neue Messe Stuttgart, Deutschland
Halle 6, Stand 527
23. - 27. Februar 2008
MoveRetail auf der EuroShop 2008 in Düsseldorf, Deutschland
Halle 6, Stand C50
Salomon Automation GmbH - Friesachstrasse 15 - A-8114 Friesach bei Graz
Sitz der Gesellschaft: Friesach bei Graz
UID-NR:ATU28654300 - Firmenbuchnummer: 49324 K
Firmenbuchgericht: Landesgericht für Zivilrechtssachen Graz
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
--- src/configure.in.orig 2008-01-11 09:29:46.0 +0100
+++ src/configure.in 2008-01-11 10:21:34.0 +0100
@@ -189,27 +189,45 @@
dnl Add /usr/local/lib to $LDFLAGS and /usr/local/include to CFLAGS.
dnl Only when the directory exists and it wasn't there yet.
dnl For gcc don't do this when it is already in the default search path.
+AC_MSG_CHECKING(for local dir)
+local_dir=/usr/local
have_local_include=''
have_local_lib=''
-if test "$GCC" = yes; then
+AC_ARG_WITH(local-dir, [dnl
+ --with-local-dir=/path build with /path/include, /path/lib [[/usr/local]]
+ --without-local-dir do not build with /usr/local/include, /usr/local/lib], [
+ local_dir="$withval"
+ case "$withval" in
+ */*) ;;
+ no) local_dir= ;;
+ *) AC_MSG_ERROR(must pass path argument or 'no' to --with-local-dir) ;;
+ esac
+])
+if test -z "${local_dir}"; then
+# avoid adding local dir to LDFLAGS and CPPFLAGS
+have_local_dir=yes
+have_local_lib=yes
+fi
+if test -n "${local_dir}" -a "$GCC" = yes; then
echo 'void f(){}' > conftest.c
dnl -no-cpp-precomp is needed for OS X 10.2 (Ben Fowler)
- have_local_include=`${CC-cc} -no-cpp-precomp -c -v conftest.c 2>&1 | grep '/usr/local/include'`
- have_local_lib=`${CC-cc} -c -v conftest.c 2>&1 | grep '/usr/local/lib'`
+ have_local_include=`${CC-cc} -no-cpp-precomp -c -v conftest.c 2>&1 | grep "${local_dir}/include"`
+ have_local_lib=`${CC-cc} -c -v conftest.c 2>&1 | grep "${local_dir}/lib"`
rm -f conftest.c conftest.o
fi
-if test -z "$have_local_lib" -a -d /usr/local/lib; then
- tt=`echo "$LDFLAGS" | sed -e 's+-L/usr/local/lib ++g' -e 's+-L/usr/local/lib$++g'`
+if test -z "$have_local_lib" -a -d "${local_dir}"/lib; then
+ tt=`echo "$LDFLAGS" | sed -e "s+-L${local_dir}lib ++g" -e "s+-L${local_dir}/lib$++g"`
if test "$tt" = "$LDFLAGS"; then
-LDFLAGS="$LDFLAGS -L/usr/local/lib"
+LDFLAGS="$LDFLAGS -L${local_dir}/lib"
fi
fi
-if test -z "$have_local_include" -a -d /usr/local/include; then
- tt=`echo "$CPPFLAGS" | sed -e 's+-I/usr/local/include ++g' -e 's+-I/usr/local/include$++g'`
+if test -z "$have_local_include" -a -d "${local_dir}"/include; then
+ tt=`echo "$CPPFLAGS" | sed -e "s+-I${local_dir}/include ++g" -e "s+-I${local_dir}/include$++g"`
if test "$tt" = "$CPPFLAGS"; then
-CPPFLAGS="$CPPFLAGS -I/usr/local/include"
+CPPFLAGS="$CPPFLAGS -I${local_dir}/include"
fi
fi
+AC_MSG_RESULT($local_dir)
AC_MSG_CHECKING(--with-vim-name argument)
AC_ARG_WITH(vim-name, [ --with-vim-name=NAMEwhat to call the Vim executable],
Re: Bug in syntax/mail.vim
On 10/01/2008 19:39, James Vega 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, Chapter and verse please, for education purposes. My reading of 3986 (which updates 1738) allows ( and ) to appear in URLs with no requirement to percent encode. Percent encoding of any URL characters that do no otherwise require them should only happen when those characters are used to indicate components within the URL. Obviously this could be any character, including alphanums! > 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. Mike -- Youth would be an ideal state if it came a little later in life. --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
