Re: file subset of file updated

On 2019-07-31 12:15, Bee wrote:
> Does vim have the ability to reference a file made of files?
>
> file A is a subset of file B
> file A = text
> file B = file A plus more text
>
> When file A is updated opening file B shows the changes

Not out of the box AFAIK.

It would help to know the type of inclusion: are these C-style
#include files? or are they LaTeX with \input{filename} style
includes? And what tooling are you using to generate the resulting
file you want to view?

My first inclination would be to lean on make(1) to generate the
output file based on the input files (updating based on their
changes), then create an autocmd (`:help autocmd` and `:h
BufWritePost`) that runs :make when you save and optionally loads the
results into a preview window.

-tim


--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190731142857.60bfe8c2%40bigbox.christie.dr.

file subset of file updated

Does vim have the ability to reference a file made of files?

file A is a subset of file B
file A = text
file B = file A plus more text

When file A is updated opening file B shows the changes

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/8411df1e-78ac-473f-9198-41a6ab76b802%40googlegroups.com.

Re: Vim plugin with Python3

https://github.com/Yggdroot/LeaderF

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/98526ea4-9b7a-481c-8b6e-a29b2c3b3474%40googlegroups.com.

Re: awkembed.vim

Le vendredi 26 juillet 2019 16:18:13 UTC-3, Christian Brabandt a écrit :
> On Fr, 26 Jul 2019, 'J S' via vim_use wrote:
>
> > I think it should be pretty clear by now that if I thought I could do this myself, I'd have already done so - and would not have posted to this list at all.
> >
> > IOW, if I have to sweat blood to get this done, it's just not worth it.
> >
> > I was hoping that either:
> >
> > 1) It had already been done by someone and the code could be made available.
> > or
> > 2) There exists someone for whom this is a trivial task, and that person could just do it.
> >
> > Note well, re #2: I am not asking anyone to do any large amount of work. I'm just assuming there is someone out there for whom this task would be trivial.
>
> I haven't had a look at the details, but try Ingos Plugin SyntaxRange
> https://github.com/inkarkat/vim-SyntaxRange, I believe it tries to use
> the code mentioned in the help and make it easier available for users
>
> Best
> Christian
> --
> Das Chaos sei willkommen, denn die Ordnung hat versagt.
> -- Karl Kraus

Have a look at how /usr/share/vim/syntax/markdown.vim handles the languages listed in g:markdown_fenced_languages.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1d1e442e-4566-4a1c-b729-2012d25e7aad%40googlegroups.com.

Re: awkembed.vim

On Fr, 26 Jul 2019, 'J S' via vim_use wrote:

> I think it should be pretty clear by now that if I thought I could do this myself, I'd have already done so - and would not have posted to this list at all.
>
> IOW, if I have to sweat blood to get this done, it's just not worth it.
>
> I was hoping that either:
>
> 1) It had already been done by someone and the code could be made available.
> or
> 2) There exists someone for whom this is a trivial task, and that person could just do it.
>
> Note well, re #2: I am not asking anyone to do any large amount of work. I'm just assuming there is someone out there for whom this task would be trivial.

I haven't had a look at the details, but try Ingos Plugin SyntaxRange
https://github.com/inkarkat/vim-SyntaxRange, I believe it tries to use
the code mentioned in the help and make it easier available for users

Best
Christian
--
Das Chaos sei willkommen, denn die Ordnung hat versagt.
-- Karl Kraus

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190726191759.GE32566%40256bit.org.

awkembed.vim

I think it should be pretty clear by now that if I thought I could do this myself, I'd have already done so - and would not have posted to this list at all.

IOW, if I have to sweat blood to get this done, it's just not worth it.

I was hoping that either:

1) It had already been done by someone and the code could be made available.
or
2) There exists someone for whom this is a trivial task, and that person could just do it.

Note well, re #2: I am not asking anyone to do any large amount of work. I'm just assuming there is someone out there for whom this task would be trivial.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1890351613.3078671.1564158114830%40mail.yahoo.com.

Re: awkembed.vim

On Fr, 26 Jul 2019, 'J S' via vim_use wrote:

> I get that people read quickly, and also that English is not everyone's first language (a lethal combination, that), but the fact is that in the OP, every word was very carefully chosen, to impart all needed information. Unfortunate, that I need to re-state that which was clearly stated originally.
>
> That all said, the specific problem to which I seek a specific solution is this:
>
> 1) I write Expect scripts with embedded AWK script.
> 2) I would like the embedded AWK code to be highlighted as AWK code.
>
> Further comments:
>
> 1) In theory, it should be possible to do this sort of thing with any combination of languages. That is, any enclosing language and any embedded language. Again, to clarify, in my specific case, the enclosing language is Expect and the embedded language is AWK.
>
> 2) As far as I can tell, the only specific combination that has been implemented (at least in publicly available VIM script code) is the combination of embedding AWK inside of shell.
>
> As stated, I want to highlight embedded AWK inside of Expect.

Well, the general appraoch is explained at :h sh-embed However it was
never clear from your message, that you already know about it and that
you have tried it.

So did you apply the method mentioned there to try to solve your
problem? If so, what exact problem are you facing?

Best,
Christian
--
Manche Frauen tun für ihr Äußeres Dinge, für die ein Gebrauchtwagenhändler
ins Gefängnis käme.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190726145249.GC32566%40256bit.org.

awkembed.vim

I get that people read quickly, and also that English is not everyone's first language (a lethal combination, that), but the fact is that in the OP, every word was very carefully chosen, to impart all needed information. Unfortunate, that I need to re-state that which was clearly stated originally.

That all said, the specific problem to which I seek a specific solution is this:

1) I write Expect scripts with embedded AWK script.
2) I would like the embedded AWK code to be highlighted as AWK code.

Further comments:

1) In theory, it should be possible to do this sort of thing with any combination of languages. That is, any enclosing language and any embedded language. Again, to clarify, in my specific case, the enclosing language is Expect and the embedded language is AWK.

2) As far as I can tell, the only specific combination that has been implemented (at least in publicly available VIM script code) is the combination of embedding AWK inside of shell.

As stated, I want to highlight embedded AWK inside of Expect.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1454053570.1450734.1564149066909%40mail.yahoo.com.

Re: job_start the make command

Le lundi 25 septembre 2017 06:22:14 UTC-3, Vincent Stone a écrit :
> Asynchrun is too heavy to be included in the vim just for make and grep. I prefer the vim-make-background plugin. Is there any plan to include it?
>
> --Vincent Stone

In defense of AsyncRun, it worked unfailingly for the last two years. The 40 kilobytes of source code are also due to (useful) options listed in https://github.com/skywind3000/asyncrun.vim/wiki/Options

Vim-dispatch https://github.com/tpope/vim-dispatch is backwards comaptible, but bigger, and the job-feature was implemented last month: https://github.com/tpope/vim-dispatch/commit/597b338f3579ca6929c47465397974d366f4eccc

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/7269019f-465d-43ec-9826-a7ba9225891d%40googlegroups.com.

Re: Recent showcmd change?

On Tue, Jul 02, 2019 at 05:07:19PM +0100, Paul wrote:
>I noticed that since around 8.1.1561 (or was it 1651?), showcmd would start showing one-off cursor movements (hjklwbe, etc.) in normal mode, very briefly. It's barely noticeable in gvim, more noticeable when sending the keystrokes over a slow connection (eg., remote SSH) — annoying, then, in fact. Yes, I know it is bad form to hold down those keys, but still, I didn't notice Vim doing that before recently.

Any idea about this? It's still happening as of patch 1746. On a remote, slow connection (for visibility), where file is something that Vim has a syntax definition for (again, for visibility), and large enough to scroll up and down for a few moments:

vim -Nu NONE -c 'set showcmd' -c 'syntax on' file

Hold j or k down long enough that Vim has to scroll the file (not just move the cursor). For me, "j"/"k" flickers in the showcmd area.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190725113858.GA18983%40rainslide.net.

Re: New compiler/perl.vim

Christian J. Robinson wrote:

> Small change to escape the filename.

I'll include it, thanks.

--
The problem with political jokes is that they get elected.

/// Bram Moolenaar -- Bram@Moolenaar.net -- 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_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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201907232015.x6NKFsoC015479%40masaka.moolenaar.net.

New compiler/perl.vim

Small change to escape the filename.

--
Christian J. Robinson <heptite@gmail.com> -- https://christianrobinson.name/
"You can only be young once. But you can always be immature."
-- Dave Barry

In the virtual console, VIM doesn't work with GPM on most of my Ubuntu PC.

I have several Ubuntu boxes with different Ubuntu versions. When I use VIM in virtual consoles and set mouse=a, GPM mouse works only on one PC. On all other GPM cursor is frozen. I compared all the related settings on all machines, but still cannot understand why VIM+GPM works on one box, and doesn't work on all others.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/e5b825a0-a660-4dcf-8b53-6fb6b646938a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

Thank you! It really helps!

Christian Brabandt <cblists@256bit.org> 于2019年7月16日周二 上午1:25写道：

On Di, 16 Jul 2019, 吴祖姜 wrote:

> No, not a tmap. I know tmap. 
>
> What I want is, to invoke vim command from a terminal with shell commands,
> without typing <c-w> prefix or entering normal mode. 
>
> Like providing a shell function 'send-keys-to-host-vim' (and I want its name be
> ':'), then run
>
> $ send-keys-to-host-vim vsp my.file<enter>
>
> It equals to <c-w>:vsp my.file<enter>
>
> Sorry for my poor English, hope it is explained clearly this time. 

Have a look at `:h terminal-api`. I have a plugin that does something
similar: https://github.com/chrisbra/vpager you can also have a look
there.

Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
  Clara Schnaps

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190715172540.GO31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAPHDgoOaXmZqiBpAqv6T6Rk4e_b1t%3D31-U7yxTV-LOszhXBs_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

On Di, 16 Jul 2019, 吴祖姜 wrote:

> No, not a tmap. I know tmap. 
>
> What I want is, to invoke vim command from a terminal with shell commands,
> without typing <c-w> prefix or entering normal mode. 
>
> Like providing a shell function 'send-keys-to-host-vim' (and I want its name be
> ':'), then run
>
> $ send-keys-to-host-vim vsp my.file<enter>
>
> It equals to <c-w>:vsp my.file<enter>
>
> Sorry for my poor English, hope it is explained clearly this time. 

Have a look at `:h terminal-api`. I have a plugin that does something
similar: https://github.com/chrisbra/vpager you can also have a look
there.

Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
Clara Schnaps

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190715172540.GO31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

Salman Halim,

Your mapping idea seems good. I will try it. Thanks.

吴祖姜 <billbill290@gmail.com>于2019年7月16日 周二上午1:19写道：

