* Stephen P. Wall (swall@...) [000630 08:26]:
> You don't need to change version.c so much.  This should do fine:

The problem is that on some Windows machines, $USER and $HOST aren't
defined..  So, to avoid printing user@ or just @, you need to check..

jon

--
.Jonathan J. Miner------------------Division of Information Technology.
|miner@...                 University Of Wisconsin - Madison|
|608/262.9655                               Room 3149 Computer Science|
`---------------------------------------------------------------------'

  I hope I'm not getting so famous that I can't think out load [sic] anymore.
               -- Larry Wall in <199709032332.QAA21669@...>

Hi,

I like the new cvs commit syntax file in 5.7.  However, with the provided
runtime files, it will only be loaded automatically when the commit file
starts with cvs, followed by a number of digits.  This is not the case on
the platforms I'm working on.  (On Linux, I get something like "cvsW18rmm",
on Windoze 2000 "\2".

I think I know a better way.  As far as I know, the second line of a CVS
commit file always starts with "CVS:"  Therefore, if the following is added
to scripts.vim:

" CVS commit
elseif getline(2) =~ '^CVS:'
    set ft=cvs

it should work everywhere.

Any comments?  (Sorry, no patch)

   - Michael

--
    Michael Schaap - mscha@... - www.mscha.com
    Marne 83, 1186 PE  Amstelveen, The Netherlands
    Phone: (+31) (0)20 6402223 - Fax: (+31) (0)20 7778606

          Habeo nomen domani, ergo sum

On Jun 30, 2000, Michael Schaap wrote:

> I think I know a better way.  As far as I know, the second line of a CVS
> commit file always starts with "CVS:"  Therefore, if the following is added
> to scripts.vim:
>
> " CVS commit
> elseif getline(2) =~ '^CVS:'
>    set ft=cvs
>
> it should work everywhere.
>
> Any comments?  (Sorry, no patch)

That's what I did with my personal hacklet on the subject (all I did was
highlight the 'CVS:' lines as comments, though), and it's always worked
for me.

						 -sbigham

Hello people,


Where would the correct place to submit a revised Apache syntax file be?
(one with better knowledge of what goes in Apache conf files.)


cheers,
--
#!/usr/bin/perl -l -- # -- iain.               <http://eh.org/~koschei/>
$#=rekcaH(lreP(rehtonA(tsuJ()))),$#=~s g $gqq#,#ge;print$#;sub AUTOLOAD{
($_)=$AUTOLOAD=~m m.*::(.*)m;join("\x20",$_[0]).reverse(qq- -,split//);}

Hi,

On Mon, Jul 03, 2000 at 10:18:19AM +0200,
iain truskett <ict-lists@...> wrote:
>
> Hello people,
>
>
> Where would the correct place to submit a revised Apache syntax file be?
> (one with better knowledge of what goes in Apache conf files.)

Usually it's best to send a copy to the syntax file maintainer.

Which of these do you mean?

==> apachestyle.vim <==
" Vim syntax file
" Language:     Apache-style config files (Apache, ProFTPd, etc)
" Maintainer:   Christian Hammers <ch@...>

or

==> apache.vim <==
" Vim syntax file
" Language:     Apache httpd.conf, srm.conf, access.conf
" Maintainer:   Allan Kelly <allan.kelly@...>

Choose the one to contact :)

If the maintainer does not respond for too long, it may be time to send
the new syntax file here instead.

CU,
Thomas

--
  Thomas Köhler Email:   jean-luc@...     | LCARS - Linux
      <><        WWW:     http://jeanluc-picard.de      | for Computers
                 IRC:             jeanluc               | on All Real
                PGP public key available from Homepage! | Starships

Heyo,

* Thomas Köhler (jean-luc@...) [20000703 18:33]:
> iain truskett <ict-lists@...> wrote:
[...]
> > Where would the correct place to submit a revised Apache syntax file be?
> > (one with better knowledge of what goes in Apache conf files.)
>
> Usually it's best to send a copy to the syntax file maintainer.

*slaps forehead* I'm an idiot!

> Which of these do you mean?
>
> ==> apachestyle.vim <==
> or
> ==> apache.vim <==
> " Vim syntax file
> " Language:     Apache httpd.conf, srm.conf, access.conf
> " Maintainer:   Allan Kelly <allan.kelly@...>

apache.vim --- since it's for Apache files, not Apache-like files =)

> Choose the one to contact :)
>
> If the maintainer does not respond for too long, it may be time to
> send the new syntax file here instead.

Sounds like a plan. Thanks for that. =)


cheers,
--
#!/usr/bin/perl -l -- # -- iain.               <http://eh.org/~koschei/>
$#=rekcaH(lreP(rehtonA(tsuJ()))),$#=~s g $gqq#,#ge;print$#;sub AUTOLOAD{
($_)=$AUTOLOAD=~m m.*::(.*)m;join("\x20",$_[0]).reverse(qq- -,split//);}

~> traceroute cvs.vim.org
traceroute to aether.wiggy.net (216.10.33.18), 30 hops max, 38 byte packets
[...]
22  gw.inflicted.net (216.10.33.1)  784.797 ms  975.718 ms  789.819 ms
23  deviant.inflicted.net (216.10.33.3)  789.836 ms  777.249 ms  978.743 ms
24  deviant.inflicted.net (216.10.33.3)  3550.543 ms !H  3516.631 ms !H 
3346.145 ms !H

Host not available :-(

CU,
Thomas

--
  Thomas Köhler Email:   jean-luc@...     | LCARS - Linux
      <><        WWW:     http://jeanluc-picard.de      | for Computers
                 IRC:             jeanluc               | on All Real
                PGP public key available from Homepage! | Starships

Can this be separated out as a separate syntax file in future releases so that
   it can be included in hybrids with other languages lacking a build in
   preprocessor (eg html/java).

   JL


This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

Previously Thomas K?hler wrote:
> ~> traceroute cvs.vim.org
> traceroute to aether.wiggy.net (216.10.33.18), 30 hops max, 38 byte packets
> [...]
> 22  gw.inflicted.net (216.10.33.1)  784.797 ms  975.718 ms  789.819 ms
> 23  deviant.inflicted.net (216.10.33.3)  789.836 ms  777.249 ms  978.743 ms
> 24  deviant.inflicted.net (216.10.33.3)  3550.543 ms !H  3516.631 ms !H 
3346.145 ms !H

Grrr, looks like it. I've alerted the owner of the system..

Wichert.

--
   _________________________________________________________________
  / Generally uninteresting signature - ignore at your convenience  \
| wichert@...                   http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |

John Lonergan wrote:

>   Can this be separated out as a separate syntax file in future releases so
>   that it can be included in hybrids with other languages lacking a build in
>   preprocessor (eg html/java).

It would be possible.  But there will probably be some interaction between the
preprocessor and the language.  It would also be possible to copy the relevant
code from c.vim.  Would that be a big problem?

--
hundred-and-one symptoms of being an internet addict:
163. You go outside for the fresh air (at -30 degrees) but open the
      window first to hear new mail arrive.

///  Bram Moolenaar     Bram@...     http://www.moolenaar.net  \\\
\\\  Vim: http://www.vim.org      ICCF Holland: http://iccf-holland.org  ///

Bram Moolenaar wrote:

> John Lonergan wrote:
>
> >   Can this be separated out as a separate syntax file in future releases so
> >   that it can be included in hybrids with other languages lacking a build in
> >   preprocessor (eg html/java).
>
> It would be possible.  But there will probably be some interaction between the
> preprocessor and the language.  It would also be possible to copy the relevant
> code from c.vim.  Would that be a big problem?

m4 is a better preprocessor for arbitrary languages and
it already has its own syntax file. you could try that.

raf

This gets wierder.

   After a distinct lack of response to my Perl compilation problems, I
just went to have another stab. I unpacked the rt/src tgz afresh,
reconfigured, and remade. However, I'm no longer even getting as far as I
did before!

   In src:


/usr97/gnu/bin/perl -e 'unless ( $] >= 5.005 ) \
    { for (qw(na defgv errgv)) { print "#define PL_$_ $_\n" }}' > if_perl.c
Backslash found where operator expected at -e line 1, near ") \"
         (Missing operator before \?)
syntax error at -e line 1, near ") \"
Execution of -e aborted due to compilation errors.
*** Error code 255
make: Warning: Target `if_perl.c' not remade because of errors
Current working directory /home/nabird/tmp/install/vim-5.7/src


   This command (must include the '\' split) works fine under tcsh/csh but
gives that error under sh (that make uses) and even bash 2.04.


   I can't explain why I had such bizarre errors before, but I similarly
can't explain how this line in the Makefile could ever work for anyone!?


   If I mimic the 5.6 way of doing things:

/usr97/gnu/bin/perl -e 'unless ( $] >= 5.005 \
     ) { for (qw(na defgv errgv)) { print "#define PL_$_ $_\n" }}' >
if_perl.c

   I get the same error.


   However,

/usr97/gnu/bin/perl -e 'unless ( $] >= 5.005 && \
     1 ) { for (qw(na defgv errgv)) { print "#define PL_$_ $_\n" }}' >
if_perl.c


   (a more correct mimic of the 5.6 Makefile) works a treat.


   As a 'proper' fix, removing the '\' sorts it more cleanly.


   Explanation, anyone? (including how anyone else gets it to work!)



   Oh b#gger. Now I'm back to the other error:

if_perl.xs: In function `do_perldo':
if_perl.xs:309: warning: unused variable `Perl___notused'
if_perl.xs: In function `xs_init':
if_perl.xs:374: warning: passing arg 3 of `Perl_newXS' from incompatible
pointer type
if_perl.xs:375: warning: passing arg 3 of `Perl_newXS' from incompatible
pointer type
if_perl.c: At top level:
if_perl.c:392: conflicting types for `XS_VIM_Msg'
proto/if_perl.pro:8: previous declaration of `XS_VIM_Msg'

   etc. etc.

   Oh well.

--
=====================- http://www.racaldefence.com/ -===================
   Neil Bird                      |
                                  |    If this .signature looks pants,
     mailto:neil.bird@...  |     then just stop using Outlook!

Neil Bird wrote:
>   After a distinct lack of response to my Perl compilation problems, I
> just went to have another stab. I unpacked the rt/src tgz afresh,
> reconfigured, and remade. ...

   I think I'm beginning to se the light!


   What seems to work for me is:

- change src/Makefile (can't find a Makefile.in?) to do the first line
creating if_perl.c on one line, not with a '\' split. Can't explain this
one.

- use the attached src/proto/if_perl.pro

- in src/proto.h, replace the CV #define with:

# define XS(p) void p __ARGS((void *cv))

- in if_perl.xs, insert 'pTHXo_' before CV in bootDynLoader & boot_VIM.
I'd rather have found a way to use XS() here to, but that didn't work.


   Two issues:

(a) I don't know whether XS() is used to define routines (from perl
XSUB.h) on other platforms. It's used for my perl 5.5 & 5.6. If it's not,
I don't know what you can use.

(b) I don't know how to correlate the perl 5.6ism 'pTHXo_ CV*' with the
perl 5.5 'CV*' (from the definition of XS()). So, simply including pTHXo_
in if_perl.xs won't fix anything properly, unless the funny bit in the
makefile that *creates* if_perl.c differently for different perls also
creates a dummy '#define pTHXo_' for perl < 5.6

   My vim 5.7.2 now compiles & tests out perfectly, though.


   For ref: Sparc/Solaris 2.5.1, perl 5.6.0 sun4-solaris-thread-multi

--
=====================- http://www.racaldefence.com/ -===================
   Neil Bird                      |
                                  |    If this .signature looks pants,
     mailto:neil.bird@...  |     then just stop using Outlook!

/* if_perl.c */
void perl_end __ARGS((void));
void msg_split __ARGS((char_u *s, int attr));
void perl_win_free __ARGS((WIN *wp));
void perl_buf_free __ARGS((BUF *bp));
int do_perl __ARGS((EXARG *eap));
int do_perldo __ARGS((EXARG *eap));
XS(XS_VIM_Msg);
XS(XS_VIM_SetOption);
XS(XS_VIM_DoCommand);
XS(XS_VIM_Eval);
XS(XS_VIM_Buffers);
XS(XS_VIM_Windows);
XS(XS_VIWIN_DESTROY);
XS(XS_VIWIN_Buffer);
XS(XS_VIWIN_SetHeight);
XS(XS_VIWIN_Cursor);
XS(XS_VIBUF_DESTROY);
XS(XS_VIBUF_Name);
XS(XS_VIBUF_Number);
XS(XS_VIBUF_Count);
XS(XS_VIBUF_Get);
XS(XS_VIBUF_Set);
XS(XS_VIBUF_Delete);
XS(XS_VIBUF_Append);
XS(boot_VIM);

Neil Bird wrote:

>   After a distinct lack of response to my Perl compilation problems, I
> just went to have another stab. I unpacked the rt/src tgz afresh,
> reconfigured, and remade. However, I'm no longer even getting as far as I
> did before!

Strange that you have these problems.  It works fine for me, and others have
reported that they can compile Vim with Perl without modifications.

> /usr97/gnu/bin/perl -e 'unless ( $] >= 5.005 ) \
>    { for (qw(na defgv errgv)) { print "#define PL_$_ $_\n" }}' > if_perl.c
> Backslash found where operator expected at -e line 1, near ") \"
>         (Missing operator before \?)
> syntax error at -e line 1, near ") \"
> Execution of -e aborted due to compilation errors.
> *** Error code 255
> make: Warning: Target `if_perl.c' not remade because of errors
> Current working directory /home/nabird/tmp/install/vim-5.7/src
>
>
>   This command (must include the '\' split) works fine under tcsh/csh but
> gives that error under sh (that make uses) and even bash 2.04.

The removal of the backslashes is done by the make program.  It shouldn't
matter which shell you are using (although the shell might remove backslashes
that make left in).  Perhaps you are using a different "make" this time?

The other problems you report seem to be specific for the Sun version of Perl.
Perhaps this requires re-installing Perl.  Otherwise, if many people use this
Perl version, we might be able to include some configure checks in Vim?

--
hundred-and-one symptoms of being an internet addict:
168. You have your own domain name.

///  Bram Moolenaar     Bram@...     http://www.moolenaar.net  \\\
\\\  Vim: http://www.vim.org      ICCF Holland: http://iccf-holland.org  ///

Bram Moolenaar wrote:
> Strange that you have these problems.  It works fine for me, and others
> have reported that they can compile Vim with Perl without modifications.

   It is a little bizarre. Maybe some people who're actually following this
thread can examine their 5.7 'if_perl.c' to see what the proc. specs. of
things like XS_MIV_Msg have come out as (mine are "XS(XS_VIM_Msg)", e.g.),
and what possible defs. of XS() they have in perl.../CORE/XSUB.h.

   Mine says:

#if defined(__CYGWIN__) && defined(USE_DYNAMIC_LOADING)
#  define XS(name) __declspec(dllexport) void name(pTHXo_ CV* cv)
#else
#  define XS(name) void name(pTHXo_ CV* cv)
#endif

   I'll be picking up the second one; that's where that pTHXo_ jobby comes
from. pTHXo_ is defined in perl.h, but I'm not 100% certain as to what it
comes out to be. Hang on ...

void  XS_VIM_Msg (register PerlInterpreter *my_perl ,   CV* cv) ;
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   My initial guyess would be that it's not 'cos I've built it on a Sun,
but 'cos I've built the multi-threaded version - but then, I built the
threaded perl 5.5.

   It's got a definition:

#ifdef CAN_PROTOTYPE
#ifdef PERL_OBJECT
#define XS(name) void name(CV* cv, CPerlObj* pPerl)
#else
#define XS(name) void name(CV* cv)
#endif
#else
#define XS(name) void name(cv) CV* cv;
#endif

   ... but I can't say which of these I used to pick up.


   It still looks to me as if the 'XS()' macro should be used by vim to
spec. the procedures instead of guessing what that macro outputs.


> > Backslash found where operator expected at -e line 1, near ") \"
> >         (Missing operator before \?)
>
> ...  Perhaps you are using a different "make" this time?

   D'Oh! Yes; I have Sun 'make' and GNU's make installed as 'gmake'.
Previously, vim was one of the few remaining apps. that would build using
either make, so I've become used to not noticing whcih one I type. I'll
make a mental note to use gmake for vim now.

   If it wasn't for tha fact that our work stuff relies on things that Sun
make does that gmake can't, I'd swap permanently!

   [actually, now I come to think about it, for a couple of days recently,
I've been inadvertantly picking up another version of GNU make *called*
make, so that probably caused my confusion]

--
=====================- http://www.racaldefence.com/ -===================
   Neil Bird                      |
                                  |    If this .signature looks pants,
     mailto:neil.bird@...  |     then just stop using Outlook!

Hi,
If I try to tab-complete a filename with a "$" sign in it, the $ is
backslash-escaped, when it shouldn't be. You get this when trying to
complete UNC filenames for files on "hidden" shares (which have a final $ in
the sharename) on NT. For example, assuming you have such a share, typing

:e \\MYSERVER\C$\WINN<tab>

will complete the WINN to WINNT, but will also add a backslash before the $.
This makes the filename invalid :-(

No patch for this, sorry.
Paul.

Moore, Paul wrote:
> Hi,
> If I try to tab-complete a filename with a "$" sign in it, the $ is
> backslash-escaped, when it shouldn't be. You get this when trying to
> complete UNC filenames for files on "hidden" shares (which have a final $
in
> the sharename) on NT. For example, assuming you have such a share, typing
>
> :e \\MYSERVER\C$\WINN<tab>
>
> will complete the WINN to WINNT, but will also add a backslash before the
$.
> This makes the filename invalid :-(

I believe this is because of line 2196 of ex_getln.c:

		     p = vim_strsave_escaped(cmd_files[i],
#ifdef BACKSLASH_IN_FILENAME
						     (char_u *)" *?[{`$%#"
#else
# ifdef COLON_AS_PATHSEP
						     (char_u *)" *?[{`$%#/"
# else
						     (char_u *)"
*?[{`$\\%#'\"|"
# endif
#endif


... which escapes the '$'s in any filename resulting from
expansion/completion. You could try removing the $ from the
BACKSLASH_IN_FILENAME lilst, I don't know if it'll break the
handling of paths with envvars like $VIM/_vimrc etc.

Vince



--
Vince Negri (vnegri@...)
Application Solutions Ltd. Tel:+44(0)1273-476608 Fax:+44(0)1273-478888
Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions Ltd. Information in this
e-mail may be confidential and is for the use of the intended recipient
only, no mistake in transmission is intended to waive or compromise such
privilege. Please advise the sender if you receive this e-mail by mistake.

Bram Moolenaar wrote:
> Strange that you have these problems.  It works fine for me, and others
> have reported that they can compile Vim with Perl without modifications.

I have perl v5.6.0 built, but I was unable to build a vim with perl
support for 5.6*.  Guess I could try again.

Regards,
Dr C

--
         Charles E Campbell, Jr, PhD            _   __   __
         Goddard Space Flight Center           / /_/\_\_/ /
         cec@...      /_/  \/_//_/
   PGP public key: http://www.erols.com/astronaut/pgp.html/

"Dr. Charles E. Campbell" wrote:
> result resembles:  (item on left is a scrollbar)
>
>     +-+----------+
>         | | VIM- | | | <- usual iconify, whole-screen stuff
>     +-+----------+
>     | |1234567890|
>     | |3456789012|
>     | |5678901234|
>     | |7890123456|
>     | |90        |
>     | | ~        |
>     | | ~        |
>     | | ~        |
>     | | ~        |
>      (etc)


   Ah. My mistake - I was looking for <space> gapds, not missing-letter
gaps! Yes, my latest xter/vim does the very same thing at <= 11 chars.
width.

   Just tried with my gnome-terminal, and that's wrong too, but even more
so, & terribly inconsistently, so I'd write that one off for now.

   cmdtool acts much the same.


   Seems to me,

  a) it *is* vim at fault, somehow miscalculating the terminal width.

  b) if you shrink it such that it fails, at least with gnome-tool and
cmdtool you can 'nudge' the windows bigger & suddenly it works OK. Yep,
you can with xterm too, if you're persistent, and resize thge window in
tiny steps (even though they 'snap' the window size to a round no. of
chars!). A little more investiagtion, and the terminal *is* getting bigger
by one char, and 'showing' the missing letters.

   I wonder now if it /is/ vim; I feel that somehow it is, but I can't be
certain.

--
=====================- http://www.racaldefence.com/ -===================
   Neil Bird                      |
                                  |    If this .signature looks pants,
     mailto:neil.bird@...  |     then just stop using Outlook!

>  a) it *is* vim at fault, somehow miscalculating the terminal width.

Vim appears to expect a minimum window size of 12 characters.  The
vanishing characters begin appearing for me when I resize to 11.
Doing a ":set columns?" at that point (or any size less than that)
results in "columns=12".

Ok, I've checked the source, and there is a "MIN_COLUMNS" constant
in vim.h that equates to 12.  In term.c, the function "check_winsize()"
sets the global "Columns" to "MIN_COLUMNS" if it is less than "MIN_COLUMNS".
Without checking deeper, I'd say that this function is called anytime
vim receives a SIGWINCH from the xterm.  This would also explain why the
gui would not shrink smaller than 12 columns.  So there appears to be
a hard limit of 12 columns minimum.

--
Free High Speed DSL Access:
http://in.winfire.com/s/isapiEng.dll/wf.exe?cmd=rl&452,180045277&wf.exe
______________________________________________________________________
                                                     ________  ______
Stephen P. Wall        Redcom Laboratories, Inc.   /  __   /\/  ___/\
Steve_Wall@...  One Redcom Center       ___/  /\/  /_/  /\__\/
(716) 924-7550         Victor, NY 14564       /_____/ /_______/ /
x300                   USA                    \_____\/\_______\/

> From: Neil Bird [mailto:neil.bird@...]
>
>  b) if you shrink it such that it fails, at least with gnome-tool and
> cmdtool you can 'nudge' the windows bigger & suddenly it
> works OK. Yep,
> you can with xterm too, if you're persistent, and resize thge
> window in
> tiny steps (even though they 'snap' the window size to a round no. of
> chars!). A little more investiagtion, and the terminal *is*
> getting bigger
> by one char, and 'showing' the missing letters.

I just tried the following, having a xterm/vim with 11 visible columns
   :se colums?
gives 12
   :sh
   echo $COLUMNS
gives 11

>
>   I wonder now if it /is/ vim; I feel that somehow it is, but
> I can't be
> certain.

So do/am I

Michael

Hi,
I'm currently working on StoryServer templates. That's mostly html,
containing embedded tcl. Now, I have my own version of html.vim:
au! Syntax html so ~/vim/mysyntaxfiles/html.vim
In this file, I added a few extra lines like this:

if main_syntax == 'storyserver'
   syn match   embTclComment +\[\s*#.*\]+
   syn match   tclMatch  +<=+
   syn match   tclMatch  +< +me=e-1
   syn region  embTcl start=+\[+ end=+\]+
contains=embTclComment,embTcl,@htmlTcl,htmlTag,htmlEndTag,tclMatch
   syn include @htmlTcl <sfile>:p:h/tcl.vim

   syn cluster htmlPreproc      add=embTcl
   syn cluster htmlPreproc      add=embTclComment
endif

Now, what's the problem? Here it is: embedded tcl can also be nested, so
every syntax item in tcl.vim should also have a
"contains=embTcl,embTclComment" added. (of course, syn keyword could be
ignored).
I did this for tclString for the moment, but the real problem is: Now, I
also need an extra copy of tcl.vim, not only of html.vim - this is bad.
Is it possible to change vim to allow something like this?
   syn include @htmlTcl <sfile>:p:h/tcl.vim contains=embTcl,embTclComment
                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                            this is the new part: add
                                            contains to all syntax items
                                            from tcl.vim

(the next problem, to match HTML-Tags within embeded tcl parts, while
<,>,<=,>= are also allowed is just another piece of fun so far: without
the above tclMatch hack, highlightning just goes mad :-))

CU,
Thomas

--
  Thomas Köhler Email:   jean-luc@...     | LCARS - Linux
      <><        WWW:     http://jeanluc-picard.de      | for Computers
                 IRC:             jeanluc               | on All Real
                PGP public key available from Homepage! | Starships

Hello,

weird: view the attached file with vim.

--
    Johannes

" the ^a stands for `any command'

a "\<c-d>"
a ":\<c-d>"
a "::\<c-d>"
a ": :\<c-d>"
a "::::\<c-d>"
a ":::aa:\<c-d>"
a ":::au:\<c-d>"
a "a\<c-d>"
a "aa\<c-d>"
a ":aa\<c-d>"
a ": a\<c-d>"

" single quotes do correct highlighting
a '\<c-d>'
a ':\<c-d>'
a '::\<c-d>'
a ': :\<c-d>'
a '::::\<c-d>'
a ':::aa:\<c-d>'
a ':::au:\<c-d>'
a 'a\<c-d>'
a 'aa\<c-d>'
a ':aa\<c-d>'
a ': a\<c-d>'

Hello!

There was a bit of a bug; only the ": should have been highlighted as
vimRegister, not ":: .  However, the fix for that (available at
http://www.erols.com/astronaut/vim/syntax/vim.vim.gz) doesn't really
improve the situation that JZ noticed.

Its difficult to have the syntax properly and generally decide when one has a
register ("a), a comment ("....), or a string ("...").  A way to do it so that
<vim.vim> syntax highlighting which perhaps has the potential of being correct
more often is to go through all the individual commands and write syntax
handling for each one, separately.  That would result in an enormous
slower-than-a-snail syntax-highlighting file.  Shucks, <vim.vim> is already
big.

There are more difficulties, however; consider the substitute command.
The text indicates that

:[range]s[ubstitute]/{pattern}/{string}/[c][e][g][p][r][i][I] [count]
..etc..

but actually the "/"s may be most if not all punctuation characters.  So
consider

:s!"this!is a sub"!

You can even apply this particular sub to itself.

Needless to say, <vim.vim> as it currently stands doesn't highlight that
properly.  I suspect that the vim language isn't a LALR grammar due to this
sort of thing (ie. its not context-free).  The new 6.0 coming out should allow
one to pass start patterns to ending patterns, so this particular construct'
associated syntax highlighting may have a fix in the near future (I believe
Bram said about two weeks!).  I'll have to see about the (unexpected)
interactions, though.

In the problematic cases in JZ's example below, most of them depend on the fact
that ": is a (read-only) register.  There are several special registers that are
accessed via punctuation: "[-:.%#=*_/] (see :he registers).  <vim.vim> is having
a problem deciding when to highlight as a vimRegister vs as a vimString.

Regards,
Dr C

  ---------------------------------------------------------------------
Thus saith Johannes Zellner:  wierd!
" the ^a stands for `any command'
a "\<c-d>"
a ":\<c-d>"
a "::\<c-d>"
a ": :\<c-d>"
a "::::\<c-d>"
a ":::aa:\<c-d>"
a ":::au:\<c-d>"
a "a\<c-d>"
a "aa\<c-d>"
a ":aa\<c-d>"
a ": a\<c-d>"
  ---------------------------------------------------------------------

--
         Charles E Campbell, Jr, PhD            _   __   __
         Goddard Space Flight Center           / /_/\_\_/ /
         cec@...      /_/  \/_//_/
   PGP public key: http://www.erols.com/astronaut/pgp.html/

Hello!

I think one of my <engspchk.vim> users found a hidden reserved syntax
modifier; try this out:

vi tmp
:so tmp.vim

with the following two files:

  -- <tmp> ------------------------------------------------------------
fold crumple
  -- <tmp.vim> --------------------------------------------------------
syn clear
syn keyword Example1 fold
syn keyword Example2 crumple
hi  link    Example1 Statement
hi  link    Example2 PreProc
  ---------------------------------------------------------------------

You'll see that "crumple" gets highlighted as PreProc which is just fine, but
"fold" does *not* get highlighted as Statement.  Sounds like "fold" is a
reserved word for the 6.0 future!

Just guessing,
Dr C

--
         Charles E Campbell, Jr, PhD            _   __   __
         Goddard Space Flight Center           / /_/\_\_/ /
         cec@...      /_/  \/_//_/
   PGP public key: http://www.erols.com/astronaut/pgp.html/

> From: "Dr. Charles E. Campbell" <cec@...>
>
> I think one of my <engspchk.vim> users found a hidden reserved syntax
> modifier; try this out:
>
...
> "fold" does *not* get highlighted as Statement.  Sounds like "fold"
> is a reserved word for the 6.0 future!

:help added-5.7
...
"display" and "fold" arguments for syntax items.  For future
extension, they are ignored now.


--
Free High Speed DSL Access:
http://in.winfire.com/s/isapiEng.dll/wf.exe?cmd=rl&452,180045277&wf.exe
______________________________________________________________________
                                                     ________  ______
Stephen P. Wall        Redcom Laboratories, Inc.   /  __   /\/  ___/\
Steve_Wall@...  One Redcom Center       ___/  /\/  /_/  /\__\/
(716) 924-7550         Victor, NY 14564       /_____/ /_______/ /
x300                   USA                    \_____\/\_______\/

Hello,

I just wasn't able to find a nice solution to do
sort of a `multiview' with vim functions. So this
is an idea for a new feature `set multiview=...'

Examples:

latex:

     " vim settings
     set multiview=.tex
     set path=.,$TEXINPUTS

     % latex file
     \include{dyn}

     and placing the cursor on dyn and typing `gf' should search
     in the path first for dyn and if not found (which is likely)
     search for dyn.tex


python:

     " vim settings
     set multiview=.py
     set path=.,/usr/lib/python1.5
     set include=import

     # python file
     import code
     compile_command('print "fred"')

     and placing the cursor on `compile_command' and typing `[i'
     should take me to /usr/lib/python1.5/code.py


generally one could also benfit from

     set multiview=.gz,.bz2


Comments ?  maybe something for the TODO list ?

--
    Johannes

> From: Johannes Zellner <johannes@...>
>
>     " vim settings
>     set multiview=.tex
>     set path=.,$TEXINPUTS
>
>     % latex file
>     \include{dyn}
>
>     and placing the cursor on dyn and typing `gf' should search
>     in the path first for dyn and if not found (which is likely)
>     search for dyn.tex

An option along these lines is in the offing for vim 6.0.

--
Free High Speed DSL Access:
http://in.winfire.com/s/isapiEng.dll/wf.exe?cmd=rl&452,180045277&wf.exe
______________________________________________________________________
                                                     ________  ______
Stephen P. Wall        Redcom Laboratories, Inc.   /  __   /\/  ___/\
Steve_Wall@...  One Redcom Center       ___/  /\/  /_/  /\__\/
(716) 924-7550         Victor, NY 14564       /_____/ /_______/ /
x300                   USA                    \_____\/\_______\/

Charles Campbell wrote:

> I think one of my <engspchk.vim> users found a hidden reserved syntax
> modifier; try this out:
>
> vi tmp
> :so tmp.vim
>
> with the following two files:
>
>  -- <tmp> ------------------------------------------------------------
> fold crumple
>  -- <tmp.vim> --------------------------------------------------------
> syn clear
> syn keyword Example1 fold
> syn keyword Example2 crumple
> hi  link    Example1 Statement
> hi  link    Example2 PreProc
>  ---------------------------------------------------------------------
>
> You'll see that "crumple" gets highlighted as PreProc which is just fine, but
> "fold" does *not* get highlighted as Statement.  Sounds like "fold" is a
> reserved word for the 6.0 future!

Right.  Just above ":help fixed-5.7":

	 "display" and "fold" arguments for syntax items.  For future
	 extension, they are ignored now.

One complication: "fold" can no longer be used as a keyword.  It requires
using a match item.  Same for "syntax", which is a problem with vim.vim.
Oops, forgot about that for the 5.7 release...

--
hundred-and-one symptoms of being an internet addict:
183. You move your coffeemaker next to your computer.

///  Bram Moolenaar     Bram@...     http://www.moolenaar.net  \\\
\\\  Vim: http://www.vim.org      ICCF Holland: http://iccf-holland.org  ///

Johannes Zellner wrote:

> I just wasn't able to find a nice solution to do
> sort of a `multiview' with vim functions. So this
> is an idea for a new feature `set multiview=...'

For Vim ("real soon now") 6.0 there will be the 'suffixesadd' option.
I think it does what you expect from "multiview".  Here is the help for the
option:

'suffixesadd' 'sua' string (default "")
			 local to buffer
			 {not in Vi}
			 {not available when compiled without the
			 |+file_in_path| feature}
	 Comma separated list of suffixes, which are used when searching for a
	 file for the "gf", "[I", etc. commands.  Example:
		 :set suffixesadd=.java

It's still a bit short...

--
hundred-and-one symptoms of being an internet addict:
187. You promise yourself that you'll only stay online for another
      15 minutes...at least once every hour.

///  Bram Moolenaar     Bram@...     http://www.moolenaar.net  \\\
\\\  Vim: http://www.vim.org      ICCF Holland: http://iccf-holland.org  ///