enabling tag_any_white

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

enabling tag_any_white

robert h-2
I am trying to help someone that posted in the /r/vim Reddit forum. They are trying to get "tag_any_white" compiled in.

He has tried the following:

configure:15432: WARNING: unrecognized options: --with-tag_any_white
configure:15432: WARNING: unrecognized options: --enable-tag_any_white

Neither worked...

Thanks,

Bob

--
--
You received this message from the "vim_use" 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: enabling tag_any_white

Christian Brabandt

On Do, 13 Jul 2017, Robert wrote:

> I am trying to help someone that posted in the /r/vim Reddit forum. They are trying to get "tag_any_white" compiled in.
>
> He has tried the following:
>
> configure:15432: WARNING: unrecognized options: --with-tag_any_white
> configure:15432: WARNING: unrecognized options: --enable-tag_any_white
>
> Neither worked...

I already wondered why the OP at reddit wanted to enable all those
features, even if they do not make sense like ebcdic. It seems one can
only enable tag_any_white by editing feature.h. Is there any tag program, that
needs that?

,----[ feature.h ]
|   /*
|    * +tag_any_white       Allow any white space to separate the fields in a tags
|    *                      file.  When not defined, only a TAB is allowed.
|    */
|   /* #define FEAT_TAG_ANYWHITE */
`----


Best,
Christian
--
Heute ist die Utopie vom Vormittag die Wirklichkeit vom Nachmittag.
                -- Truman Capote

--
--
You received this message from the "vim_use" 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: enabling tag_any_white

Tony Mechelynck
On Thu, Jul 13, 2017 at 9:16 PM, Christian Brabandt <[hidden email]> wrote:

>
> On Do, 13 Jul 2017, Robert wrote:
>
>> I am trying to help someone that posted in the /r/vim Reddit forum. They are trying to get "tag_any_white" compiled in.
>>
>> He has tried the following:
>>
>> configure:15432: WARNING: unrecognized options: --with-tag_any_white
>> configure:15432: WARNING: unrecognized options: --enable-tag_any_white
>>
>> Neither worked...
>
> I already wondered why the OP at reddit wanted to enable all those
> features, even if they do not make sense like ebcdic. It seems one can
> only enable tag_any_white by editing feature.h. Is there any tag program, that
> needs that?
>
> ,----[ feature.h ]
> |   /*
> |    * +tag_any_white       Allow any white space to separate the fields in a tags
> |    *                      file.  When not defined, only a TAB is allowed.
> |    */
> |   /* #define FEAT_TAG_ANYWHITE */
> `----
>
>
> Best,
> Christian
> --
> Heute ist die Utopie vom Vormittag die Wirklichkeit vom Nachmittag.
>                 -- Truman Capote
>

Ebcdic should indeed only be enabled by configure, if it finds out
that you are on an ebcdic machine.

There are indeed some features which AFAIK can only be enabled or
disabled by editing feature.h. That's how I'm running with +xterm_save
but -tag_old_static. If you (Robert) really want +tag_any_white you
can uncomment a line somewhere after line 350 of feature.h, but as
Christian implied, the tags files generated by Vim's :helptags
command, or (IIUC) by the Exuberant Ctags program, don't need that
feature.

Beware that if you do this you will have what Mercurial calls two
unnamed parallel changeset chains (unnamed branches?) within the
default branch, which you will have to merge (e.g. by using hg fetch
instead of hg pull -u) every time you get new patches from Bram's
repository. I'm not sure how it works if you use a git clone.

Best regads,
Tony.

--
--
You received this message from the "vim_use" 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: enabling tag_any_white

robert h-2
On Thursday, July 13, 2017 at 3:45:22 PM UTC-4, Tony Mechelynck wrote:

> On Thu, Jul 13, 2017 at 9:16 PM, Christian Brabandt <[hidden email]> wrote:
> >
> > On Do, 13 Jul 2017, Robert wrote:
> >
> >> I am trying to help someone that posted in the /r/vim Reddit forum. They are trying to get "tag_any_white" compiled in.
> >>
> >> He has tried the following:
> >>
> >> configure:15432: WARNING: unrecognized options: --with-tag_any_white
> >> configure:15432: WARNING: unrecognized options: --enable-tag_any_white
> >>
> >> Neither worked...
> >
> > I already wondered why the OP at reddit wanted to enable all those
> > features, even if they do not make sense like ebcdic. It seems one can
> > only enable tag_any_white by editing feature.h. Is there any tag program, that
> > needs that?
> >
> > ,----[ feature.h ]
> > |   /*
> > |    * +tag_any_white       Allow any white space to separate the fields in a tags
> > |    *                      file.  When not defined, only a TAB is allowed.
> > |    */
> > |   /* #define FEAT_TAG_ANYWHITE */
> > `----
> >
> >
> > Best,
> > Christian
> > --
> > Heute ist die Utopie vom Vormittag die Wirklichkeit vom Nachmittag.
> >                 -- Truman Capote
> >
>
> Ebcdic should indeed only be enabled by configure, if it finds out
> that you are on an ebcdic machine.
>
> There are indeed some features which AFAIK can only be enabled or
> disabled by editing feature.h. That's how I'm running with +xterm_save
> but -tag_old_static. If you (Robert) really want +tag_any_white you
> can uncomment a line somewhere after line 350 of feature.h, but as
> Christian implied, the tags files generated by Vim's :helptags
> command, or (IIUC) by the Exuberant Ctags program, don't need that
> feature.
>
> Beware that if you do this you will have what Mercurial calls two
> unnamed parallel changeset chains (unnamed branches?) within the
> default branch, which you will have to merge (e.g. by using hg fetch
> instead of hg pull -u) every time you get new patches from Bram's
> repository. I'm not sure how it works if you use a git clone.
>
> Best regads,
> Tony.
Thanks Tony. It wasn't for me I as asking but trying to find an answer for another person (See Christians post). I appreciate both yours and Christians time in answering.

Bob

--
--
You received this message from the "vim_use" 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 because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...