No, not a tmap. I know tmap. 

What I want is, to invoke vim command from a terminal with shell commands, without typing <c-w> prefix or entering normal mode. 

Like providing a shell function 'send-keys-to-host-vim' (and I want its name be ':'), then run

$ send-keys-to-host-vim vsp my.file<enter>

It equals to <c-w>:vsp my.file<enter>

Sorry for my poor English, hope it is explained clearly this time. 

Salman Halim <salmanhalim@gmail.com>于2019年7月14日 周日下午10:46写道：

--

Salman

On Sun, Jul 14, 2019, 09:18 Christian Brabandt <cblists@256bit.org> wrote:

On Sa, 13 Jul 2019, 陈世用 wrote:

> Like in a terminal buffer, typing:
>
> ```
> $ :vsp demo.file
> ```
>
> `:` is the custom shell function's name.
>
> It's expand to `<c-w>:vsp demo.file` or something.

I think it is unclear, what you are asking exactly. Please clarify.

Best,
Christian

Sound like you want a terminal mapping. I think :help tmap may give you what you want, but if you remap the colon, you'll have trouble if you need to use it in an actual command. You could either map the double colon (::) to do this or to insert an actual single colon:

tmap : <c-w>:

tnoremap :: :

Or, depending on which you prefer, reverse the two mappings. 

Salman

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcCesOnUPGDGUsjjRAiQxfnJ7E_JskEzLiXcQrSJyF7DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAPHDgoM1roeVRjxe6S9H2Shnm13jVnp-QqHPZBy-xHUwLEaTJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

No, not a tmap. I know tmap. 

What I want is, to invoke vim command from a terminal with shell commands, without typing <c-w> prefix or entering normal mode. 

Like providing a shell function 'send-keys-to-host-vim' (and I want its name be ':'), then run

$ send-keys-to-host-vim vsp my.file<enter>

It equals to <c-w>:vsp my.file<enter>

Sorry for my poor English, hope it is explained clearly this time. 

Salman Halim <salmanhalim@gmail.com>于2019年7月14日 周日下午10:46写道：

--

Salman

On Sun, Jul 14, 2019, 09:18 Christian Brabandt <cblists@256bit.org> wrote:

On Sa, 13 Jul 2019, 陈世用 wrote:

> Like in a terminal buffer, typing:
>
> ```
> $ :vsp demo.file
> ```
>
> `:` is the custom shell function's name.
>
> It's expand to `<c-w>:vsp demo.file` or something.

I think it is unclear, what you are asking exactly. Please clarify.

Best,
Christian

Sound like you want a terminal mapping. I think :help tmap may give you what you want, but if you remap the colon, you'll have trouble if you need to use it in an actual command. You could either map the double colon (::) to do this or to insert an actual single colon:

tmap : <c-w>:

tnoremap :: :

Or, depending on which you prefer, reverse the two mappings. 

Salman

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcCesOnUPGDGUsjjRAiQxfnJ7E_JskEzLiXcQrSJyF7DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAPHDgoOzhq0s77XMV_c0Bzj9Y_OnzsEXa9jgM%2BvVGh6DBzK5MA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: awkembed.vim

On So, 14 Jul 2019, 'J S' via vim_use wrote:

> > Have a look at :h sh-embed for the general principle.
>
> I'm assuming that you either didn't read the OP or read it very
> quickly, since it (the OP) makes it very clear that I had already done
> that.

You are making it unnecessary hard to follow your messages, since
apparently you break the threads on answering.

I somehow missed, that you already tried that method, so what problem
are you trying to solve? (you cut the quotes quite strictly, so cannot
follow the thread)

Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
Jack Ett

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714144733.GG31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

--

Salman

On Sun, Jul 14, 2019, 09:18 Christian Brabandt <cblists@256bit.org> wrote:

On Sa, 13 Jul 2019, 陈世用 wrote:

> Like in a terminal buffer, typing:
>
> ```
> $ :vsp demo.file
> ```
>
> `:` is the custom shell function's name.
>
> It's expand to `<c-w>:vsp demo.file` or something.

I think it is unclear, what you are asking exactly. Please clarify.

Best,
Christian

Sound like you want a terminal mapping. I think :help tmap may give you what you want, but if you remap the colon, you'll have trouble if you need to use it in an actual command. You could either map the double colon (::) to do this or to insert an actual single colon:

tmap : <c-w>:

tnoremap :: :

Or, depending on which you prefer, reverse the two mappings. 

Salman

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcCesOnUPGDGUsjjRAiQxfnJ7E_JskEzLiXcQrSJyF7DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: awkembed.vim

> Perl is off-topic in this thread.
>
> I do not want any discussion of Perl in this thread.
>

OK, just trying to offer a solution.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/88a7c82196970f41ff3b8cbfe22b434d.squirrel%40webmail.vybenetworks.com.
For more options, visit https://groups.google.com/d/optout.

awkembed.vim

> Have a look at :h sh-embed for the general principle.

I'm assuming that you either didn't read the OP or read it very quickly, since it (the OP) makes it very clear that I had already done that.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1184455045.1646401.1563113650077%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim crashes in windows when trying to execute python 3 command

On So, 14 Jul 2019, skeept wrote:

> I confirmed that is the case. When I try using another python distribution it doesn't crash.
> I hope at some point vim or conda can fix the issue, for now my best choice is to find time to compile vim without python.

It is probably an implementation detail that differs and that makes Vim
crash.

If someone who knows the exact details of python embedding and Vim can
pinpoint the problem, we can actually fix it, but so far nobody has done
it :(

Best,
Christian
--
Letzte Worte eines Postboten:
"Du bist aber ein lieber Hund."

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714133903.GF31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: vim crashes in windows when trying to execute python 3 command

> Although nowhere stated explicitly, I believe Vims python implementation
> is not exactly compatible with conda. Please try with a normal python
> distribution.
>
>
> Best,
> Christian
> --
> Man soll die lieben, über die man befielt, aber man soll es ihnen
> nicht sagen.
> -- Antoine de Saint-Exypery



Thank you Christian,

I confirmed that is the case. When I try using another python distribution it doesn't crash.
I hope at some point vim or conda can fix the issue, for now my best choice is to find time to compile vim without python.

Best,
Jorge

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/8621d956-7c72-45ee-8707-a52173848210%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: execute an alias with vim

On Mi, 10 Jul 2019, Mathieu Roux wrote:

> Hello,
>
> I use many text files to write many things on my laptop, and i use
> aliases to access them.
> For exemple, suppose that i have the alias "foo" to access ~/bar with
> vim.
>
> alias foo='vim ~/bar'
>
> So it works when i write "foo" in my terminal.
>
> But I also want to use this alias in vim.
> When i am in vim, i do "C-w n" to open one new window.
> And then i try :!foo
>
> But it writes:
>
> "/bin/bash: foo: command not found
>
> le shell a retourné 127"

I believe, if you set the shellcmdflag to -ic Vim will run an
interactive shell (which in turn should read your alias file).

Mit freundlichen Grüßen
Christian
--
Wir sind doch alle nur Schachfiguren, sagte der König zum Bauern.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714132804.GE31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: Code folding not working for restructuredText (.rst) after 8.1-153

On Mo, 01 Jul 2019, Steve Canny wrote:

> After a recent upgrade to 8.1-154 and 8.1-156, code-folding is not working for restructuredText (rst) file-type. Reverting to version 8.1-153 restores that functionality.
>
> :e foobar.rst
>
> -> file opens with text fully expanded
>
> zc
>
> -> E490: No fold found
>
> set fdm? -> expr
> set fde? -> RstFold#GetRstFold
>
> This behavior was observed on two of my three machines, running 8.1-154, 8.1-156, and 8.1-153. Reverting the second one to v153 restored RST code-folding.
>
> Let me know if you need more and I'll be happy to provide :)

The Vim runtime files for rst have been updated in between. Try the
latest version from https://github.com/marshallward/vim-restructuredtext

If it still doesn't work, open an issue there with the upstream author
to have it fixed. Thanks.


Best,
Christian
--
Freude bereiten heißt: Die Banane essen und die Schale einem Anderen hinlegen.
-- Helmut Kohl
(Marc-Uwe Kling: Falsch zugeordnete Zitate; eigentlich Dashiell Hammett)

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714132520.GD31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: awkembed.vim

On Sa, 13 Jul 2019, 'J S' via vim_use wrote:

> (On the subject of syntax highlighting languages embedded in other languages)
>
> I frequently write (bash) shell scripts with embedded AWK scripts, and I've found the awkembed.vim script quite useful. I have it installed at:
>
> ~/.vim/after/syntax/sh/awkembed.vim
>
> And it works quite well. Now, I would like to extend the idea beyond the set of "shell" and "awk".
>
> There are, obviously, two variables here: The enclosing language and the embedded language. As far as I can tell (based on a little Googoling) this has only been done for the one specific combination: shell & awk. Note: :help sh-embed
>
> Specifically, I have an Expect script with embedded AWK. How hard is it going to be to get this to work?
>
> I took a look at the awkembed.vim script - it's mostly greek to me, although I was able to modify it slightly because my awk has a different name than the one assumed by the script.
>
> It'd be nice if someone could tell me either a quick way to make a script to do what I want - or to tell me it can't be done...

Have a look at :h sh-embed for the general principle.

Best,
Christian
--
Ist Windows 98 ein Spiel oder ein Betriebssystem?

Nein, ich finde ein Spiel sollte schon eine Lösung haben.
Ich stecke im 97. Level.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714132100.GC31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: vim crashes in windows when trying to execute python 3 command

On Sa, 13 Jul 2019, skeept wrote:

> I had to change computers recently. In my previous computer I was compiling vim with python to avoid this issue also, but I had no time to compile it yet
> so I downloaded a 64 bit build of vim for windows:
>
> MS-Windows 64-bit console version
> Included patches: 1-1649
> Compiled by appveyor@APPVYR-WIN
>
>
> I also downloaded conda python distribution and I have the folder where python.exe is located in my PATH variable.
>
> Without a vimrc or vimfiles folder if I do the following:
>
> :py3 import os
>
> then I get the following error message and vim crashes:
>
>
> Fatal Python error: initfsencoding: unable to load the file system codec
> ModuleNotFoundError: No module named 'encodings'
>
> Current thread 0x00007ed4 (most recent call first):
>
>
> I understand there might be something I can put in my vimrc to avoid this, but i don't think vim should crash this way.

Although nowhere stated explicitly, I believe Vims python implementation
is not exactly compatible with conda. Please try with a normal python
distribution.


Best,
Christian
--
Man soll die lieben, über die man befielt, aber man soll es ihnen
nicht sagen.
-- Antoine de Saint-Exypery

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714132001.GB31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Re: How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

On Sa, 13 Jul 2019, 陈世用 wrote:

> Like in a terminal buffer, typing:
>
> ```
> $ :vsp demo.file
> ```
>
> `:` is the custom shell function's name.
>
> It's expand to `<c-w>:vsp demo.file` or something.

I think it is unclear, what you are asking exactly. Please clarify.

Best,
Christian
--
Munterbleiben, heute ist Weltuntergang!

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190714131855.GA31610%40256bit.org.
For more options, visit https://groups.google.com/d/optout.

Jumplist oddity

Given two files A, and B, with the following jump lists:

A:
3: Text A2
2: Text A1
1: <file_B>
>

B:
3: Text in B2
2: Text in B1
1: <file_A>
>

Starting from B, how would I ever be able to reach position "Text in B1" using <C-o>?

And - as this is a rhetorical question - how could we improve this (ping-pong) behavior that - under the specified circumstances - renders the jump lists useless?

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/813fac7a-b822-4944-b065-128add0bdf76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How can I define a shell function (named `:` would be neat) from a terminal buffe and send commands to current vim clientr?

Like in a terminal buffer, typing:

```
$ :vsp demo.file
```

`:` is the custom shell function's name.

It's expand to `<c-w>:vsp demo.file` or something.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/4cefdbda-f8ff-404f-ab4b-7052b350d4c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

vim crashes in windows when trying to execute python 3 command

I had to change computers recently. In my previous computer I was compiling vim with python to avoid this issue also, but I had no time to compile it yet
so I downloaded a 64 bit build of vim for windows:

MS-Windows 64-bit console version
Included patches: 1-1649
Compiled by appveyor@APPVYR-WIN


I also downloaded conda python distribution and I have the folder where python.exe is located in my PATH variable.

Without a vimrc or vimfiles folder if I do the following:

:py3 import os

then I get the following error message and vim crashes:


Fatal Python error: initfsencoding: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007ed4 (most recent call first):


I understand there might be something I can put in my vimrc to avoid this, but i don't think vim should crash this way.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/54d05ecb-5c4c-4c56-a003-c13ce62fd631%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

awkembed.vim

Perl is off-topic in this thread.

Normally, I wouldn't say anything, but I've found that, on boards like this, the first response sets the tone for the thread. People end up reacting more to the first response than to the original post. I do not want any discussion of Perl in this thread.

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/211025713.1524557.1563059502500%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vin crashes with "Caught deadly signal ABRT" unless launched without .vimrc

On Fri, 12 Jul 2019 at 14:37, Bram Moolenaar <Bram@moolenaar.net> wrote:

> It looks like you run into the false-positive fortify check.
> Although the build log mentiones -D_FORTIFY_SOURCE=1 it behaves like a
> higher fortify level was used.

Thanks for your input Bram. I wanted to make a couple of checks before
getting back you.

In pkgsrc, as default we have:

PKGSRC_USE_FORTIFY?= strong

As explained here:
http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/mk/defaults/mk.conf

PKGSRC_USE_FORTIFY?= strong
# Turns on substitute wrappers for commonly used functions that do not bounds
# checking regularly, but could in some cases. This is effectively in use only
# when both enabled and supported.
# Possible values:
# no: Do not pass any flags for FORTIFY
# weak: Pass -D_FORTIFY_SOURCE=1
# strong: Pass -D_FORTIFY_SOURCE=2
# Default: strong


I have rebuilt with PKGSRC_USE_FORTIFY?=weak

and this seems to produce an installation that doesn't crash.

I've passed this information to pkgsrc-users and the editors/vim
package maintainer.

Thanks for you assistance.




--
Ottavio Caruso

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAEJNuHwiYMzGNxGMAnPzed8jQY1tKOUkE4T39exLcdpiCJ55EA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: awkembed.vim

> I frequently write (bash) shell scripts with embedded AWK scripts,

It sounds as though Perl might be good fit for whatever you are doing.
(Perl evolved because shell, sed and awk combinations were becoming
cumbersome.)

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/19b6f2c832eeee701a0b5a9838ebb08f.squirrel%40webmail.vybenetworks.com.
For more options, visit https://groups.google.com/d/optout.

awkembed.vim

(On the subject of syntax highlighting languages embedded in other languages)

I frequently write (bash) shell scripts with embedded AWK scripts, and I've found the awkembed.vim script quite useful. I have it installed at:

~/.vim/after/syntax/sh/awkembed.vim

And it works quite well. Now, I would like to extend the idea beyond the set of "shell" and "awk".

There are, obviously, two variables here: The enclosing language and the embedded language. As far as I can tell (based on a little Googoling) this has only been done for the one specific combination: shell & awk. Note: :help sh-embed

Specifically, I have an Expect script with embedded AWK. How hard is it going to be to get this to work?

I took a look at the awkembed.vim script - it's mostly greek to me, although I was able to modify it slightly because my awk has a different name than the one assumed by the script.

It'd be nice if someone could tell me either a quick way to make a script to do what I want - or to tell me it can't be done...

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1632295224.1316600.1563020677437%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vin crashes with "Caught deadly signal ABRT" unless launched without .vimrc

Ottavio Caruso wrote:

> I'd like to have the opinion of this list before reporting this issue
> as a bug on github.
>
> I have compiled and installed Vim using pkgsrc on my Linux Mint Debian Edition.
> I've already reported the issue on the pkgsrc-users list and it has
> been suggested that I report the issue upstream.
>
> The build has run fine, but, and this seems to be a common failure,
> when Vim is launched, it crashes like this:
>
> $vim
> Vim: Caught deadly signal
> Vim: Finished.
>
> Full vim --version here:
> http://paste.debian.net/hidden/ded7a246/
>
> Full build log here:
> http://paste.debian.net/hidden/5ebf5480/
>
> I've made a gdb capture here:
> http://paste.debian.net/hidden/4ca4bed2/
>
> Temporary workarounds:
>
> 1) `vim -u NONE` # works, but without modules
>
> 2) recompiling with the option: "CFLAGS=-g INSTALL_UNSTRIPPED=yes" #
> produces a binary without crashes.
>
> Any input will be appreciated.

It looks like you run into the false-positive fortify check.
Although the build log mentiones -D_FORTIFY_SOURCE=1 it behaves like a
higher fortify level was used.

--
FATHER: You only killed the bride's father - that's all -
LAUNCELOT: Oh dear, I didn't really mean to...
FATHER: Didn't mean to? You put your sword right through his head!
LAUNCELOT: Gosh - Is he all right?
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/// Bram Moolenaar -- Bram@Moolenaar.net -- 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_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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201907121337.x6CDbUqT011874%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.

Re: Vim crashes with "Caught deadly signal ABRT" unless launched without .vimrc

GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from vim...done.
(gdb) run
Starting program: /opt/pkg/bin/vim
Vim: Warning: Output is not to a terminal
[?1000h[?1049h[?1h=
Program received signal SIGABRT, Aborted.
0x00007ffff7308fff in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0 0x00007ffff7308fff in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1 0x00007ffff730a42a in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2 0x00007ffff7346c00 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#3 0x00007ffff73cf1f7 in __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#4 0x00007ffff73cd330 in __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#5 0x000055555571dee3 in strcpy (__src=0x555555763046 "0", __dest=0x555555c3e951 "") at /usr/include/x86_64-linux-gnu/bits/string3.h:110
No locals.
#6 add_nr_var (nr=<optimized out>, name=0x555555763046 "0", v=<optimized out>, dp=0x555555c3ece8) at userfunc.c:618
No locals.
#7 call_user_func (selfdict=<optimized out>, lastline=1, firstline=1, rettv=0x7fffffffd570, argvars=<optimized out>, argcount=1, fp=0x555555c28b50) at userfunc.c:858
save_sourcing_name = <optimized out>
fixvar_idx = <optimized out>
i = <optimized out>
ai = <optimized out>
len = <optimized out>
wait_start = {tv_sec = 0, tv_usec = 140737340837732}
fc = 0x555555c3e930
save_did_emsg = <optimized out>
default_arg_err = 0
v = <optimized out>
islambda = 0
numbuf = "\220\323\377\377\377\177\000\000\220\323\377\377\377\177\000\000\001\000\000\000\000\000\000\000\224\025[UUU\000\000\240\320\377\377\377\177\000\000\022", '\000' <repeats 15 times>, "P\302\303U\000\000\000\000\234"
call_start = {tv_sec = 140737333868241, tv_usec = 40}
depth = 1
save_sourcing_lnum = <optimized out>
save_current_sctx = <optimized out>
using_sandbox = 0
name = <optimized out>
started_profiling = 0
depth = 1
#8 call_func (funcname=funcname@entry=0x555555c47e60 "\200\375R13_LocalBrowse", len=len@entry=-1, rettv=rettv@entry=0x7fffffffd570, argcount_in=argcount_in@entry=1,
argvars_in=argvars_in@entry=0x7fffffffd390, argv_func=argv_func@entry=0x0, firstline=1, lastline=1, doesrange=0x7fffffffd55c, evaluate=<optimized out>,
partial=0x0, selfdict_in=0x0) at userfunc.c:1621
did_save_redo = 1
save_redo = {sr_redobuff = {bh_first = {b_next = 0x0, b_str = ""}, bh_curr = 0x0, bh_index = 0, bh_space = 0}, sr_old_redobuff = {bh_first = {b_next = 0x0,
b_str = ""}, bh_curr = 0x0, bh_index = 0, bh_space = 0}}
rfname = <optimized out>
ret = 0
error = 0
i = <optimized out>
fp = 0x555555c28b50
fname_buf = '\000' <repeats 24 times>, "\210\323\377\377\377\177\000\000\220\323\377\377\377\177\000\000\001"
tofree = 0x0
fname = <optimized out>
name = 0x555555c47e80 "\200\375R13_LocalBrowse"
argcount = 1
argvars = <optimized out>
selfdict = <optimized out>
argv = {{v_type = 4294955056, v_lock = -1 '\377', vval = {v_number = 93824999521852, v_float = 4.6355708984818457e-310,
v_string = 0x555555c47e3c "d(\"<amatch>\"))", v_list = 0x555555c47e3c, v_dict = 0x555555c47e3c, v_partial = 0x555555c47e3c, v_job = 0x555555c47e3c,
v_channel = 0x555555c47e3c, v_blob = 0x555555c47e3c}}, {v_type = 1436489232, v_lock = 85 'U', vval = {v_number = 35, v_float = 1.7292297604443629e-322,
v_string = 0x23 <error: Cannot access memory at address 0x23>, v_list = 0x23, v_dict = 0x23, v_partial = 0x23, v_job = 0x23, v_channel = 0x23,
v_blob = 0x23}}, {v_type = 1436489232, v_lock = 85 'U', vval = {v_number = 93823560581122, v_float = 4.6354998053637362e-310,
v_string = 0x555500000002 <error: Cannot access memory at address 0x555500000002>, v_list = 0x555500000002, v_dict = 0x555500000002,
v_partial = 0x555500000002, v_job = 0x555500000002, v_channel = 0x555500000002, v_blob = 0x555500000002}}, {v_type = 20, v_lock = 0 '\000', vval = {
v_number = 64, v_float = 3.1620201333839779e-322, v_string = 0x40 <error: Cannot access memory at address 0x40>, v_list = 0x40, v_dict = 0x40,
v_partial = 0x40, v_job = 0x40, v_channel = 0x40, v_blob = 0x40}}, {v_type = VAR_UNKNOWN, v_lock = 0 '\000', vval = {v_number = 206158430210,
v_float = 1.018557979673212e-312, v_string = 0x3000000002 <error: Cannot access memory at address 0x3000000002>, v_list = 0x3000000002,
v_dict = 0x3000000002, v_partial = 0x3000000002, v_job = 0x3000000002, v_channel = 0x3000000002, v_blob = 0x3000000002}}, {v_type = VAR_UNKNOWN,
v_lock = 0 '\000', vval = {v_number = 93824992604365, v_float = 4.6355705567125774e-310, v_string = 0x5555555af0cd <handle_subscript+285> "H\201Ĉ",
v_list = 0x5555555af0cd <handle_subscript+285>, v_dict = 0x5555555af0cd <handle_subscript+285>, v_partial = 0x5555555af0cd <handle_subscript+285>,
v_job = 0x5555555af0cd <handle_subscript+285>, v_channel = 0x5555555af0cd <handle_subscript+285>, v_blob = 0x5555555af0cd <handle_subscript+285>}}, {
v_type = 4294954856, v_lock = -1 '\377', vval = {v_number = 4294967296, v_float = 2.1219957909652723e-314,
v_string = 0x100000000 <error: Cannot access memory at address 0x100000000>, v_list = 0x100000000, v_dict = 0x100000000, v_partial = 0x100000000,
v_job = 0x100000000, v_channel = 0x100000000, v_blob = 0x100000000}}, {v_type = 4294954880, v_lock = -1 '\377', vval = {v_number = 140737488342928,
v_float = 6.9533558072223629e-310, v_string = 0x7fffffffcf90 "7~\304UUU", v_list = 0x7fffffffcf90, v_dict = 0x7fffffffcf90, v_partial = 0x7fffffffcf90,
v_job = 0x7fffffffcf90, v_channel = 0x7fffffffcf90, v_blob = 0x7fffffffcf90}}, {v_type = 1438940727, v_lock = 85 'U', vval = {
v_number = 140737488342892, v_float = 6.9533558072205843e-310, v_string = 0x7fffffffcf6c "", v_list = 0x7fffffffcf6c, v_dict = 0x7fffffffcf6c,
v_partial = 0x7fffffffcf6c, v_job = 0x7fffffffcf6c, v_channel = 0x7fffffffcf6c, v_blob = 0x7fffffffcf6c}}, {v_type = 20, v_lock = 0 '\000', vval = {
v_number = 1, v_float = 4.9406564584124654e-324, v_string = 0x1 <error: Cannot access memory at address 0x1>, v_list = 0x1, v_dict = 0x1,
v_partial = 0x1, v_job = 0x1, v_channel = 0x1, v_blob = 0x1}}, {v_type = VAR_NUMBER, v_lock = 0 '\000', vval = {v_number = 0, v_float = 0,
v_string = 0x0, v_list = 0x0, v_dict = 0x0, v_partial = 0x0, v_job = 0x0, v_channel = 0x0, v_blob = 0x0}}, {v_type = 1438940727, v_lock = 85 'U',
vval = {v_number = 140737340837732, v_float = 6.9533485194973703e-310,
v_string = 0x7ffff7350f64 <malloc+84> "H\205\300H\211\302\017\204", <incomplete sequence \310>, v_list = 0x7ffff7350f64 <malloc+84>,
v_dict = 0x7ffff7350f64 <malloc+84>, v_partial = 0x7ffff7350f64 <malloc+84>, v_job = 0x7ffff7350f64 <malloc+84>, v_channel = 0x7ffff7350f64 <malloc+84>,
v_blob = 0x7ffff7350f64 <malloc+84>}}, {v_type = 4294955024, v_lock = -1 '\377', vval = {v_number = 140737488343944, v_float = 6.95335580727256e-310,
v_string = 0x7fffffffd388 "J~\304UUU", v_list = 0x7fffffffd388, v_dict = 0x7fffffffd388, v_partial = 0x7fffffffd388, v_job = 0x7fffffffd388,
v_channel = 0x7fffffffd388, v_blob = 0x7fffffffd388}}, {v_type = 1438940727, v_lock = 85 'U', vval = {v_number = 140737488343952,
v_float = 6.9533558072729552e-310, v_string = 0x7fffffffd390 "\002", v_list = 0x7fffffffd390, v_dict = 0x7fffffffd390, v_partial = 0x7fffffffd390,
v_job = 0x7fffffffd390, v_channel = 0x7fffffffd390, v_blob = 0x7fffffffd390}}, {v_type = VAR_NUMBER, v_lock = 0 '\000', vval = {
v_number = 140737488343944, v_float = 6.95335580727256e-310, v_string = 0x7fffffffd388 "J~\304UUU", v_list = 0x7fffffffd388, v_dict = 0x7fffffffd388,
v_partial = 0x7fffffffd388, v_job = 0x7fffffffd388, v_channel = 0x7fffffffd388, v_blob = 0x7fffffffd388}}, {v_type = 1438940727, v_lock = 85 'U',
vval = {v_number = 140737488343952, v_float = 6.9533558072729552e-310, v_string = 0x7fffffffd390 "\002", v_list = 0x7fffffffd390, v_dict = 0x7fffffffd390,
v_partial = 0x7fffffffd390, v_job = 0x7fffffffd390, v_channel = 0x7fffffffd390, v_blob = 0x7fffffffd390}}, {v_type = VAR_NUMBER, v_lock = 0 '\000',
vval = {v_number = 1, v_float = 4.9406564584124654e-324, v_string = 0x1 <error: Cannot access memory at address 0x1>, v_list = 0x1, v_dict = 0x1,
v_partial = 0x1, v_job = 0x1, v_channel = 0x1, v_blob = 0x1}}, {v_type = 1438940727, v_lock = 85 'U', vval = {v_number = 93824992610283,
v_float = 4.6355705570049655e-310, v_string = 0x5555555b07eb <eval7+395> "\203\370\001A\211\306\017\205\326\001", v_list = 0x5555555b07eb <eval7+395>,
v_dict = 0x5555555b07eb <eval7+395>, v_partial = 0x5555555b07eb <eval7+395>, v_job = 0x5555555b07eb <eval7+395>, v_channel = 0x5555555b07eb <eval7+395>,
v_blob = 0x5555555b07eb <eval7+395>}}, {v_type = 1438940800, v_lock = 85 'U', vval = {v_number = 140737336019860, v_float = 6.9533482814628661e-310,
v_string = 0x7ffff6eb8b94 "libc.so.6", v_list = 0x7ffff6eb8b94, v_dict = 0x7ffff6eb8b94, v_partial = 0x7ffff6eb8b94, v_job = 0x7ffff6eb8b94,
v_channel = 0x7ffff6eb8b94, v_blob = 0x7ffff6eb8b94}}, {v_type = VAR_UNKNOWN, v_lock = 0 '\000', vval = {v_number = 140737351915145,
v_float = 6.9533490667942911e-310, v_string = 0x7ffff7de1689 "\205\300uBA\366\207\025\003", v_list = 0x7ffff7de1689, v_dict = 0x7ffff7de1689,
v_partial = 0x7ffff7de1689, v_job = 0x7ffff7de1689, v_channel = 0x7ffff7de1689, v_blob = 0x7ffff7de1689}}, {v_type = 1438892624, v_lock = 2 '\002',
vval = {v_number = 140733193388032, v_float = 6.9531436082559078e-310, v_string = 0x7fff00000000 <error: Cannot access memory at address 0x7fff00000000>,
v_list = 0x7fff00000000, v_dict = 0x7fff00000000, v_partial = 0x7fff00000000, v_job = 0x7fff00000000, v_channel = 0x7fff00000000,
v_blob = 0x7fff00000000}}}
argv_clear = <optimized out>
#9 0x000055555571effb in get_func_tv (name=name@entry=0x555555c47e60 "\200\375R13_LocalBrowse", len=len@entry=-1, rettv=rettv@entry=0x7fffffffd570,
arg=arg@entry=0x7fffffffd560, firstline=1, lastline=1, doesrange=0x7fffffffd55c, evaluate=1, partial=0x0, selfdict=0x0) at userfunc.c:490
i = 0
argp = 0x555555c47e4a ""
ret = 1
argvars = {{v_type = VAR_STRING, v_lock = 0 '\000', vval = {v_number = 0, v_float = 0, v_string = 0x0, v_list = 0x0, v_dict = 0x0, v_partial = 0x0,
v_job = 0x0, v_channel = 0x0, v_blob = 0x0}}, {v_type = 91, v_lock = 110 'n', vval = {v_number = 0, v_float = 0, v_string = 0x0, v_list = 0x0,
v_dict = 0x0, v_partial = 0x0, v_job = 0x0, v_channel = 0x0, v_blob = 0x0}}, {v_type = VAR_UNKNOWN, v_lock = 0 '\000', vval = {v_number = 532575944823,
v_float = 2.6312747813848758e-312, v_string = 0x7c00000077 <error: Cannot access memory at address 0x7c00000077>, v_list = 0x7c00000077,
v_dict = 0x7c00000077, v_partial = 0x7c00000077, v_job = 0x7c00000077, v_channel = 0x7c00000077, v_blob = 0x7c00000077}}, {v_type = VAR_UNKNOWN,
v_lock = 0 '\000', vval = {v_number = 140737344109312, v_float = 6.9533486811348988e-310, v_string = 0x7ffff766fb00 "", v_list = 0x7ffff766fb00,
v_dict = 0x7ffff766fb00, v_partial = 0x7ffff766fb00, v_job = 0x7ffff766fb00, v_channel = 0x7ffff766fb00, v_blob = 0x7ffff766fb00}}, {v_type = 18,
v_lock = 0 '\000', vval = {v_number = 1, v_float = 4.9406564584124654e-324, v_string = 0x1 <error: Cannot access memory at address 0x1>, v_list = 0x1,
v_dict = 0x1, v_partial = 0x1, v_job = 0x1, v_channel = 0x1, v_blob = 0x1}}, {v_type = 1438940715, v_lock = 85 'U', vval = {v_number = 6,
v_float = 2.9643938750474793e-323, v_string = 0x6 <error: Cannot access memory at address 0x6>, v_list = 0x6, v_dict = 0x6, v_partial = 0x6,
v_job = 0x6, v_channel = 0x6, v_blob = 0x6}}, {v_type = 1438940713, v_lock = 85 'U', vval = {v_number = 140737340837732,
v_float = 6.9533485194973703e-310, v_string = 0x7ffff7350f64 <malloc+84> "H\205\300H\211\302\017\204", <incomplete sequence \310>,
v_list = 0x7ffff7350f64 <malloc+84>, v_dict = 0x7ffff7350f64 <malloc+84>, v_partial = 0x7ffff7350f64 <malloc+84>, v_job = 0x7ffff7350f64 <malloc+84>,
v_channel = 0x7ffff7350f64 <malloc+84>, v_blob = 0x7ffff7350f64 <malloc+84>}}, {v_type = 4294956384, v_lock = -1 '\377', vval = {
v_number = 140737488344176, v_float = 6.9533558072840223e-310, v_string = 0x7fffffffd470 "+~\304UUU", v_list = 0x7fffffffd470, v_dict = 0x7fffffffd470,
v_partial = 0x7fffffffd470, v_job = 0x7fffffffd470, v_channel = 0x7fffffffd470, v_blob = 0x7fffffffd470}}, {v_type = 18, v_lock = 0 '\000', vval = {
v_number = 93824993201137, v_float = 4.6355705861970318e-310,
v_string = 0x555555640bf1 <lalloc+81> "H\205\300H\211\303t\277H\211\330[]A\\\303\017\037\200", v_list = 0x555555640bf1 <lalloc+81>,
v_dict = 0x555555640bf1 <lalloc+81>, v_partial = 0x555555640bf1 <lalloc+81>, v_job = 0x555555640bf1 <lalloc+81>, v_channel = 0x555555640bf1 <lalloc+81>,
v_blob = 0x555555640bf1 <lalloc+81>}}, {v_type = 4294956144, v_lock = -1 '\377', vval = {v_number = 93824999521904, v_float = 4.6355708984844148e-310,
v_string = 0x555555c47e70 "e", v_list = 0x555555c47e70, v_dict = 0x555555c47e70, v_partial = 0x555555c47e70, v_job = 0x555555c47e70,
v_channel = 0x555555c47e70, v_blob = 0x555555c47e70}}, {v_type = 1436489232, v_lock = 85 'U', vval = {v_number = 35, v_float = 1.7292297604443629e-322,
v_string = 0x23 <error: Cannot access memory at address 0x23>, v_list = 0x23, v_dict = 0x23, v_partial = 0x23, v_job = 0x23, v_channel = 0x23,
v_blob = 0x23}}, {v_type = 1436489232, v_lock = 85 'U', vval = {v_number = 93824993206393, v_float = 4.6355705864567127e-310,
v_string = 0x555555642079 <vim_strchr+201> "H\230H\001\303\017\266\003\205\300\017\204p\377\377\377A9\304u\342H\211\330[]A\\\303f.\017\037\204",
v_list = 0x555555642079 <vim_strchr+201>, v_dict = 0x555555642079 <vim_strchr+201>, v_partial = 0x555555642079 <vim_strchr+201>,
v_job = 0x555555642079 <vim_strchr+201>, v_channel = 0x555555642079 <vim_strchr+201>, v_blob = 0x555555642079 <vim_strchr+201>}}, {v_type = 1438940768,
v_lock = 85 'U', vval = {v_number = 93824997070352, v_float = 4.6355707773616526e-310, v_string = 0x5555559f1610 <globvardict+16> "?",
v_list = 0x5555559f1610 <globvardict+16>, v_dict = 0x5555559f1610 <globvardict+16>, v_partial = 0x5555559f1610 <globvardict+16>,
v_job = 0x5555559f1610 <globvardict+16>, v_channel = 0x5555559f1610 <globvardict+16>, v_blob = 0x5555559f1610 <globvardict+16>}}, {v_type = VAR_UNKNOWN,
v_lock = 0 '\000', vval = {v_number = 93824992576654, v_float = 4.6355705553434721e-310,
v_string = 0x5555555a848e <script_autoload+30> "H\205\300teH9\303t`H\211\337\350@\377\377\377\213-\032\244B",
v_list = 0x5555555a848e <script_autoload+30>, v_dict = 0x5555555a848e <script_autoload+30>, v_partial = 0x5555555a848e <script_autoload+30>,
v_job = 0x5555555a848e <script_autoload+30>, v_channel = 0x5555555a848e <script_autoload+30>, v_blob = 0x5555555a848e <script_autoload+30>}}, {
v_type = 1438940715, v_lock = 85 'U', vval = {v_number = 93824999521888, v_float = 4.6355708984836243e-310,
v_string = 0x555555c47e60 "\200\375R13_LocalBrowse", v_list = 0x555555c47e60, v_dict = 0x555555c47e60, v_partial = 0x555555c47e60,
v_job = 0x555555c47e60, v_channel = 0x555555c47e60, v_blob = 0x555555c47e60}}, {v_type = 1436489232, v_lock = 85 'U', vval = {v_number = 0, v_float = 0,
v_string = 0x0, v_list = 0x0, v_dict = 0x0, v_partial = 0x0, v_job = 0x0, v_channel = 0x0, v_blob = 0x0}}, {v_type = 1436489232, v_lock = 85 'U',
vval = {v_number = 93824992409744, v_float = 4.6355705470970224e-310, v_string = 0x55555557f890 <getnextac> "H\203>", v_list = 0x55555557f890 <getnextac>,
v_dict = 0x55555557f890 <getnextac>, v_partial = 0x55555557f890 <getnextac>, v_job = 0x55555557f890 <getnextac>, v_channel = 0x55555557f890 <getnextac>,
v_blob = 0x55555557f890 <getnextac>}}, {v_type = 1438940768, v_lock = 85 'U', vval = {v_number = 93824992577162, v_float = 4.6355705553685707e-310,
v_string = 0x5555555a868a <find_var_in_ht+282> "\205\300t\353\350\355$\004", v_list = 0x5555555a868a <find_var_in_ht+282>,
v_dict = 0x5555555a868a <find_var_in_ht+282>, v_partial = 0x5555555a868a <find_var_in_ht+282>, v_job = 0x5555555a868a <find_var_in_ht+282>,
v_channel = 0x5555555a868a <find_var_in_ht+282>, v_blob = 0x5555555a868a <find_var_in_ht+282>}}, {v_type = 1438940768, v_lock = 85 'U', vval = {
v_number = 0, v_float = 0, v_string = 0x0, v_list = 0x0, v_dict = 0x0, v_partial = 0x0, v_job = 0x0, v_channel = 0x0, v_blob = 0x0}}, {
v_type = VAR_UNKNOWN, v_lock = 0 '\000', vval = {v_number = 93824999521888, v_float = 4.6355708984836243e-310,
v_string = 0x555555c47e60 "\200\375R13_LocalBrowse", v_list = 0x555555c47e60, v_dict = 0x555555c47e60, v_partial = 0x555555c47e60,
v_job = 0x555555c47e60, v_channel = 0x555555c47e60, v_blob = 0x555555c47e60}}, {v_type = VAR_UNKNOWN, v_lock = 0 '\000', vval = {
v_number = 93824992579386, v_float = 4.6355705554784509e-310, v_string = 0x5555555a8f3a <find_var+106> "\353\345\017\037@",
v_list = 0x5555555a8f3a <find_var+106>, v_dict = 0x5555555a8f3a <find_var+106>, v_partial = 0x5555555a8f3a <find_var+106>,
v_job = 0x5555555a8f3a <find_var+106>, v_channel = 0x5555555a8f3a <find_var+106>, v_blob = 0x5555555a8f3a <find_var+106>}}}
argcount = <optimized out>
#10 0x0000555555721dd9 in ex_call (eap=0x7fffffffd780) at userfunc.c:3338
arg = 0x555555c47e36 "(expand(\"<amatch>\"))"
startarg = 0x555555c47e36 "(expand(\"<amatch>\"))"
name = 0x555555c47e60 "\200\375R13_LocalBrowse"
tofree = 0x555555c47e60 "\200\375R13_LocalBrowse"
len = 17
rettv = {v_type = VAR_NUMBER, v_lock = -1 '\377', vval = {v_number = 0, v_float = 0, v_string = 0x0, v_list = 0x0, v_dict = 0x0, v_partial = 0x0, v_job = 0x0,
v_channel = 0x0, v_blob = 0x0}}
lnum = 1
doesrange = 0
failed = 0
fudi = {fd_dict = 0x0, fd_newkey = 0x0, fd_di = 0x0}
partial = 0x0
#11 0x00005555555e73dc in do_one_cmd (cookie=0x7fffffffdec0, fgetline=0x55555557f890 <getnextac>, cstack=0x7fffffffd940, sourcing=1, cmdlinep=0x7fffffffd6e0)
at ex_docmd.c:2500
p = <optimized out>
errormsg = 0x0
after_modifier = <optimized out>
ea = {arg = 0x555555c47e29 "s:LocalBrowse(expand(\"<amatch>\"))", nextcmd = 0x0, cmd = 0x555555c47e24 "call s:LocalBrowse(expand(\"<amatch>\"))",
cmdlinep = 0x7fffffffd6e0, cmdidx = CMD_call, argt = 788613, skip = 0, forceit = 0, addr_count = 0, line1 = 1, line2 = 1, addr_type = ADDR_LINES, flags = 0,
do_ecmd_cmd = 0x0, do_ecmd_lnum = 0, append = 0, usefilter = 0, amount = 0, regname = 0, force_bin = 0, read_edit = 0, force_ff = 0, force_enc = 0,
bad_char = 0, useridx = 0, errmsg = 0x0, getline = 0x55555557f890 <getnextac>, cookie = 0x7fffffffdec0, cstack = 0x7fffffffd940, verbose_save = -1,
save_msg_silent = 0, did_esilent = 0, did_sandbox = 0}
save_cmdmod = {hide = 0, browse = 0, split = 0, tab = 0, confirm = 0, keepalt = 0, keepmarks = 0, keepjumps = 0, lockmarks = 0, keeppatterns = 0,
noswapfile = 0, save_ei = 0x0, filter_regmatch = {regprog = 0x0, startp = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, endp = {0x0, 0x0, 0x0, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, rm_ic = 0}, filter_force = 0}
cmd = <optimized out>
n = <optimized out>
lnum = <optimized out>
save_msg_scroll = 0
save_reg_executing = 0
ni = <optimized out>
#12 do_cmdline (cmdline=cmdline@entry=0x0, fgetline=fgetline@entry=0x55555557f890 <getnextac>, cookie=cookie@entry=0x7fffffffdec0, flags=flags@entry=7)
at ex_docmd.c:995
next_cmdline = <optimized out>
cmdline_copy = 0x555555c47e20 "sil call s:LocalBrowse(expand(\"<amatch>\"))"
used_getline = <optimized out>
recursive = 1
msg_didout_before_start = 0
count = <optimized out>
did_inc = 0
retval = 1
cstack = {cs_flags = {911, 110, 0, 0, 28728, -2258, 32767, 0, -9616, -1, 32767, 0, -25200, -2259, 32767, 0, 1, 0, 32767, 0, 32128, 21956, 21845, 0, 0, 0, 0,
0, 6, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, -9496, -1, 0, 0, 0, 0, 0, 0, 4, 0},
cs_pending = "\000\000\000\000\310\344\377\367\377\177\000\000\000\333\377\377\377\177\000\000\060z\377\367\377\177\000\000\001", '\000' <repeats 15 times>, "(\333\377\377\377\177", cs_pend = {csp_rv = {0x7ffff7de30c1, 0x4, 0x7ffff7ff7a30, 0x1, 0x0, 0x1, 0x7ffff7ffe170, 0x555555555b8a, 0xff878ec2, 0x0, 0x7ffff7ffe4c8,
0x7fffffffda70, 0x1f7ff73e8, 0x7ffff7ffe170, 0x7fffffffda60, 0x555555555b4b, 0x0, 0x0, 0x0, 0x7ffff72dca78, 0x7ffff7ff73e8, 0x0, 0x0, 0x0,
0x555500000005, 0x3d, 0x70, 0x1, 0x3100000005, 0x0, 0x0, 0x6e0000005b, 0x0, 0x0, 0x7c00000077, 0x0, 0x7ffff766fb00, 0x3d, 0x0, 0x0, 0x0, 0x5555559ff410,
0x555555c47da0, 0x0, 0x7fffffffdca0, 0x5555559ff680, 0x7ffff73068b0, 0x7fffffffdc80, 0x7ffff7670b78, 0x0}, csp_ex = {0x7ffff7de30c1, 0x4,
0x7ffff7ff7a30, 0x1, 0x0, 0x1, 0x7ffff7ffe170, 0x555555555b8a, 0xff878ec2, 0x0, 0x7ffff7ffe4c8, 0x7fffffffda70, 0x1f7ff73e8, 0x7ffff7ffe170,
0x7fffffffda60, 0x555555555b4b, 0x0, 0x0, 0x0, 0x7ffff72dca78, 0x7ffff7ff73e8, 0x0, 0x0, 0x0, 0x555500000005, 0x3d, 0x70, 0x1, 0x3100000005, 0x0, 0x0,
0x6e0000005b, 0x0, 0x0, 0x7c00000077, 0x0, 0x7ffff766fb00, 0x3d, 0x0, 0x0, 0x0, 0x5555559ff410, 0x555555c47da0, 0x0, 0x7fffffffdca0, 0x5555559ff680,
0x7ffff73068b0, 0x7fffffffdc80, 0x7ffff7670b78, 0x0}}, cs_forinfo = {0x1e, 0x5555559f8b10, 0x5555559ff4a0, 0x0, 0x12, 0x0, 0x5555559f8b10,
0x7fffffffdbe0, 0xffffffffffffffff, 0x7fffffffdbe0, 0x55555575a57d, 0x7fffffffdd18, 0x1, 0x555555c47df0, 0x7ffff73cc97c <__vsprintf_chk+140>,
0x5555fbad8001, 0x555555c47df0, 0x555555c47df0, 0x555555c47df0, 0x555555c47df0, 0x555555c47e0d, 0xffffffffffffffff, 0x555555c47df0, 0xffffffffffffffff,
0x0, 0x0, 0x0, 0x0, 0x0, 0x400000002, 0x5555559ff410, 0xffffffffffff0000, 0x0, 0x7fffffffdde0, 0x7ffff7303d26, 0xffffffffffffffff, 0x0, 0x0,
0x7ffff7303af8, 0x41535345ffffffff, 0x2e6d69762f534547, 0x555555006f6d, 0x7ffff766c5c0, 0x0, 0x7ffff7303a9f, 0x54552e42475f6e65, 0x55555575a647, 0x0,
0x18, 0x55555575a57d}, cs_line = {-8512, 32767, 1436562976, 21845, -147011379, 32767, 0, 0, 48, 48, -8720, 32767, -8912, 32767, 0, 0, 3, 48, 0, 0, 0, 0,
1433773639, 21845, 1438745664, 21845, 0, 0, 119, 124, 1436518208, 21845, -144246016, 32767, 34, 0, 1, 0, 1433773437, 21845, -8512, 32767, 1436562976,
21845, -147517596, 32767, 0, 0, 1433773639, 21845}, cs_idx = -1, cs_looplevel = 0, cs_trylevel = 0, cs_emsg_silent_list = 0x0, cs_lflags = 0 '\000'}
lines_ga = {ga_len = 0, ga_maxlen = 0, ga_itemsize = 16, ga_growsize = 10, ga_data = 0x0}
current_line = 0
fname = 0x0
breakpoint = 0x0
dbg_tick = 0x0
debug_saved = {trylevel = 0, force_abort = 0, caught_stack = 0x0, vv_exception = 0x0, vv_throwpoint = 0x0, did_emsg = 0, got_int = 0, did_throw = 0,
need_rethrow = 0, check_cstack = 0, current_exception = 0x0}
initial_trylevel = 0
saved_msg_list = 0x0
private_msg_list = 0x0
cmd_getline = 0x55555557f890 <getnextac>
cmd_cookie = 0x7fffffffdec0
cmd_loop_cookie = {lines_gap = 0x55555575a57d, current_line = 2, repeating = 0, getline = 0x7d8, cookie = 0x55555575a595}
call_depth = 1
#13 0x000055555558002e in apply_autocmds_group (event=EVENT_BUFENTER, fname=0x555555c47d80 "", fname_io=<optimized out>, force=<optimized out>, group=group@entry=-3,
buf=0x5555559fb020, eap=0x0) at autocmd.c:2120
sfname = 0x0
tail = <optimized out>
save_changed = 0
old_curbuf = 0x5555559fb020
retval = 1
save_sourcing_name = 0x0
save_sourcing_lnum = 0
save_autocmd_fname = 0x0
save_autocmd_fname_full = 0
save_autocmd_bufnr = 0
save_autocmd_match = 0x0
save_autocmd_busy = 0
save_autocmd_nested = 0
nesting = 1
patcmd = {curpat = 0x555555a03620, nextcmd = 0x0, group = -3, fname = 0x555555c47d80 "", sfname = 0x0, tail = 0x555555c47d80 "", event = EVENT_BUFENTER,
arg_bufnr = 1, next = 0x0}
ap = <optimized out>
save_current_sctx = {sc_sid = 0, sc_seq = 0, sc_lnum = 0, sc_version = 0}
funccal_entry = {top_funccal = 0x0, next = 0x0}
save_cmdarg = <optimized out>
save_cmdbang = 0
filechangeshell_busy = 0
wait_time = {tv_sec = 140737488346920, tv_usec = 93824997044704}
did_save_redobuff = 1
save_redo = {sr_redobuff = {bh_first = {b_next = 0x0, b_str = ""}, bh_curr = 0x0, bh_index = 0, bh_space = 0}, sr_old_redobuff = {bh_first = {b_next = 0x0,
b_str = ""}, bh_curr = 0x0, bh_index = 0, bh_space = 0}}
#14 0x0000555555580fb4 in apply_autocmds (event=<optimized out>, fname=<optimized out>, fname_io=<optimized out>, force=<optimized out>, buf=<optimized out>)
at autocmd.c:1615
No locals.
#15 0x0000555555750721 in vim_main2 () at main.c:740
No locals.
#16 0x000055555557ceba in main (argc=<optimized out>, argv=<optimized out>) at main.c:444
i = <optimized out>
(gdb) quit
A debugging session is active.

Inferior 1 [process 22668] will be killed.

Quit anyway? (y or n) y
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 11 2019 17:39:46)
Included patches: 1-1566
Modified by morr@NetBSD.org
Compiled by oc@e130
Huge version without GUI. Features included (+) or not (-):
+acl -farsi -mouse_sysmouse -tag_any_white
+arabic +file_in_path +mouse_urxvt -tcl
+autocmd +find_in_path +mouse_xterm +termguicolors
+autochdir +float +multi_byte +terminal
-autoservername +folding +multi_lang +terminfo
-balloon_eval -footer -mzscheme +termresponse
+balloon_eval_term +fork() +netbeans_intg +textobjects
-browse +gettext +num64 +textprop
-builtin_terms -hangul_input +packages +timers
+byte_offset +iconv +path_extra +title
+channel +insert_expand -perl -toolbar
+cindent +job +persistent_undo +user_commands
-clientserver +jumplist +postscript +vartabs
-clipboard +keymap +printer +vertsplit
+cmdline_compl +lambda +profile +virtualedit
+cmdline_hist +langmap -python +visual
+cmdline_info +libcall -python3 +visualextra
+comments +linebreak +quickfix +viminfo
+conceal +lispindent +reltime +vreplace
+cryptv +listcmds +rightleft +wildignore
+cscope +localmap -ruby +wildmenu
+cursorbind -lua +scrollbind +windows
+cursorshape +menu +signs +writebackup
+dialog_con +mksession +smartindent -X11
+diff +modify_fname -sound -xfontset
+digraphs +mouse +spell -xim
-dnd -mouseshape +startuptime -xpm
-ebcdic +mouse_dec +statusline -xsmp
+emacs_tags -mouse_gpm -sun_workshop -xterm_clipboard
+eval -mouse_jsbterm +syntax -xterm_save
+ex_extra +mouse_netterm +tag_binary
+extra_search +mouse_sgr -tag_old_static
system vimrc file: "/opt/pkg/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/opt/pkg/share/vim"
Compilation: cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: cc -L/opt/pkg/lib -Wl,-R/opt/pkg/lib -L/usr/local/lib -Wl,--as-needed -o vim -lm -lnsl -lncurses -liconv -ldl
=> Bootstrap dependency digest>=20010302: found digest-20190127
===> Skipping vulnerability checks.
WARNING: No /opt/pkg/pkgdb/pkg-vulnerabilities file found.
WARNING: To fix run: `/opt/pkg/sbin/pkg_admin -K /opt/pkg/pkgdb fetch-pkg-vulnerabilities'.
=> Checksum SHA1 OK for vim-8.1.1566.tar.gz
=> Checksum RMD160 OK for vim-8.1.1566.tar.gz
=> Checksum SHA512 OK for vim-8.1.1566.tar.gz
===> Installing dependencies for vim-8.1.1566
==========================================================================
The supported build options for vim are:

lua luajit perl python ruby

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or the following variable. Its current value is shown:

PKG_OPTIONS.vim (not defined)

==========================================================================
==========================================================================
The following variables will affect the build process of this package,
vim-8.1.1566. Their current value is shown below:

* CURSES_DEFAULT = ncurses

Based on these variables, the following variables have been set:

* CURSES_TYPE = ncurses
* TERMCAP_TYPE = curses

You may want to abort the process now with CTRL-C and change their value
before continuing. Be sure to run `/opt/pkg/bin/bmake clean' after
the changes.
==========================================================================
=> Tool dependency nbpatch-[0-9]*: found nbpatch-20151107
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency cwrappers>=20150314: found cwrappers-20180325
=> Full dependency vim-share-8.1.1566{,nb*}: found vim-share-8.1.1566
=> Full dependency ncurses>=6.0: found ncurses-6.1nb5
===> Overriding tools for vim-8.1.1566
===> Extracting for vim-8.1.1566
===> Patching for vim-8.1.1566
=> Applying pkgsrc patches for vim-8.1.1566
=> Verifying /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-Makefile
=> Applying pkgsrc patch /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-Makefile
=> Verifying /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-auto_configure
=> Applying pkgsrc patch /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-auto_configure
=> Verifying /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-configure
=> Applying pkgsrc patch /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-configure
=> Verifying /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-feature.h
=> Applying pkgsrc patch /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-feature.h
=> Verifying /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-link.sh
=> Applying pkgsrc patch /home/oc/pkgsrc/current/pkgsrc/editors/vim/../../editors/vim-share/patches/patch-link.sh
find /home/oc/pkgsrc/work/editors/vim/work -name '*.orig_dist' -exec rm -f {} \;
===> Creating toolchain wrappers for vim-8.1.1566
===> Configuring for vim-8.1.1566
=> Substituting "sysconfdir" in feature.h
=> Modifying GNU configure scripts to avoid --recheck
=> Replacing config-guess with pkgsrc versions
=> Replacing config-sub with pkgsrc versions
=> Replacing install-sh with pkgsrc version
=> Checking for portability problems in extracted files
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for x86_64-debian-linux-gcc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking for cc option to accept ISO C99... none needed
checking how to run the C preprocessor... cc -E
checking for grep that handles long lines and -e... (cached) /bin/grep
checking for egrep... (cached) /bin/egrep
checking for fgrep... /bin/grep -F
checking for library containing strerror... none required
checking for gawk... /opt/pkg/bin/nawk
checking for strip... strip
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking if the compiler supports trailing commas... yes
checking if the compiler supports C++ comments... yes
checking --enable-fail-if-missing argument... no
checking for clang version... N/A
configure: checking for buggy tools...
- sh is 'GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.' - probably OK.
checking for BeOS... no
checking for QNX... no
checking for Darwin (Mac OS X)... no
checking AvailabilityMacros.h usability... no
checking AvailabilityMacros.h presence... no
checking for AvailabilityMacros.h... no
checking --with-local-dir argument... Defaulting to /usr/local
checking --with-vim-name argument... Defaulting to vim
checking --with-ex-name argument... Defaulting to ex
checking --with-view-name argument... Defaulting to view
checking --with-global-runtime argument... no
checking --with-modified-by argument... morr@NetBSD.org
checking if character set is EBCDIC... no
checking --disable-smack argument... no
checking linux/xattr.h usability... yes
checking linux/xattr.h presence... yes
checking for linux/xattr.h... yes
checking attr/xattr.h usability... no
checking attr/xattr.h presence... no
checking for attr/xattr.h... no
checking --disable-selinux argument... no
checking for is_selinux_enabled in -lselinux... no
checking --with-features argument... Defaulting to huge
checking --with-compiledby argument... no
checking --disable-xsmp argument... no
checking --disable-xsmp-interact argument... no
checking --enable-luainterp argument... no
checking --enable-mzschemeinterp argument... no
checking --enable-perlinterp argument... no
checking --enable-pythoninterp argument... no
checking --enable-python3interp argument... no
checking --enable-tclinterp argument... no
checking --enable-rubyinterp argument... no
checking --enable-cscope argument... yes
checking --disable-netbeans argument... no
checking --disable-channel argument... no
checking for socket in -lsocket... no
checking for gethostbyname in -lnsl... yes
checking whether compiling with process communication is possible... yes
checking --enable-terminal argument... defaulting to yes
checking --enable-autoservername argument... no
checking --enable-multibyte argument... yes
checking --disable-rightleft argument... no
checking --disable-arabic argument... no
checking --enable-hangulinput argument... no
checking --enable-xim argument... defaulting to auto
checking --enable-fontset argument... no
defaulting to: don't HAVE_X11
checking --enable-gui argument... no GUI support
checking for x86_64-debian-linux-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking X11/SM/SMlib.h usability... no
checking X11/SM/SMlib.h presence... no
checking for X11/SM/SMlib.h... no
checking for /proc link to executable... /proc/self/exe
checking for CYGWIN or MSYS environment... no
checking whether toupper is broken... no
checking whether __DATE__ and __TIME__ work... yes
checking whether __attribute__((unused)) is allowed... yes
checking elf.h usability... yes
checking elf.h presence... yes
checking for elf.h... yes
checking for main in -lelf... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking stdint.h usability... yes
checking stdint.h presence... yes
checking for stdint.h... yes
checking stdlib.h usability... yes
checking stdlib.h presence... yes
checking for stdlib.h... yes
checking string.h usability... yes
checking string.h presence... yes
checking for string.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking termcap.h usability... yes
checking termcap.h presence... yes
checking for termcap.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sgtty.h usability... yes
checking sgtty.h presence... yes
checking for sgtty.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/types.h usability... yes
checking sys/types.h presence... yes
checking for sys/types.h... yes
checking termio.h usability... yes
checking termio.h presence... yes
checking for termio.h... yes
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking inttypes.h usability... yes
checking inttypes.h presence... yes
checking for inttypes.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking unistd.h usability... yes
checking unistd.h presence... yes
checking for unistd.h... yes
checking stropts.h usability... yes
checking stropts.h presence... yes
checking for stropts.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/systeminfo.h usability... no
checking sys/systeminfo.h presence... no
checking for sys/systeminfo.h... no
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking sys/stream.h usability... no
checking sys/stream.h presence... no
checking for sys/stream.h... no
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking libc.h usability... no
checking libc.h presence... no
checking for libc.h... no
checking sys/statfs.h usability... yes
checking sys/statfs.h presence... yes
checking for sys/statfs.h... yes
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/ptms.h usability... no
checking sys/ptms.h presence... no
checking for sys/ptms.h... no
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking util/debug.h usability... no
checking util/debug.h presence... no
checking for util/debug.h... no
checking util/msg18n.h usability... no
checking util/msg18n.h presence... no
checking for util/msg18n.h... no
checking frame.h usability... no
checking frame.h presence... no
checking for frame.h... no
checking sys/acl.h usability... no
checking sys/acl.h presence... no
checking for sys/acl.h... no
checking sys/access.h usability... no
checking sys/access.h presence... no
checking for sys/access.h... no
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking for sys/ptem.h... no
checking for sys/sysctl.h... yes
checking for pthread_np.h... no
checking strings.h usability... yes
checking strings.h presence... yes
checking for strings.h... yes
checking if strings.h can be included after string.h... yes
checking whether cc needs -traditional... no
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for uid_t in sys/types.h... yes
checking for uint32_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for ino_t... yes
checking for dev_t... yes
checking whether byte ordering is bigendian... no
checking for inline... inline
checking for rlim_t... yes
checking for stack_t... yes
checking whether stack_t has an ss_base field... no
checking --with-tlib argument... ncurses
checking for linking with ncurses library... OK
checking for tgetent()... yes
checking whether we talk terminfo... yes
checking what tgetent() returns for an unknown terminal... zero
checking whether termcap.h contains ospeed... yes
checking whether termcap.h contains UP, BC and PC... yes
checking whether tputs() uses outfuntype... no
checking whether sys/select.h and sys/time.h may both be included... yes
checking for /dev/ptc... no
checking for SVR4 ptys... yes
checking for ptyranges... don't know
checking default tty permissions/group... can't determine - assume ptys are world accessible
world
checking return type of signal handlers... void
checking for struct sigcontext... yes
checking getcwd implementation is broken... no
checking for fchdir... yes
checking for fchown... yes
checking for fchmod... yes
checking for fsync... yes
checking for getcwd... yes
checking for getpseudotty... no
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for getrlimit... yes
checking for gettimeofday... yes
checking for localtime_r... yes
checking for lstat... yes
checking for memset... yes
checking for mkdtemp... yes
checking for nanosleep... yes
checking for opendir... yes
checking for putenv... yes
checking for qsort... yes
checking for readlink... yes
checking for select... yes
checking for setenv... yes
checking for getpgid... yes
checking for setpgid... yes
checking for setsid... yes
checking for sigaltstack... yes
checking for sigstack... yes
checking for sigset... yes
checking for sigsetjmp... no
checking for sigaction... yes
checking for sigprocmask... yes
checking for sigvec... no
checking for strcasecmp... yes
checking for strerror... yes
checking for strftime... yes
checking for stricmp... no
checking for strncasecmp... yes
checking for strnicmp... no
checking for strpbrk... yes
checking for strtol... yes
checking for tgetent... yes
checking for towlower... yes
checking for towupper... yes
checking for iswupper... yes
checking for usleep... yes
checking for utime... yes
checking for utimes... yes
checking for mblen... yes
checking for ftruncate... yes
checking for unsetenv... yes
checking for posix_openpt... yes
checking for sys/select.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking types of arguments for select... int,fd_set *,struct timeval *
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking --enable-canberra argument... Defaulting to yes
checking for libcanberra... no
checking for st_blksize... yes
checking whether stat() ignores a trailing slash... no
checking for iconv_open()... yes; with -liconv
checking for nl_langinfo(CODESET)... yes
checking for strtod in -lm... yes
checking for strtod() and other floating point functions... yes
checking for isinf()... yes
checking for isnan()... yes
checking --disable-acl argument... no
checking for acl_get_file in -lposix1e... no
checking for acl_get_file in -lacl... no
checking for POSIX ACL support... no
checking for acl_get in -lsec... no
checking for Solaris ACL support... no
checking for AIX ACL support... no
checking --disable-gpm argument... no
checking for gpm... no
checking --disable-sysmouse argument... no
checking for sysmouse... no
checking for FD_CLOEXEC... yes
checking for rename... yes
checking for sysctl... not usable
checking for sysinfo... yes
checking for sysinfo.mem_unit... yes
checking for sysconf... yes
checking size of int... 4
checking size of long... 8
checking size of time_t... 8
checking size of off_t... 8
checking uint32_t is 32 bits... ok
checking whether memmove handles overlaps... yes
checking for _xpg4_setrunelocale in -lxpg4... no
checking how to create tags... ctags
checking how to run man with a section nr... man -s
checking --disable-nls argument... no
checking for msgfmt... msgfmt
checking for NLS... gettext() works
checking for bind_textdomain_codeset... yes
checking for _nl_msg_cat_cntr... yes
checking if msgfmt supports --desktop... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for dlopen()... no
checking for dlopen() in -ldl... yes
checking for dlsym()... yes
checking setjmp.h usability... yes
checking setjmp.h presence... yes
checking for setjmp.h... yes
checking for GCC 3 or later... yes
checking whether we need -D_FORTIFY_SOURCE=1... yes
checking whether we need to force -D_FILE_OFFSET_BITS=64... no
checking linker --as-needed support... yes
configure: updating cache auto/config.cache
configure: creating auto/config.status
config.status: creating auto/config.mk
config.status: creating auto/config.h
===> Building for vim-8.1.1566
/bin/sh install-sh -c -d objects
touch objects/.dirstamp
CC="cc -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses " srcdir=. sh ./osdef.sh
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/arabic.o arabic.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/autocmd.o autocmd.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/beval.o beval.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/buffer.o buffer.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/change.o change.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/blob.o blob.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/blowfish.o blowfish.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/crypt.o crypt.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/crypt_zip.o crypt_zip.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/debugger.o debugger.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/dict.o dict.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/diff.o diff.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/digraph.o digraph.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/edit.o edit.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/eval.o eval.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/evalfunc.o evalfunc.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_cmds.o ex_cmds.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_docmd.o ex_docmd.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_eval.o ex_eval.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_getln.o ex_getln.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/fileio.o fileio.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/findfile.o findfile.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/fold.o fold.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/getchar.o getchar.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/hardcopy.o hardcopy.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/hashtab.o hashtab.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/if_cscope.o if_cscope.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/if_xcmdsrv.o if_xcmdsrv.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/indent.o indent.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/insexpand.o insexpand.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/list.o list.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/mark.o mark.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/memline.o memline.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/menu.o menu.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/misc1.o misc1.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/misc2.o misc2.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/move.o move.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/mbyte.o mbyte.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/normal.o normal.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ops.o ops.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/option.o option.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/os_unix.o os_unix.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
creating auto/pathdef.c
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/pathdef.o auto/pathdef.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/popupmnu.o popupmnu.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/popupwin.o popupwin.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/pty.o pty.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/quickfix.o quickfix.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/regexp.o regexp.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/screen.o screen.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/search.o search.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/sha256.o sha256.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/sign.o sign.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/sound.o sound.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/spell.o spell.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/spellfile.o spellfile.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/syntax.o syntax.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/tag.o tag.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/term.o term.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/terminal.o terminal.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/textprop.o textprop.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ui.o ui.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/undo.o undo.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/usercmd.o usercmd.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/userfunc.o userfunc.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/string.h:635:0,
from os_unix.h:469,
from vim.h:227,
from userfunc.c:14:
In function 'strcpy',
inlined from 'add_nr_var' at userfunc.c:618:5,
inlined from 'call_user_func' at userfunc.c:858:5,
inlined from 'call_func' at userfunc.c:1621:7:
/usr/include/x86_64-linux-gnu/bits/string3.h:110:10: warning: call to __builtin___memcpy_chk will always overflow destination buffer
return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function 'strcpy',
inlined from 'call_user_func' at userfunc.c:866:5,
inlined from 'call_func' at userfunc.c:1621:7:
/usr/include/x86_64-linux-gnu/bits/string3.h:110:10: warning: call to __builtin___memcpy_chk will always overflow destination buffer
return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function 'strcpy',
inlined from 'add_nr_var' at userfunc.c:618:5,
inlined from 'call_user_func' at userfunc.c:881:5,
inlined from 'call_func' at userfunc.c:1621:7:
/usr/include/x86_64-linux-gnu/bits/string3.h:110:10: warning: call to __builtin___memcpy_chk will always overflow destination buffer
return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function 'strcpy',
inlined from 'add_nr_var' at userfunc.c:618:5,
inlined from 'call_user_func' at userfunc.c:883:5,
inlined from 'call_func' at userfunc.c:1621:7:
/usr/include/x86_64-linux-gnu/bits/string3.h:110:10: warning: call to __builtin___memcpy_chk will always overflow destination buffer
return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/window.o window.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/encoding.o libvterm/src/encoding.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/keyboard.o libvterm/src/keyboard.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/mouse.o libvterm/src/mouse.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/parser.o libvterm/src/parser.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/pen.o libvterm/src/pen.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/termscreen.o libvterm/src/termscreen.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/state.o libvterm/src/state.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/unicode.o libvterm/src/unicode.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Ilibvterm/include -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DINLINE="" -DVSNPRINTF=vim_vsnprintf -DIS_COMBINING_FUNCTION=utf_iscomposing_uint -DWCWIDTH_FUNCTION=utf_uint2cells -o objects/vterm.o libvterm/src/vterm.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/netbeans.o netbeans.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/channel.o channel.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/xdiffi.o xdiff/xdiffi.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/xemit.o xdiff/xemit.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/xprepare.o xdiff/xprepare.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/xutils.o xdiff/xutils.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/xhistogram.o xdiff/xhistogram.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/xpatience.o xdiff/xpatience.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/charset.o charset.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/json.o json.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/main.o main.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/memfile.o memfile.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/message.o message.c
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
cc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/pkg/include/ncurses -g -O2 -I/usr/include -I/opt/pkg/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 version.c -o objects/version.o
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly.
cc -L/opt/pkg/lib -Wl,-R/opt/pkg/lib -L/usr/local/lib -Wl,--as-needed -o vim objects/arabic.o objects/autocmd.o objects/beval.o objects/buffer.o objects/change.o objects/blob.o objects/blowfish.o objects/crypt.o objects/crypt_zip.o objects/debugger.o objects/dict.o objects/diff.o objects/digraph.o objects/edit.o objects/eval.o objects/evalfunc.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/findfile.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/hashtab.o objects/if_cscope.o objects/if_xcmdsrv.o objects/indent.o objects/insexpand.o objects/list.o objects/mark.o objects/memline.o objects/menu.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/popupwin.o objects/pty.o objects/quickfix.o objects/regexp.o objects/screen.o objects/search.o objects/sha256.o objects/sign.o objects/sound.o objects/spell.o objects/spellfile.o objects/syntax.o objects/tag.o objects/term.o objects/terminal.o objects/textprop.o objects/ui.o objects/undo.o objects/usercmd.o objects/userfunc.o objects/version.o objects/window.o objects/encoding.o objects/keyboard.o objects/mouse.o objects/parser.o objects/pen.o objects/termscreen.o objects/state.o objects/unicode.o objects/vterm.o objects/netbeans.o objects/channel.o objects/xdiffi.o objects/xemit.o objects/xprepare.o objects/xutils.o objects/xhistogram.o objects/xpatience.o objects/charset.o objects/json.o objects/main.o objects/memfile.o objects/message.o -lm -lnsl -lncurses -liconv -ldl
link.sh: Linked fine
*** Please use pkgtools/verifypc to sanity check dependencies.
===> Installing for vim-8.1.1566
=> Generating pre-install file lists
/bin/sh install-sh -c -d /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin
chmod 755 /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin
if test -f /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/vim; then mv -f /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/vim /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/vim.rm; rm -f /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/vim.rm; fi
cp vim /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin
strip /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/vim
chmod 755 /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/vim
/bin/rm -f /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/rvim
/bin/ln -s vim /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/rvim
/bin/rm -f /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/rview
/bin/ln -s vim /home/oc/pkgsrc/work/editors/vim/work/.destdir/opt/pkg/bin/rview
=> Automatic manual page handling
=> Generating post-install file lists
=> Checking file-check results for vim-8.1.1566
=> Checking for non-existent script interpreters in vim-8.1.1566
=> Checking file permissions in vim-8.1.1566
=> Checking for missing run-time search paths in vim-8.1.1566
WARNING: Skipping check for SSP in DESTDIR mode.
=> Checking for work-directory references in vim-8.1.1566
=> Creating binary package /home/oc/pkgsrc/work/editors/vim/work/.packages/vim-8.1.1566.tgz
===> Building binary package for vim-8.1.1566
=> Creating binary package /home/oc/pkgsrc/packages/All/vim-8.1.1566.tgz
===> Replacing for vim-8.1.1566
=> Becoming ``root'' to make su-replace (sudo)
===> Updating using binary package of vim-8.1.1566
/usr/bin/env /opt/pkg/sbin/pkg_add -K /opt/pkg/pkgdb -U -D /home/oc/pkgsrc/work/editors/vim/work/.packages/vim-8.1.1566.tgz
=> Dropping ``root'' privileges.
On Fri, 12 Jul 2019 at 07:18, Dominique Pellé <dominique.pelle@gmail.com> wrote:

> Your links don't work unfortunately.

Yes, sorry, blame Debian. I'm not sure if attachments are allowed, but
I've attached vim-version, build logs and the crash logs. Let me know
if they are visible and allowed.

>
> My guess is that you did not build with:
>
> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1

As per logs, this was part of the compilation options.


> Other things to try:
>
> 1) run vim with valgrind, which will report memory errors
> if any:
>
> $ valgrind --num-callers=50 --track-origins=yes ./vim 2> vg.log
>
> Then look at vg.log
>
> 2) You can also build with asan (address sanitizer).
> Uncomment out this line in vim/src/Makefile:
>
> SANITIZER_CFLAGS = -g -O0 -fsanitize=undefined -fno-omit-frame-pointer
>
> Then:
>
> $ cd vim/src
> $ make clean ; make -j8
> $ ./vim 2> asan.log
>

I'll forward this to the pkgsr-users list. If the logs are not
attached, I'll paste them in my next email.


--
Ottavio Caruso

--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAEJNuHyirg5NV4epX7PfrUiCiB3JAsyVLSv-%2BDsOpqo1Whp8YQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.