Re: error pulling

[tooth pik]

i did a "git reset --hard" and all is working normally now

sorry for the noise

On Thu, Dec 28, 2023 at 6:49 PM Ernie Rael  wrote:

> On 23/12/28 3:48 PM, tooth pik wrote:
>
> is anyone else getting this:
>
> I don't use github, but in mercurial I frequently get "modified" status
> for a file in src/po after some combo of pull/build/update. I revert the
> file to get rid of the change. Not sure what causes it, build/makefile?
>
> -ernie
>
>
> Updating 7d0abf2cb..7e4f62a25
> error: Your local changes to the following files would be overwritten by
> merge:
> src/po/ru.cp1251.po
> Please commit your local changes or stash them before you merge.
> Aborting
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/CALfSX1xEnVco0KxsKu443pGv0OqefyPC%3DsuvDQUjdqZTRsCphw%40mail.gmail.com
> <https://groups.google.com/d/msgid/vim_dev/CALfSX1xEnVco0KxsKu443pGv0OqefyPC%3DsuvDQUjdqZTRsCphw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/b8e1d615-78db-4095-95af-6589dcf47f4f%40raelity.com
> <https://groups.google.com/d/msgid/vim_dev/b8e1d615-78db-4095-95af-6589dcf47f4f%40raelity.com?utm_medium=email_source=footer>
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1w4es0ixKMKVwn2GgvzTG-uaW2MyvLxn0yr81LhesX2eg%40mail.gmail.com.

error pulling

[tooth pik]

is anyone else getting this:

Updating 7d0abf2cb..7e4f62a25
error: Your local changes to the following files would be overwritten by
merge:
src/po/ru.cp1251.po
Please commit your local changes or stash them before you merge.
Aborting

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xEnVco0KxsKu443pGv0OqefyPC%3DsuvDQUjdqZTRsCphw%40mail.gmail.com.

commit emails

[tooth pik]

up until about december 1 i would get an email in vim_dev@googlegroups.com
whenever christian committed a patch -- i am no longer seeing those emails,
while there have been many patches committed -- this isn't necessarily a
problem for me, i'm just asking:  are the emails a thing of the past?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xm6nrKXvRH3txTZR45sz1yu00u_cfBHba2Np%2BRF5Xz9g%40mail.gmail.com.

Re: actual error

[tooth pik]

ahh -- you didn't say the "--hard" option before -- that fixed it, thank you

i don't understand any of this, honestly, i didn't change anything

On Sun, Aug 20, 2023 at 3:34 AM Christian Brabandt 
wrote:

>
> On Sa, 19 Aug 2023, tooth pik wrote:
>
> >
> > Unstaged changes after reset:
> > M src/po/ja.sjis.po
> > M src/po/zh_CN.cp936.po
> > M src/po/zh_CN.po
> >
> > error: Your local changes to the following files would be overwritten by
> merge:
> > src/po/ja.sjis.po
> > src/po/zh_CN.cp936.po
> > src/po/zh_CN.po
> > Please commit your changes or stash them before you merge.
> > Aborting
> > Updating 56bafd7a6..4b1cc7906
>
> Not sure what you are trying to say here. You need to get rid of the
> changes to your local files before you can update them. So that's why I
> suggested to use git reset --hard. Note this will wipe out all your
> changes. So only do this if you don't care about it. Other options would
> be to use git stash for example, that would stash away your changes (and
> you could get them later back).
>
> Best,
> Christian
> --
> Fashion is a form of ugliness so intolerable that we have to alter it
> every six months.
> -- Oscar Wilde
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/ZOHQKfeIIrh8kn0D%40256bit.org.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xPo%2BaLr0y7%3DW1QM3caQtign3Sarx8f5bvD46MeksbOZQ%40mail.gmail.com.

Re: actual error

[tooth pik]

Unstaged changes after reset:
M src/po/ja.sjis.po
M src/po/zh_CN.cp936.po
M src/po/zh_CN.po

error: Your local changes to the following files would be overwritten by
merge:
src/po/ja.sjis.po
src/po/zh_CN.cp936.po
src/po/zh_CN.po
Please commit your changes or stash them before you merge.
Aborting
Updating 56bafd7a6..4b1cc7906

On Sat, Aug 19, 2023 at 3:09 PM Christian Brabandt 
wrote:

>
> On Sa, 19 Aug 2023, tooth pik wrote:
>
> > attached (i think)
>
> Try git reset --hard to get rid of the local changes, then pull again
> the latest changes. It should then work again.
>
>
> Best,
> Christian
> --
> Successful and fortunate crime is called virtue.
> -- Seneca
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/ZOEhhI4Gj%2BCbnSsH%40256bit.org.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1yJUiEqwtw3SPKU%2BCrpH8%3DRBOK6kd8zSEuHP-Mz4hamNQ%40mail.gmail.com.

actual error

[tooth pik]

attached (i think)

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wDNZfhXaXpCptzXzB3Z7hb9xPgyOYz3V-bx6Z-hH4Nxw%40mail.gmail.com.


save-git-failure
Description: Binary data

did git pull, up to 9.0.1754, make now fails with local changes to several files must be merged

[tooth pik]

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zbn71ARhJrChhPUYsN1g%3DfF9AzcSSAVUbgcqecr5f3uA%40mail.gmail.com.

Re: Where is Bram?

[tooth pik]

i've been wondering the same thing -- my guess was he's in africa again

On Sat, Aug 5, 2023 at 12:34 AM Yegappan Lakshmanan 
wrote:

> Hi all,
>
> I haven't seen any emails from Bram to the mailing list for more than a
> month.
> Is he on vacation?  Has anyone had any contact with him in the last month?
>
> Regards,
> Yegappan
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3De52bn9Hfip8VAs2N%3DNTEhNTjHkSkyzp0TKfpuiiPz4Q%40mail.gmail.com
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1ym4mLnioH5mhYO208kZYVNodgVc9mET5%2BQUBWBO7homQ%40mail.gmail.com.

patch withdrawal

[tooth pik]

is Bram in Africa or something?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zFW%2BwXJmfEZ_gQWrO0-pvNfQa3NnOtEukH-ToYMe8-tA%40mail.gmail.com.

Re: X11 requirements -- solved

[tooth pik]

thanx tony -- yer a mench

On Thu, Jun 15, 2023 at 11:06 AM Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:

> On Thu, Jun 15, 2023 at 5:24 PM tooth pik  wrote:
> >
> > i thought i had exhausted google, but with yet another stab at it, in
> vim.fandom.com i found reference to two packages i didn't have:
> libxpm-dev and libxt-dev
> >
> > i added both and boom, i again have a gui -- i don't know if i needed
> both of them, but now it builds fine
> >
> > i apologize for the noise
>
> I think you need them both, to go with the -lXpm -lXt arguments found
> immediately before -lX11 on the gvim "Linking:" line.
>
> Congratulations!
> Tony.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/CAJkCKXt5O2HZLY4dYRjrooRWYebH9Tz5G4vcHMfScpKJCwysWg%40mail.gmail.com
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1ytes1ribewybhiTF9PGORCQO%2BBNt6UEQ_FLgLTJ5kd-A%40mail.gmail.com.

X11 requirements -- solved

[tooth pik]

i thought i had exhausted google, but with yet another stab at it, in
vim.fandom.com i found reference to two packages i didn't have:  libxpm-dev
and libxt-dev

i added both and boom, i again have a gui -- i don't know if i needed both
of them, but now it builds fine

i apologize for the noise

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zU33g7jyJBwMd1XMy_aif5D5yQnYpvhzEW%2B-D9tRRNOQ%40mail.gmail.com.

X11 requirements list

[tooth pik]

some months ago i managed to break gvim messing around doing i wish i
remembered what, probably something to do with getting nvidia drivers to
work on my system

for me vim no longer builds with X11, vim builds fine but no gui

is there somewhere a list of packages required for X11 to successfully link
into vim?  my system (currently opensuse 15.4, gtk3, kde) shows X11 as fine
itself, everything else seems fine, even the nvidia drivers are working up
to snuff

all myconfig will tell me is it can't find X11

any help will be appreciated

tia

toothpik

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1w4PAHP89%3DkC4x7rZi%2Bm2V1eYsrEz6qdE3pPh1AyDtjNw%40mail.gmail.com.

Re: PS2 prompt appears after quitting vim

[tooth pik]

it's still doing it, but "it" isn't what i thought it was

it's not the PS2 prompt being used, it's the parts of PS1 that have to be
evaluated
are simply not being evaluated: the $(date '+%H:%M') and the \w

when my PS1 is "$(date '+%H:%M') /w > " what winds up showing is the "> "

so there appears to be an evaluation of PS1 being skipped...

On Sat, Dec 17, 2022 at 1:25 PM Bram Moolenaar  wrote:

>
> > when i set PS1 to '$(date "+%H:%M") \w> ' in my ~/.bashrc i get a bash
> > prompt with current time of day when i hit enter, current PWD, a
> > greater than sign, and a space
> >
> > just enter "echo $PS1" to see how yours is set
> >
> > echo $TERM returns xterm
> >
> > in bash the PS2 prompt is for when you are inside some functioning
> > process but it needs input
>
> Aha, you are talking about bash.
>
> I don't know how bash decides to show $PS2 and how Vim can cause that.
> I also cannot reproduce the problem.  Perhaps someone can look into it.
>
> --
> Computers are not intelligent.  They only think they are.
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1yV_NC8B5QYY51kEnQ79qhiyTLgNeOdiVBo-U5bM6_C4g%40mail.gmail.com.

Re: PS2 prompt appears after quitting vim

[tooth pik]

when i set PS1 to '$(date "+%H:%M") \w> ' in my ~/.bashrc i get a bash
prompt with
current time of day when i hit enter, current PWD, a greater than sign, and
a space

just enter "echo $PS1" to see how yours is set

echo $TERM returns xterm

in bash the PS2 prompt is for when you are inside some functioning process
but it needs
input

On Sat, Dec 17, 2022 at 9:03 AM Bram Moolenaar  wrote:

>
> > dunno if it's something i borked or vim has changed, but for the last day
> > or so when i quit vim i'm at the PS2 prompt, not the PS1
> >
> > hitting enter clears it back to the PS1 prompt BUT THAT'S AN EXTRA
> KEYSTROKE
> >
> > i'm using a slightly borked opensuse (15.3), X11, KDE, bash shell
> >
> > if i try to edit with nano when i quit i am at the PS1 prompt
> >
> > it happens if i start vim --clean so i can't suspect my .vimrc
>
> What do you mean with "PS2" and "PS1" prompt?
>
> What terminal are you using and what is the value of 'term' ?
>
> --
> Veni, Vidi, Video -- I came, I saw, I taped what I saw.
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xX1ivMzZ_-aszkOp15dKfjuvN-XVZ-cZeUAtbJjng1Zg%40mail.gmail.com.

PS2 prompt appears when quitting vim

[tooth pik]

interestingly, if there's another argument when i start vim, for example a
'+' to take me to the bottom of the file, when quitting i am at the PS1
prompt as expected

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wJMHw_U480jUrWgW0XmoV9Os0-vzCLCPFOWm7BAT36sA%40mail.gmail.com.

PS2 prompt appears after quitting vim

[tooth pik]

dunno if it's something i borked or vim has changed, but for the last day
or so when i quit vim i'm at the PS2 prompt, not the PS1

hitting enter clears it back to the PS1 prompt BUT THAT'S AN EXTRA KEYSTROKE

i'm using a slightly borked opensuse (15.3), X11, KDE, bash shell

if i try to edit with nano when i quit i am at the PS1 prompt

it happens if i start vim --clean so i can't suspect my .vimrc

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wcoX_m4GHg0MBeaE4JYWMVEQQuSM8LCH9Zrb_gur3wyQ%40mail.gmail.com.

gvim bombs

[tooth pik]

dunno the state of my code now -- i did a

git checkout v9.0.0814

did a rebuild and got 813

the good news being my calendar app works again

when the dust settles will a simple git pull get me back in
sync with the team?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wU30GVm45vpJVb_j4go2h1n9B3gapKOJSPyfB7jkRyag%40mail.gmail.com.

gvim bombs with SEGV

[tooth pik]

the group emails indicate current is 816, but when i git pull and rebuild
i get 815

and this new 815 bombs when i run my calendar app, the relevant line of
which is

gvim -geometry 22x${lc}+1692+517 --servername CAL2 -S ~/.vim/sacal22.vim -c
'call MakeMeA22Cal()' -c 'set hlsearch' 2>/dev/null

where MakeMeA22Cal() pulls in a two month calendar and calls Hideme() which
sets noswapfile,
buftype=nofile, and bufhidden=hide

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wgmLEEoSoKYznMQ_JSgY1nbjZd8J8eFwz5XcaUyhHneg%40mail.gmail.com.

Re: can't build since 9.0.0752

[tooth pik]

Awesome, thanks! you're the man!

On Sat, Oct 15, 2022 at 10:31 AM Bram Moolenaar  wrote:

>
> > i just git pulled up to 0761 and buffer.c bombs due to not knowing
> > about b_p_lop
>
> Was missing from 9.0.0761, added in 9.0.0762.
>
>
> --
> "When I die, I want a tombstone that says "GAME OVER" - Ton Richters
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xNyD-A6%3DfvAv1scFG0N2%3DRTDPpSNTTq6LqCuYCez08BQ%40mail.gmail.com.

can't build since 9.0.0752

[tooth pik]

i just git pulled up to 0761 and buffer.c bombs due to not knowing
about b_p_lop

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wCs%3D86dj%2BOcu%2B5q_zriK3NZD-q5M-RWdSK0FSRPfXWow%40mail.gmail.com.

Re: Removing the rightleft feature?

[tooth pik]

it seems to me everyone would be better served by splitting vim into two:
normal
vim that goes left to right and arabic vim (viml?) that goes right to left
-- both apps
would be simpler because they wouldn't have to go both directions.



On Thu, Sep 29, 2022 at 9:28 AM Bram Moolenaar  wrote:

>
> The +rightleft feature has not gotten any work done for quite a while.
> In the past we would get a bug report once in a while.  These days I'm
> sure a lot of things have been added that do not work with 'rightleft'
> set, and I haven't heard complaints.
>
> I think 'rightleft' is most useful when working on Hebrew or Arabic
> text.  Any users around who do that?  Is nothing broken?
>
> The code for rightleft handling is all over the place and makes some
> functions quite complex.  It would help a lot if we can remove it.
>
> On the other hand, if someone would want to pick up fixing the
> +rightleft feature, the current code is probably a good starting point.
> That is why it's left in until now.  Even though bi-directional text
> handling probably needs to be done differently, using markers in the
> text.  But that is also very complicated, e.g. what does "d3w" do when
> some text is right-to-left?
>
> Opinions?
>
> --
> hundred-and-one symptoms of being an internet addict:
> 219. Your spouse has his or her lawyer deliver the divorce papers...
>  via e-mail.
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/20220929142806.C86491C05F2%40moolenaar.net
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zkrBMRgnW9x2eiU4wb9vtDHXrp0efZ%2B9wAjy%2BDqL4_dg%40mail.gmail.com.

Re: git down?

[tooth pik]

git's fine now -- sorry for the noise -- i must have hit him when he was
busy with something important

On Thu, Sep 22, 2022 at 10:55 PM Dominique Pellé 
wrote:

> tooth pik  wrote:
>
> > is git having problems?  i entered 'git pull' and i'm still waiting...
>
> "git pull" works fine for me.  What does "git remote -v" say?
>
> Dominique
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/CAON-T_jf_zj8iEGEZBDsH-jMaFoxWn_vWzMi8o47npnPtKXXzQ%40mail.gmail.com
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1yfiGiAvDX3bF8AL7TPk-oQm%2Bt83g2kKraGOwYfkHjJZQ%40mail.gmail.com.

git down?

[tooth pik]

is git having problems?  i entered 'git pull' and i'm still waiting...

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1x6zYOG_8dnoq1TvjS3O0%2Bs3FPxRZJ1oBbqGMvNwU7rVA%40mail.gmail.com.

Re: 9.0.0475 segfaults while compiling vim9script

[tooth pik]

well i downloaded the latest patches, did a 'make clean', and presto, no
more seg faults

i know i don't say this enough, but thanks bram


On Fri, Sep 16, 2022 at 6:29 AM Bram Moolenaar  wrote:

>
> Marius Gedminas wrote:
>
> > On Fri, Sep 16, 2022 at 01:09:32PM +0300, Marius Gedminas wrote:
> > > On Fri, Sep 16, 2022 at 01:07:06PM +0300, Marius Gedminas wrote:
> > > > vim 9.0.0475 segfauls whenever I try to edit a file, including a
> > > > nonexistent file (e.g. vim newfile.txt).
> > >
> > > git bisect blames
> > >
> > > commit b46c083a5ed9e0c4ac5f3aec577946dcbe8c9dc5
> > > Author: Bram Moolenaar 
> > > Date:   Thu Sep 15 17:19:37 2022 +0100
> > >
> > > patch 9.0.0470: in :def function all closures in loop get the same
> variables
> >
> > The segfault went away when I did a full rebuild after git clean -dfx.
> >
> > Weird.  Perhaps some data structure layout changed and the Makefile
> > didn't have the correct dependencies to rebuild everything affected?
>
> I think, based on the stack trace and what changed, that the dependency
> of vim9type.c on vim9.h is missing.  The dependencies are not 100%
> complete to avoid rebuilding everything on the smallest change.
> It does mean that a "make clean" may be needed once in a while.
>
> --
> From "know your smileys":
>  :-HIs missing teeth
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/20220916112942.4203A1C0846%40moolenaar.net
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zXSzBpHGTSreY_Pqyx2viD019b6AVFAvSmfHBg-xKnAw%40mail.gmail.com.

need to back out updates

[tooth pik]

please -- i need a working editor

the last version of vim i had that worked was Patch 9.0.0469 -- updates to
9.0.0475 leave me with a vim that bombs so bad it breaks the X11/KDE/bash
shell it's running in

can someone tell me the git commands to back my source level to 9.0.0469 so
i can have an editor that works?

thx in advance

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xmE8t-nob10OczezbLq0bnE3RU6JvDYra12wD26GovmA%40mail.gmail.com.

caught deadly signal SEGV

[tooth pik]

i tried a myconfig but it still bombs immediately -- both vim and gvim

this is on Patch 9.0.0475

openSUSE Leap 15.3

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xdWj8EM%2BVzn%3DsAM-9WL-wZ0TMzR0Sa%2BHi8B3aHETVQjQ%40mail.gmail.com.

Re: Zero cmdheight

[tooth pik]

if we're voting put me down on the side of less work, less complicated code

i tried a zero cmdheight and immediately didn't like it

On Mon, Aug 29, 2022 at 5:24 AM Bram Moolenaar  wrote:

>
> It takes a lot of effort to make zero 'cmdheight' work properly.
> Various bugs and corner cases keep popping up.
>
> I added the message window, so that various informative messages do not
> get lost, and that helps.  But it also makes it more complicated.
>
> There is also one bug that I don't know how to reproduce yet, which
> makes the window frames too tall.  The last statusline goes missing.
>
> So, I was wondering who will actually want to use this?  It gives you a
> line of extra space, at the cost of various side effects.  Especially
> the last status line jumping up when typing ":" or "/".  Is this worth
> the extra work and making the code more complicated?
>
>
> --
> Wi n0t trei a h0liday in Sweden thi yer?
>  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES
> LTD
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/20220829102404.A8A9B1C0907%40moolenaar.net
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1yN%2BBbQJiKD1HRic_CCio6xuwWRp79meVqkO%3DB25nJhxg%40mail.gmail.com.

Re: can't build w/o stropts.h

[tooth pik]

that was it, james, thx

On Tue, Aug 16, 2022 at 4:15 PM James McCoy  wrote:

> On Tue, Aug 16, 2022 at 02:28:29PM -0500, tooth pik wrote:
> > i just upgraded my opensuse and am struggling to get the proper nvidia
> driver
> > installed -- doo dah
> >
> > i can't tell if my inability to build vim (no such file stropts.h) is
> because
> > of my upgrade or a problem with patch 9.0.0220, the first patch where
> problems
> > ensued
> >
> > struggling...
>
> The build only tries to use stropts.h if configure detected that the
> file exists.  Maybe it existed before your upgrade and no longer does,
> so you need to re-configure the Vim build.  Try "make reconfig".
>
> Cheers,
> --
> James
> GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/20220816211545.jzleujp35eosmnyj%40localhost
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zKoihVTO%2BRSPZxxM4sD4xPwFSnOjj7vq17xFHaesvc7w%40mail.gmail.com.

can't build w/o stropts.h

[tooth pik]

i just upgraded my opensuse and am struggling to get the proper nvidia
driver installed -- doo dah

i can't tell if my inability to build vim (no such file stropts.h) is
because of my upgrade or a problem with patch 9.0.0220, the first patch
where problems ensued

struggling...

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wJjt1BADVFg-ZwLawyXMNS%2B0c-U4hd6C85MqMZHKwXGw%40mail.gmail.com.

Re: Patch 9.0.0220

[tooth pik]

no such file stropts.h

On Tue, Aug 16, 2022 at 11:51 AM Bram Moolenaar  wrote:

>
> Patch 9.0.0220
> Problem:Invalid memory access with for loop over NULL string.
> Solution:   Make sure mb_ptr2len() consistently returns zero for NUL.
> Files:  src/globals.h, src/mbyte.c, src/testdir/test_eval_stuff.vim
>
>
> *** ../vim-9.0.0219/src/globals.h   2022-07-31 11:37:16.447058514 +0100
> --- src/globals.h   2022-08-16 17:47:21.316417137 +0100
> ***
> *** 1035,1041 
>* (DBCS).
>* The value is set in mb_init();
>*/
> ! // length of char in bytes, including following composing chars
>   EXTERN int (*mb_ptr2len)(char_u *p) INIT(= latin_ptr2len);
>
>   // idem, with limit on string length
> --- 1035,1042 
>* (DBCS).
>* The value is set in mb_init();
>*/
> ! // Length of char in bytes, including any following composing chars.
> ! // NUL has length zero.
>   EXTERN int (*mb_ptr2len)(char_u *p) INIT(= latin_ptr2len);
>
>   // idem, with limit on string length
> *** ../vim-9.0.0219/src/mbyte.c 2022-08-09 12:53:09.907689958 +0100
> --- src/mbyte.c 2022-08-16 17:49:02.276073146 +0100
> ***
> *** 1077,1100 
>   }
>
>   /*
> !  * mb_ptr2len() function pointer.
> !  * Get byte length of character at "*p" but stop at a NUL.
> !  * For UTF-8 this includes following composing characters.
> !  * Returns 0 when *p is NUL.
>*/
>   int
>   latin_ptr2len(char_u *p)
>   {
> !  return MB_BYTE2LEN(*p);
>   }
>
>   static int
> ! dbcs_ptr2len(
> ! char_u*p)
>   {
>   int   len;
>
> ! // Check if second byte is not missing.
>   len = MB_BYTE2LEN(*p);
>   if (len == 2 && p[1] == NUL)
> len = 1;
> --- 1077,1104 
>   }
>
>   /*
> !  * Get byte length of character at "*p".  Returns zero when "*p" is NUL.
> !  * Used for mb_ptr2len() when 'encoding' latin.
>*/
>   int
>   latin_ptr2len(char_u *p)
>   {
> ! return *p == NUL ? 0 : 1;
>   }
>
> + /*
> +  * Get byte length of character at "*p".  Returns zero when "*p" is NUL.
> +  * Used for mb_ptr2len() when 'encoding' DBCS.
> +  */
>   static int
> ! dbcs_ptr2len(char_u *p)
>   {
>   int   len;
>
> ! if (*p == NUL)
> !   return 0;
> !
> ! // if the second byte is missing the length is 1
>   len = MB_BYTE2LEN(*p);
>   if (len == 2 && p[1] == NUL)
> len = 1;
> ***
> *** 2105,2110 
> --- 2109,2115 
>   /*
>* Return the number of bytes the UTF-8 encoding of the character at "p"
> takes.
>* This includes following composing characters.
> +  * Returns zero for NUL.
>*/
>   int
>   utfc_ptr2len(char_u *p)
> *** ../vim-9.0.0219/src/testdir/test_eval_stuff.vim 2022-07-29
> 15:28:24.019397903 +0100
> --- src/testdir/test_eval_stuff.vim 2022-08-16 17:36:39.882781721 +0100
> ***
> *** 75,80 
> --- 75,92 
> redraw
>   endfunc
>
> + func Test_for_over_null_string()
> +   let save_enc = 
> +   set enc=iso8859
> +   let cnt = 0
> +   for c in test_null_string()
> + let cnt += 1
> +   endfor
> +   call assert_equal(0, cnt)
> +
> +   let  = save_enc
> + endfunc
> +
>   func Test_readfile_binary()
> new
> call setline(1, ['one', 'two', 'three'])
> *** ../vim-9.0.0219/src/version.c   2022-08-16 16:09:53.599527502 +0100
> --- src/version.c   2022-08-16 17:21:58.235446605 +0100
> ***
> *** 737,738 
> --- 737,740 
>   {   /* Add new patch number below this line */
> + /**/
> + 220,
>   /**/
>
> --
> Witches prefer brooms: vacuum-cleaners need extension cords!
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/20220816165145.626211C0739%40moolenaar.net
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

warnings from the compiler

[tooth pik]

am i supposed to be getting (and ignoring?) a warning on make
that _FORIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xDRHDa_bEgj_2sL1yyem9vaUSGAWybAVw532X8Q-H27Q%40mail.gmail.com.

Re: 3605 installs as 3604

[tooth pik]

Thanks for all you do! you're the man!

On Tue, Nov 16, 2021 at 12:05 PM Bram Moolenaar  wrote:

>
> > did something get mis-labelled?
>
> Somehow the change to version.c didn't get included.
> Corrected that now.
>
>
> --
> BLACK KNIGHT:  I move for no man.
> ARTHUR:So be it!
> [hah] [parry thrust]
> [ARTHUR chops the BLACK KNIGHT's left arm off]
> ARTHUR:Now stand aside, worthy adversary.
> BLACK KNIGHT:  'Tis but a scratch.
>   The Quest for the Holy Grail (Monty
> Python)
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1yEe1Jfs8AcghjHsB8ZNSqw56UbpzqUdLnPbWLAjjwgGw%40mail.gmail.com.

3605 installs as 3604

[tooth pik]

did something get mis-labelled?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xXOhMgiJshr4gRwNDyYXzac61n32wJ7agCRB0%3Dup67aw%40mail.gmail.com.

Re: Vim code coverage is now above 90%

[tooth pik]

i somehow let World Gin Day slip by unacknowledged and uncelebrated

perhaps now's a good time to work on rectifying that

i raise my [martini] glass to all who contribute, all who slavishly test all
who use and appreciate -- to everyone, thank you

On Wed, Jun 23, 2021 at 9:00 PM Yegappan Lakshmanan 
wrote:

> Hi all,
>
> After patch 8.2.3040 (and several years of development), the
> Vim code  coverage is now above 90%:
>
>
> https://codecov.io/gh/vim/vim/commit/d415d269130b233c0f198c75cc159bee721aa55c/
>
> Some statistics:
> 121 out of the 130 source files have greater than 80% code coverage.
> 87 source files have greater than 90% code coverage.
> 151,090 lines out of 167,830 lines are now covered by tests.
> 3700 test functions and 23042 asserts are used.
>
> Regards,
> Yegappan
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3DAP%2BqJ_nstj5Mm0KEgmBh9EQavkEQHiap-q7a7fD%3DeRA%40mail.gmail.com
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1x2vr_MtDyt6RMWUgQDQFUbzGbCjrm0KnDuvSHKjaccqA%40mail.gmail.com.

Re: Patch 8.2.2759

[tooth pik]

i can't build after pulling this patch

On Tue, Apr 13, 2021 at 1:54 PM Bram Moolenaar  wrote:

>
> Patch 8.2.2759
> Problem:Vim9: for loop infers type of loop variable.
> Solution:   Do not get the member type. (closes #8102)
> Files:  src/vim9type.c, src/proto/vim9type.pro, src/list.c,
> src/vim9script.c, src/proto/vim9script.pro, src/vim.h,
> src/testdir/test_vim9_script.vim
>
>
> *** ../vim-8.2.2758/src/vim9type.c  2021-03-18 22:15:00.589208304 +0100
> --- src/vim9type.c  2021-04-13 20:37:54.449383083 +0200
> ***
> *** 252,260 
>   /*
>* Get a type_T for a typval_T.
>* "type_gap" is used to temporarily create types in.
>*/
>   static type_T *
> ! typval2type_int(typval_T *tv, int copyID, garray_T *type_gap)
>   {
>   type_T  *type;
>   type_T  *member_type = _any;
> --- 252,261 
>   /*
>* Get a type_T for a typval_T.
>* "type_gap" is used to temporarily create types in.
> +  * When "do_member" is TRUE also get the member type, otherwise use
> "any".
>*/
>   static type_T *
> ! typval2type_int(typval_T *tv, int copyID, garray_T *type_gap, int
> do_member)
>   {
>   type_T  *type;
>   type_T  *member_type = _any;
> ***
> *** 274,279 
> --- 275,282 
>
> if (l == NULL || l->lv_first == NULL)
> return _list_empty;
> +   if (!do_member)
> +   return _list_any;
> if (l->lv_first == _list_item)
> return _list_number;
> if (l->lv_copyID == copyID)
> ***
> *** 282,290 
> l->lv_copyID = copyID;
>
> // Use the common type of all members.
> !   member_type = typval2type(>lv_first->li_tv, copyID, type_gap);
> for (li = l->lv_first->li_next; li != NULL; li = li->li_next)
> !   common_type(typval2type(>li_tv, copyID, type_gap),
>   member_type, _type,
> type_gap);
> return get_list_type(member_type, type_gap);
>   }
> --- 285,293 
> l->lv_copyID = copyID;
>
> // Use the common type of all members.
> !   member_type = typval2type(>lv_first->li_tv, copyID, type_gap,
> TRUE);
> for (li = l->lv_first->li_next; li != NULL; li = li->li_next)
> !   common_type(typval2type(>li_tv, copyID, type_gap, TRUE),
>   member_type, _type,
> type_gap);
> return get_list_type(member_type, type_gap);
>   }
> ***
> *** 297,302 
> --- 300,307 
>
> if (d == NULL || d->dv_hashtab.ht_used == 0)
> return _dict_empty;
> +   if (!do_member)
> +   return _dict_any;
> if (d->dv_copyID == copyID)
> // avoid recursion
> return _dict_any;
> ***
> *** 305,313 
> // Use the common type of all values.
> dict_iterate_start(tv, );
> dict_iterate_next(, );
> !   member_type = typval2type(value, copyID, type_gap);
> while (dict_iterate_next(, ) != NULL)
> !   common_type(typval2type(value, copyID, type_gap),
>   member_type, _type,
> type_gap);
> return get_dict_type(member_type, type_gap);
>   }
> --- 310,318 
> // Use the common type of all values.
> dict_iterate_start(tv, );
> dict_iterate_next(, );
> !   member_type = typval2type(value, copyID, type_gap, TRUE);
> while (dict_iterate_next(, ) != NULL)
> !   common_type(typval2type(value, copyID, type_gap, TRUE),
>   member_type, _type,
> type_gap);
> return get_dict_type(member_type, type_gap);
>   }
> ***
> *** 378,388 
>   /*
>* Get a type_T for a typval_T.
>* "type_list" is used to temporarily create types in.
>*/
>   type_T *
> ! typval2type(typval_T *tv, int copyID, garray_T *type_gap)
>   {
> ! type_T *type = typval2type_int(tv, copyID, type_gap);
>
>   if (type != NULL && type != _bool
> && (tv->v_type == VAR_NUMBER
> --- 383,394 
>   /*
>* Get a type_T for a typval_T.
>* "type_list" is used to temporarily create types in.
> +  * When "do_member" is TRUE also get the member type, otherwise use
> "any".
>*/
>   type_T *
> ! typval2type(typval_T *tv, int copyID, garray_T *type_gap, int do_member)
>   {
> ! type_T *type = typval2type_int(tv, copyID, type_gap, do_member);
>
>   if (type != NULL && type != _bool
> && (tv->v_type == VAR_NUMBER
> ***
> *** 404,410 
> return _list_string;
>   if (tv->v_type == VAR_DICT)  // e.g. for v:completed_item
> return _dict_any;
> ! return typval2type(tv, get_copyID(), type_gap);
>   }
>
>   int
> --- 410,416 
> return _list_string;
>   if (tv->v_type == VAR_DICT)  // e.g. for v:completed_item
> return _dict_any;
> ! return 

Re: [vim/vim] Force help to open in current window. (#7534)

[tooth pik]

why not do something simple like

command! -nargs=+ H execute "silent help " | only

in your vimrc?

On Sat, Dec 26, 2020 at 10:22 AM lacygoill 
wrote:

> For me, it doesn't seem to work; that is, I still get two windows instead
> of one, because :h still splits the current window, even when the latter
> displays a help file. Maybe I'm missing some option though.
>
> Is there a way to automate that?
>
> Try this:
>
> au CmdlineLeave : if getcmdline() =~# '^h\%[elp]\s' | exe 'e ' ..  | 
> endif
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> , or
> unsubscribe
> 
> .
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/7534/751371195%40github.com
> 
> .
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zo1FE%2BidnT7OJCS0%2BGm8ZxRG9szLj0tzDR1PK9kGoJmw%40mail.gmail.com.

GTimeVal warning

[tooth pik]

is anyone else getting these when they build?
[image: image.png]

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1wDcxz-o9hCCPf20G_cmMVhhdgUiUWrDmCDKnFSUdYY3g%40mail.gmail.com.

Re: Patch 8.2.0910

[tooth pik]

was there supposed to be a version update here?

On Fri, Jun 5, 2020 at 4:17 PM Bram Moolenaar  wrote:
>
>
> Patch 8.2.0910
> Problem:Vim is not reproducibly buildable.
> Solution:   Use the $SOURCE_DATE_EPOCH environment variable in configure.
> (James McCoy, closes #513)  Give a warning about using it.
> Files:  src/config.h.in, src/config.mk.in, src/configure.ac,
> src/auto/configure, src/version.c, src/Makefile
>
>
> *** ../vim-8.2.0909/src/config.h.in 2020-05-07 18:37:00.124512605 +0200
> --- src/config.h.in 2020-06-05 22:48:47.863212338 +0200
> ***
> *** 30,35 
> --- 30,38 
>   /* Define when __DATE__ " " __TIME__ can be used */
>   #undef HAVE_DATE_TIME
>
> + /* Defined from $SOURCE_DATE_EPOCH, used as the build date */
> + #undef BUILD_DATE
> +
>   /* Define when __attribute__((unused)) can be used */
>   #undef HAVE_ATTRIBUTE_UNUSED
>
> *** ../vim-8.2.0909/src/config.mk.in2019-11-21 17:03:28.0 +0100
> --- src/config.mk.in2020-06-05 22:53:31.026107842 +0200
> ***
> *** 169,174 
> --- 169,178 
>   MSGFMT= @MSGFMT@
>   MSGFMT_DESKTOP= @MSGFMT_DESKTOP@
>
> + ### set if $SOURCE_DATE_EPOCH was set when running configure
> + BUILD_DATE_MSG= @BUILD_DATE_MSG@
> +
> +
>   # Make sure that "make first" will run "make all" once configure has done 
> its
>   # work.  This is needed when using the Makefile in the top directory.
>   first: all
> *** ../vim-8.2.0909/src/configure.ac2020-05-30 18:14:37.824521074 +0200
> --- src/configure.ac2020-06-05 23:14:42.985737574 +0200
> ***
> *** 62,67 
> --- 62,79 
> fi
>   fi
>
> + dnl If $SOURCE_DATE_EPOCH is present in the environment, use that as the
> + dnl "compiled" timestamp in :version's output.  Attempt to get the formatted
> + dnl date using GNU date syntax, BSD date syntax, and finally falling back to
> + dnl just using the current time.
> + if test -n "$SOURCE_DATE_EPOCH"; then
> +   DATE_FMT="%b %d %Y %H:%M:%S"
> +   BUILD_DATE=$(LC_ALL=C date -u -d "@$SOURCE_DATE_EPOCH" "+$DATE_FMT" 
> 2>/dev/null || LC_ALL=C date -u -r "$SOURCE_DATE_EPOCH" "+$DATE_FMT" 
> 2>/dev/null || LC_ALL=C date -u "+$DATE_FMT")
> +   AC_DEFINE_UNQUOTED(BUILD_DATE, ["$BUILD_DATE"])
> +   BUILD_DATE_MSG=-"echo -e 
> '=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\nNOTE: 
> build date/time is fixed: 
> $BUILD_DATE\n=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-='"
> +   AC_SUBST(BUILD_DATE_MSG)
> + fi
> +
>   dnl Check for the flag that fails if stuff are missing.
>
>   AC_MSG_CHECKING(--enable-fail-if-missing argument)
> *** ../vim-8.2.0909/src/auto/configure  2020-05-30 18:14:37.824521074 +0200
> --- src/auto/configure  2020-06-05 23:14:48.093721505 +0200
> ***
> *** 721,726 
> --- 721,727 
>   XCODE_SELECT
>   CPP_MM
>   CROSS_COMPILING
> + BUILD_DATE_MSG
>   STRIP
>   AWK
>   FGREP
> ***
> *** 4455,4460 
> --- 4456,4472 
> fi
>   fi
>
> + if test -n "$SOURCE_DATE_EPOCH"; then
> +   DATE_FMT="%b %d %Y %H:%M:%S"
> +   BUILD_DATE=$(LC_ALL=C date -u -d "@$SOURCE_DATE_EPOCH" "+$DATE_FMT" 
> 2>/dev/null || LC_ALL=C date -u -r "$SOURCE_DATE_EPOCH" "+$DATE_FMT" 
> 2>/dev/null || LC_ALL=C date -u "+$DATE_FMT")
> +   cat >>confdefs.h <<_ACEOF
> + #define BUILD_DATE "$BUILD_DATE"
> + _ACEOF
> +
> +   BUILD_DATE_MSG=-"echo -e 
> '=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\nNOTE: 
> build date/time is fixed: 
> $BUILD_DATE\n=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-='"
> +
> + fi
> +
>
>   { $as_echo "$as_me:${as_lineno-$LINENO}: checking --enable-fail-if-missing 
> argument" >&5
>   $as_echo_n "checking --enable-fail-if-missing argument... " >&6; }
> *** ../vim-8.2.0909/src/version.c   2020-06-05 22:33:38.409658754 +0200
> --- src/version.c   2020-06-05 22:45:50.531697794 +0200
> ***
> *** 44,52 
> --- 44,56 
>* VAX C can't concatenate strings in the preprocessor.
>*/
>   strcpy(longVersion, VIM_VERSION_LONG_DATE);
> + #ifdef BUILD_DATE
> + strcat(longVersion, BUILD_DATE);
> + #else
>   strcat(longVersion, __DATE__);
>   strcat(longVersion, " ");
>   strcat(longVersion, __TIME__);
> + #endif
>   strcat(longVersion, ")");
>   }
>
> ***
> *** 56,62 
> --- 60,70 
>   {
>   if (longVersion == NULL)
>   {
> + #ifdef BUILD_DATE
> +   char *date_time = BUILD_DATE;
> + #else
> char *date_time = __DATE__ " " __TIME__;
> + #endif
> char *msg = _("%s (%s, compiled %s)");
> size_t len = strlen(msg)
> + strlen(VIM_VERSION_LONG_ONLY)
> *** ../vim-8.2.0909/src/Makefile2020-06-02 20:25:33.164477793 +0200
> --- src/Makefile2020-06-05 23:03:33.035904816 +0200
> ***
> *** 2130,2135 
> --- 2130,2136 
>   # A shell script is used to try linking without 

latest build

[tooth pik]

i'm having trouble linking:  getting an undefined reference to
veryfast_breakcheck in vim9execute

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1z-Bi6csr-cw671Pwx0OF0knZbJQEkq7oejfjSHSYAKUg%40mail.gmail.com.

Re: Patch 8.1.2187

[tooth pik]

i can't build after applying this patch:

cmdexpand.c: In function ‘ExpandFromContext’:
cmdexpand.c:1979:19: error: ‘WILD_NOERROR’ undeclared (first use in
this function); did you mean ‘FIND_NOERROR’?
 if (options & WILD_NOERROR)
   ^~~~
   FIND_NOERROR
cmdexpand.c:1979:19: note: each undeclared identifier is reported only
once for each function it appears in

On Sat, Oct 19, 2019 at 2:01 PM Bram Moolenaar  wrote:
>
>
> Patch 8.1.2187
> Problem:Error for bad regexp even though regexp is not used when writing
> a file. (Arseny Nasokin)
> Solution:   Ignore regexp errors. (closes #5059)
> Files:  src/cmdexpand.c, src/ex_docmd.c, src/testdir/test_writefile.vim
>
>
> *** ../vim-8.1.2186/src/cmdexpand.c 2019-08-25 15:40:39.658739525 +0200
> --- src/cmdexpand.c 2019-10-19 20:45:12.123133046 +0200
> ***
> *** 1976,1981 
> --- 1976,1983 
> flags |= EW_KEEPALL;
>   if (options & WILD_SILENT)
> flags |= EW_SILENT;
> + if (options & WILD_NOERROR)
> +   flags |= EW_NOERROR;
>   if (options & WILD_ALLLINKS)
> flags |= EW_ALLLINKS;
>
> *** ../vim-8.1.2186/src/ex_docmd.c  2019-10-18 20:53:30.697741631 +0200
> --- src/ex_docmd.c  2019-10-19 20:53:43.044943051 +0200
> ***
> *** 4211,4217 
> else /* n == 2 */
> {
> expand_Txpc;
> !   int options = WILD_LIST_NOTFOUND|WILD_ADD_SLASH;
>
> ExpandInit();
> xpc.xp_context = EXPAND_FILES;
> --- 4211,4218 
> else /* n == 2 */
> {
> expand_Txpc;
> !   int options = WILD_LIST_NOTFOUND
> !  | WILD_NOERROR | 
> WILD_ADD_SLASH;
>
> ExpandInit();
> xpc.xp_context = EXPAND_FILES;
> *** ../vim-8.1.2186/src/testdir/test_writefile.vim  2019-05-31 
> 20:42:04.690287097 +0200
> --- src/testdir/test_writefile.vim  2019-10-19 20:53:13.793051153 +0200
> ***
> *** 1,4 
> ! " Tests for the writefile() function.
>
>   func Test_writefile()
> let f = tempname()
> --- 1,4 
> ! " Tests for the writefile() function and some :write commands.
>
>   func Test_writefile()
> let f = tempname()
> ***
> *** 16,21 
> --- 16,26 
> call delete(f)
>   endfunc
>
> + func Test_writefile_ignore_regexp_error()
> +   write Xt[z-a]est.txt
> +   call delete('Xt[z-a]est.txt')
> + endfunc
> +
>   func Test_writefile_fails_gently()
> call assert_fails('call writefile(["test"], "Xfile", [])', 'E730:')
> call assert_false(filereadable("Xfile"))
> *** ../vim-8.1.2186/src/version.c   2019-10-19 20:57:24.956093733 +0200
> --- src/version.c   2019-10-19 21:00:05.991452059 +0200
> ***
> *** 743,744 
> --- 743,746 
>   {   /* Add new patch number below this line */
> + /**/
> + 2187,
>   /**/
>
> --
> Kiss me twice.  I'm schizophrenic.
>
>  /// Bram Moolenaar -- b...@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_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/201910191901.x9JJ1bir011399%40masaka.moolenaar.net.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zSU4eJAXzk_EO214DffG1E%3D-vHShu%3D6Qx7WKdvFi56mA%40mail.gmail.com.

Re: hampered scrolling behavior

[tooth pik]

that's good information, thank you -- i didn't think the scroll
behavior used to be affected
by normal/insert mode (7.3.475 was current mar-16 of 2012)

my inference is that some overhead has been added to the 
function that temporarily
escapes from insert mode and then returns after whatever you've asked
it to do is done

On Mon, Jul 29, 2019 at 1:01 AM Sihera Andre  wrote:
>
> On 29/07/19 04:02, tooth pik wrote:
> > i love and use the CTRL-E and CTRL-Y scrolling commands so much i have
> > them mapped to F10 and F11 in my ~/.vimrc:
> >
> > nnoremap  
> > inoremap  
> > nnoremap  
> > inoremap  
> >
> > just today i noticed both up and down are impeded if i happen to be in
> > insert mode when i use them, going slower and in a jerky manner --
> > they both scroll beautifully when in normal mode
> >
> > i wouldn't define this as a "problem," but a minor annoyance -- has
> > anyone else noticed the same?
> >
> Hi,
>
> I'm using version 7.3.475 and there appears to be no problem here.
> With your key mappings, scrolling is equally responsive both in Insert
> mode and Normal mode.
>
> Is it just C-E/C-Y? Or maybe it is it all cursor movement and you just
> haven't noticed? Cursor movements appear to be written to the swap
> file so slowed access to the swap file (e.g., when editing over NFS)
> would cause a kind of sluggishness similar to what you appear to be
> experiencing.
>
> Cheers,
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/PSXP216MB0629550EF93B3E81A31639CEC0DD0%40PSXP216MB0629.KORP216.PROD.OUTLOOK.COM.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xe6MJf-ezX7P84EBbSgzri6eTsLtLXtKFoR9mXQM2%2BUg%40mail.gmail.com.

hampered scrolling behavior

[tooth pik]

i love and use the CTRL-E and CTRL-Y scrolling commands so much i have
them mapped to F10 and F11 in my ~/.vimrc:

nnoremap  
inoremap  
nnoremap  
inoremap  

just today i noticed both up and down are impeded if i happen to be in
insert mode when i use them, going slower and in a jerky manner --
they both scroll beautifully when in normal mode

i wouldn't define this as a "problem," but a minor annoyance -- has
anyone else noticed the same?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zJP1-hzjKN5V96NuVRAwvMe1j0rvy4Di7VUVTDgOtxCA%40mail.gmail.com.

Re: Patch 8.1.1748

[tooth pik]

i wish you'd test :version after messing with version.c -- it is still
horked when you
execute a :ver inside a running vim instance -- it looks fine when you
run vim --version
on the command line so it's better than it was

On Thu, Jul 25, 2019 at 2:53 PM Bram Moolenaar  wrote:
>
>
> Patch 8.1.1748 (after 8.1.1737)
> Problem::args output is not aligned.
> Solution:   Output a line break after the last item in a row.
> Files:  src/version.c
>
>
> *** ../vim-8.1.1747/src/version.c   2019-07-25 20:52:59.780237300 +0200
> --- src/version.c   2019-07-25 21:50:26.887673097 +0200
> ***
> *** 4440,4445 
> --- 4442,4454 
> msg_putchar(' ');
> }
> }
> +   else
> +   {
> +   // this row is out of items, thus at the end of the row
> +   if (msg_col > 0 && cur_row < nrow)
> +   msg_putchar('\n');
> +   ++cur_row;
> +   }
>   }
>   }
>
> *** ../vim-8.1.1747/src/version.c   2019-07-25 20:52:59.780237300 +0200
> --- src/version.c   2019-07-25 21:50:26.887673097 +0200
> ***
> *** 779,780 
> --- 779,782 
>   {   /* Add new patch number below this line */
> + /**/
> + 1748,
>   /**/
>
> --
> OLD WOMAN: King of the WHO?
> ARTHUR:The Britons.
> OLD WOMAN: Who are the Britons?
>  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
>
>  /// Bram Moolenaar -- b...@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_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/201907251952.x6PJqwEo031035%40masaka.moolenaar.net.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1y6F3Ghwu9eK_qy81%2BySTQKEL_D7kGrce8e3VO8otQLvw%40mail.gmail.com.

Re: script stopped working

[tooth pik]

it still hangs for me and requires i kill the vim process

looking at the vim --version output i see the last line of features
has six features, and all
other lines have four -- the last two, +mouse_sgr and -tag_old_static,
would not be at the
end if the features were sorted

i still maintain the --version output is horked

On Wed, Jul 24, 2019 at 6:08 AM Bram Moolenaar  wrote:
>
>
> > i had this cute bash script to display a nicely formatted version in
> > konsole and it
> > just stopped working
> >
> > after the shebang it reads
> >
> > vim --cmd ':version | :q'
> >
> > before today it worked beautifully -- today it hangs and won't release 
> > control
> > until i kill the vim process
>
> Works fine for me.  Try: vim --clean --cmd ':version | :q'
>
> --
> SECOND SOLDIER: It could be carried by an African swallow!
> FIRST SOLDIER:  Oh  yes! An African swallow maybe ... but not a European
> swallow. that's my point.
>  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
>
>  /// Bram Moolenaar -- b...@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_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xMsjWBwmvHEgzx_TsXpnyZLq6AZrSSrnKUbeFm9%3DCgSw%40mail.gmail.com.

version display horked

[tooth pik]

looking at my broken script and wondering why it stopped working i noticed the
version display is bolixed whether i run it inside a vim session or from the
command line

the script i've been playing around with on the side triggers the end
of features
when it encounters a line that matches '^   system' -- that line is
currently appended to the last feature line, which is also horked

is somebody forgetting their newlines?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xDg1dZ-pbPAwHmM%2BO_Oxuv%3D7pSVqSYbYkhUVf6JA26VQ%40mail.gmail.com.

script stopped working

[tooth pik]

i had this cute bash script to display a nicely formatted version in
konsole and it
just stopped working

after the shebang it reads

vim --cmd ':version | :q'

before today it worked beautifully -- today it hangs and won't release control
until i kill the vim process

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1x%2BX5QBEoFRCbGqXnDcTBekUFqExMGyQMLE2iY5RBVRHQ%40mail.gmail.com.

Re: can't pull

[tooth pik]

On Thu, Jun 6, 2019 at 12:04 PM Christian Brabandt  wrote:
> On Do, 06 Jun 2019, tooth pik wrote:
>
> > this morning i get a
> >
> > Updating 32e197701..75ee544f9
> > error: Your local changes to the following files would be overwritten by 
> > merge:
> > src/testdir/test_clientserver.vim
> > Please commit your changes or stash them before you merge.
> > Aborting
> >
> > when i try to git pull
>
> Did you change test_clientserver.vim? Then git stash it away and pull
> again and do git stash pop afterwards. Or do you not care? Then git
> reset --hard before doing git pull

i have a vague recollection of trying to turn logging on to see why my tests
all failed -- no joy -- but i put it back the way it was but maybe git
is checking
time stamps

anyway git reset --hard did the trick for me -- thx christian
> Best,
> Christian
> --
> Nicht die einzelnen Anreden, sondern die zufälligen Äußerungen der
> Eltern und die absichtlose Fortsetzung und Offenbarung eines
> Charakters wirken so unglaublich auf die Kinder, denen durch ihre
> Verehrung alles so fest anfliegt.
> -- Jean Paul
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/20190606170420.GO23877%40256bit.org.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1yUTrkdgn1pDtkPAO3-ya08kP7bKiNWz-5zwhOWZ%3D_CBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

can't pull

[tooth pik]

this morning i get a

Updating 32e197701..75ee544f9
error: Your local changes to the following files would be overwritten by merge:
src/testdir/test_clientserver.vim
Please commit your changes or stash them before you merge.
Aborting

when i try to git pull

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xpiO%2BwHTjbO3PV5Z2C-eq%2BnuDhcWvvBFu3Up%3DF9QZxbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How about sound?

[tooth pik]

my first reaction is "useless cruft" -- sorry

my 2nd is, find the "vim way":  don't build the sound into vim, use an
external voice
synthesizer that vim would send text messages to with informative
error info -- the
user would be left to assign their own voice to whatever synthesizer
they came up
with, leaving it portable in the sense that surely windows and mac can
come up with
(however expensive) their own dang synthesizer that can accept text and speak it

On Tue, Jun 4, 2019 at 8:08 AM Bram Moolenaar  wrote:
>
>
> I have been wondering if it would help if Vim could play a sound.  Think
> of a gentle "ping" to indicate the cursor can't move there, or a
> "tadaa" when a background build finishes successfully.  At least I have
> had times where I didn't notice something that was going on, because I
> was looking in the wrong place.  Currently there only is the annoying
> beep (which I usually have disabled).
>
> I wonder how useful this would be.  It's probably a matter of taste
> anyway. And it only works locally (unless there is an xterm sequence to
> play a sound?).
>
> And I wonder if it can be implemented in a way it's portable.  There are
> some audio libraries floating around, but I don't expect the "-dev"
> version to be installed on most systems.  Perhaps MS-Windows has
> something that's always available?
>
> Another way would be to use a system command (in the background), but
> that could have some latency.
>
> --
> From "know your smileys":
>  ...---...   SOS
>
>  /// Bram Moolenaar -- b...@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_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/201906041307.x54D7s43025572%40masaka.moolenaar.net.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xqGi1QZ-qrvF3dkb7SX9nZT5UQv179YxirQZwC15kOjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Add digraph for horizontal ellipsis (#4472)

[tooth pik]

period -- of course -- sorry for the noise -- senior moment --

On Sun, Jun 2, 2019 at 3:07 PM Tony Mechelynck
 wrote:
>
> On Sun, Jun 2, 2019 at 9:02 PM Gary Johnson  wrote:
> >
> > On 2019-06-02, tooth pik wrote:
> >
> > > what's a full stop again?
> >
> > Full stop is the term in British English for what is a period in
> > American English.  It is the last character in these sentences.
> >
> > Regards,
> > Gary
>
> BTW, the official Unicode name for the codepoint U+002E is FULL STOP
> but the HTML entity for it is   :-D
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/CAJkCKXvBB3w2p0LJy9ARknkUN4Fii3b%2BguF5T9Hfhj47Y8_GZw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1zzC2qHpAoMSsb4nr%2BEtvVXxm3tMsXhHTO3hdFMpuw4aA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Add digraph for horizontal ellipsis (#4472)

[tooth pik]

On Sun, Jun 2, 2019 at 10:00 AM Tony Mechelynck 
wrote:

> There already is one. Be sure to be in Insert mode, then hit Ctrl-K
> followed by a comma then a full stop.
>
> what's a full stop again?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1x6qUws2Lu5dtEr2LVi7Xy7UyqvzCef5-KNrWOChT0SfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

can't build 1430

[tooth pik]

i just git pulled 1430 and it fails to build:

evalfunc.c:816:33: error: ‘f_popup_getposition’ undeclared here (not
in a function)
 {"popup_getposition", 1, 1, f_popup_getposition},
 ^
Makefile:3005: recipe for target 'objects/evalfunc.o' failed
make[1]: *** [objects/evalfunc.o] Error 1
m

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xT%3D06aoJyiekGpQOyLdyRDkoHqi7EP%2B0U5AvD5OV_v9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 8.1.1308

[tooth pik]

i can't git pull this one either -- still with the runtime/vim.desktop
and runtime/gvim.desktop

On Thu, May 9, 2019 at 12:26 PM Bram Moolenaar  wrote:
>
>
> Patch 8.1.1308
> Problem:The Normal highlight is not defined when compiled with GUI.
> Solution:   Always define Normal. (Christian Brabandt, closes #4072)
> Files:  runtime/doc/syntax.txt, src/syntax.c,
> src/testdir/test_highlight.vim
>
>
> *** ../vim-8.1.1307/runtime/doc/syntax.txt  2019-05-05 18:11:46.324590615 
> +0200
> --- runtime/doc/syntax.txt  2019-05-09 19:22:31.109616534 +0200
> ***
> *** 5002,5007 
> --- 5002,5009 
> text (see 'conceallevel')
> *hl-Cursor*
>   Cursorthe character under the cursor
> + lCursor   the character under the cursor when |language-mapping|
> +   is used (see 'guicursor')
> *hl-CursorIM*
>   CursorIM  like Cursor, but used when in IME mode |CursorIM|
> *hl-CursorColumn*
> *** ../vim-8.1.1307/src/syntax.c2019-05-09 15:12:45.180723879 +0200
> --- src/syntax.c2019-05-09 19:22:31.109616534 +0200
> ***
> *** 6865,6870 
> --- 6865,6871 
>   "lCursor guibg=fg guifg=bg", /* should be different, but what? */
>   #endif
>   "default link QuickFixLine Search",
> + CENT("Normal cterm=NONE", "Normal gui=NONE"),
>   NULL
>   };
>
> ***
> *** 6946,6954 
>   #endif
>   CENT("MatchParen term=reverse ctermbg=Cyan",
>  "MatchParen term=reverse ctermbg=Cyan guibg=Cyan"),
> - #ifdef FEAT_GUI
> - "Normal gui=NONE",
> - #endif
>   #ifdef FEAT_TERMINAL
>   CENT("StatusLineTerm term=reverse,bold cterm=bold ctermfg=White 
> ctermbg=DarkGreen",
>  "StatusLineTerm term=reverse,bold cterm=bold ctermfg=White 
> ctermbg=DarkGreen gui=bold guifg=bg guibg=DarkGreen"),
> --- 6947,6952 
> ***
> *** 7042,7050 
>   CENT("Conceal ctermbg=DarkGrey ctermfg=LightGrey",
>  "Conceal ctermbg=DarkGrey ctermfg=LightGrey guibg=DarkGrey 
> guifg=LightGrey"),
>   #endif
> - #ifdef FEAT_GUI
> - "Normal gui=NONE",
> - #endif
>   #ifdef FEAT_TERMINAL
>   CENT("StatusLineTerm term=reverse,bold cterm=bold ctermfg=Black 
> ctermbg=LightGreen",
>  "StatusLineTerm term=reverse,bold cterm=bold ctermfg=Black 
> ctermbg=LightGreen gui=bold guifg=bg guibg=LightGreen"),
> --- 7040,7045 
> *** ../vim-8.1.1307/src/testdir/test_highlight.vim  2019-03-09 
> 11:45:45.650134366 +0100
> --- src/testdir/test_highlight.vim  2019-05-09 19:25:06.884834302 +0200
> ***
> *** 572,574 
> --- 572,581 
> call StopVimInTerminal(buf)
> call delete('Xtest_cursorline_with_visualmode')
>   endfunc
> +
> + func Test_1_highlight_Normalgroup_exists()
> +   " This test must come before the Test_cursorline test, as it appears this
> +   " defines the Normal highlighting group anyway.
> +   let hlNormal = HighlightArgs('Normal')
> +   call assert_match('hi Normal\s*clear', hlNormal)
> + endfunc
> *** ../vim-8.1.1307/src/version.c   2019-05-09 18:59:27.228463605 +0200
> --- src/version.c   2019-05-09 19:25:15.532790358 +0200
> ***
> *** 769,770 
> --- 769,772 
>   {   /* Add new patch number below this line */
> + /**/
> + 1308,
>   /**/
>
> --
> Communication is one of the most compli..., eh, well, it's hard.
> You know what I mean.  Not?
>
>  /// Bram Moolenaar -- b...@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_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/201905091726.x49HQqOb007856%40masaka.moolenaar.net.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: Patch 8.1.1307

[tooth pik]

i get a weird error when i try to git pull this patch

Updating eae1b91fe..a6c27c47d
error: Your local changes to the following files would be overwritten by merge:
runtime/gvim.desktop
runtime/vim.desktop
Please commit your changes or stash them before you merge.
Aborting

On Thu, May 9, 2019 at 11:59 AM Bram Moolenaar  wrote:
>
>
> Patch 8.1.1307
> Problem:Cannot reconnect to the X server after it restarted.
> Solution:   Add the :xrestore command. (Adrian Kocis, closes #844)
> Files:  runtime/doc/index.txt, runtime/doc/various.txt, src/os_unix.c,
> src/proto/os_unix.pro, src/globals.h, src/ex_cmds.h,
> src/ex_cmdidxs.h, src/ex_docmd.c, src/testdir/test_paste.vim
>
>
> *** ../vim-8.1.1306/runtime/doc/index.txt   2019-05-05 18:11:46.316590662 
> +0200
> --- runtime/doc/index.txt   2019-05-09 16:55:09.231912512 +0200
> ***
> *** 1714,1719 
> --- 1714,1720 
>   |:xmapclear|  :xmapc[lear]remove all mappings for Visual mode
>   |:xmap|   :xm[ap] like ":map" but for Visual mode
>   |:xmenu|  :xme[nu]add menu for Visual mode
> + |:xrestore|   :xr[estore] restores the X server connection
>   |:xnoremap|   :xn[oremap] like ":noremap" but for Visual mode
>   |:xnoremenu|  :xnoreme[nu]like ":noremenu" but for Visual mode
>   |:xunmap| :xu[nmap]   like ":unmap" but for Visual mode
> *** ../vim-8.1.1306/runtime/doc/various.txt 2019-05-05 18:11:46.328590595 
> +0200
> --- runtime/doc/various.txt 2019-05-09 16:57:27.375214537 +0200
> ***
> *** 704,709 
> --- 704,724 
> available when compiled with the |+netbeans_intg|
> feature}
>
> +   *:xrestore* *:xr*
> + :xr[estore] [display] Reinitializes the connection to the X11 server. Useful
> +   after the X server restarts, e.g. when running Vim for
> +   long time inside screen/tmux and connecting from
> +   different machines).
> +   [display] should be in the format of the $DISPLAY
> +   environment variable (e.g. "localhost:10.0")
> +   If [display] is omitted, then it reinitializes the
> +   connection to the X11 server using the same value as
> +   was used for the previous execution of this command.
> +   If the value was never specified, then it uses the
> +   value of $DISPLAY environment variable as it was when
> +   Vim was started.
> +   {only available when compiled with the |+clipboard|
> +   feature}
>
> *g_CTRL-A*
>   g CTRL-A  Only when Vim was compiled with MEM_PROFILING defined
> *** ../vim-8.1.1306/src/os_unix.c   2019-05-04 17:34:30.653353882 +0200
> --- src/os_unix.c   2019-05-09 18:51:32.467132185 +0200
> ***
> *** 1659,1664 
> --- 1659,1683 
> get_x11_title(FALSE);
>   }
>   }
> +
> + void
> + ex_xrestore(exarg_T *eap)
> + {
> + if (eap->arg != NULL && STRLEN(eap->arg) > 0)
> + {
> + if (xterm_display_allocated)
> + vim_free(xterm_display);
> + xterm_display = (char *)vim_strsave(eap->arg);
> + xterm_display_allocated = TRUE;
> + }
> + smsg(_("restoring display %s"), xterm_display == NULL
> + ? (char *)mch_getenv("DISPLAY") : 
> xterm_display);
> +
> + clear_xterm_clip();
> + x11_window = 0;
> + xterm_dpy_retry_count = 5;  // Try reconnecting five times
> + may_restore_clipboard();
> + }
>   #endif
>
>   /*
> ***
> *** 1761,1766 
> --- 1780,1789 
> x11_window = (Window)atol(winid);
>
>   #ifdef FEAT_XCLIPBOARD
> + if (xterm_dpy == x11_display)
> +   // x11_display may have been set to xterm_dpy elsewhere
> +   x11_display_from = XD_XTERM;
> +
>   if (xterm_dpy != NULL && x11_window != 0)
>   {
> /* We may have checked it already, but Gnome terminal can move us to
> ***
> *** 7661,7667 
>   return TRUE;
>   }
>
> ! # if defined(FEAT_GUI) || defined(PROTO)
>   /*
>* Destroy the display, window and app_context.  Required for GTK.
>*/
> --- 7684,7690 
>   return TRUE;
>   }
>
> ! # if defined(FEAT_GUI) || defined(FEAT_XCLIPBOARD) || defined(PROTO)
>   /*
>* Destroy the display, window and app_context.  Required for GTK.
>*/
> *** ../vim-8.1.1306/src/proto/os_unix.pro   2019-05-04 17:34:30.653353882 
> +0200
> --- src/proto/os_unix.pro   2019-05-09 17:11:39.922883130 +0200
> ***
> *** 13,18 
> --- 13,19 
>   int vim_handle_signal(int sig);
>   int mch_check_win(int argc, char **argv);
>   int mch_input_isatty(void);

Fwd: more testing questions

[tooth pik]

lordy how i hate googlemail

dunno what i hit but i wasn't done

-- Forwarded message -
From: tooth pik 
Date: Thu, Apr 25, 2019 at 10:50 AM
Subject: Re: more testing questions
To: 


On Thu, Apr 25, 2019 at 9:50 AM Christian Brabandt  wrote:
>
>
> On Do, 25 Apr 2019, tooth pik wrote:
>
> > On Thu, Apr 25, 2019 at 3:48 AM Christian Brabandt  
> > wrote:
> > >
> > >
> > > On Mi, 24 Apr 2019, tooth pik wrote:
> > >
> > > > clipboard is available in xterm, but accessing it is different than in
> > > > konsole -- so
> > > > i tried testing in a konsole and got a different looking mess of
> > > > errors -- i will
> > > > attach that to this email
> > >
> > > Not sure what you mean with "accessing the clipboard in xterm is
> > > different than in konsole". That shouldn't not make a difference from
> > > the X-Server clients perspective. Perhaps, your $DISPLAY variable is not
> > > set? Is vim able to access the clipboard from xterm?
> > >
> > > As for your errors: Again, those are screen dump failures. Please run
> > > the result of the term_dumpdiff() command as indicated in the error
> > > logs.
> >
> > all i can make it tell me is "executing job failed: No such file or 
> > directory"
> >
> > i've tried from the src path as current, the testdir path, and the
> > failed path --
> > i must be missing something very basic and too obvious for me to see
>
> If you look into your output from the test, it says something like
>
> call term_dumpdiff("failed/Test_diff_of_diff_02.dump", 
> "dumps/Test_diff_of_diff_02.dump")
>
> So go into vim/src/testdir directory and fire up vim:
>
> vim -c 'call term_dumpdiff("failed/Test_diff_of_diff_02.dump", 
> "dumps/Test_diff_of_diff_02.dump")|wincmd o'
>
> (adding wincmd o to make it the only window)
>
> now you should see two pictures, at the top, you see the failed screen
> dump and at the bottom, you see the expected screen dump. And in
> between, you see a character indication of what is missing. The help
> talks about it at ':h term_dumpdiff()'
>
> You can try hitting 's' to swap the order. This allows to easily notice
> differences. Try this and see if this helps. You can also try to attach
> a failed dump here, so we can have a look.

i'm starting to worry about my box -- i added everything in the
testdir/failed directory
to the stuff i delete before i test so i could get a clean new test and got

Vim: Caught deadly signal SEGV

in the middle of test_gui.vim

the box isn't locked, but my 'make test' sure is

thank you Christian for your patience with me

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: more testing questions

[tooth pik]

On Thu, Apr 25, 2019 at 9:50 AM Christian Brabandt  wrote:
>
>
> On Do, 25 Apr 2019, tooth pik wrote:
>
> > On Thu, Apr 25, 2019 at 3:48 AM Christian Brabandt  
> > wrote:
> > >
> > >
> > > On Mi, 24 Apr 2019, tooth pik wrote:
> > >
> > > > clipboard is available in xterm, but accessing it is different than in
> > > > konsole -- so
> > > > i tried testing in a konsole and got a different looking mess of
> > > > errors -- i will
> > > > attach that to this email
> > >
> > > Not sure what you mean with "accessing the clipboard in xterm is
> > > different than in konsole". That shouldn't not make a difference from
> > > the X-Server clients perspective. Perhaps, your $DISPLAY variable is not
> > > set? Is vim able to access the clipboard from xterm?
> > >
> > > As for your errors: Again, those are screen dump failures. Please run
> > > the result of the term_dumpdiff() command as indicated in the error
> > > logs.
> >
> > all i can make it tell me is "executing job failed: No such file or 
> > directory"
> >
> > i've tried from the src path as current, the testdir path, and the
> > failed path --
> > i must be missing something very basic and too obvious for me to see
>
> If you look into your output from the test, it says something like
>
> call term_dumpdiff("failed/Test_diff_of_diff_02.dump", 
> "dumps/Test_diff_of_diff_02.dump")
>
> So go into vim/src/testdir directory and fire up vim:
>
> vim -c 'call term_dumpdiff("failed/Test_diff_of_diff_02.dump", 
> "dumps/Test_diff_of_diff_02.dump")|wincmd o'
>
> (adding wincmd o to make it the only window)
>
> now you should see two pictures, at the top, you see the failed screen
> dump and at the bottom, you see the expected screen dump. And in
> between, you see a character indication of what is missing. The help
> talks about it at ':h term_dumpdiff()'
>
> You can try hitting 's' to swap the order. This allows to easily notice
> differences. Try this and see if this helps. You can also try to attach
> a failed dump here, so we can have a look.

i'm starting to worry about my box -- i added everything in the
testdir/failed directory
to the stuff i delete before i test so i could get a clean new test and got

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: more testing questions

[tooth pik]

On Thu, Apr 25, 2019 at 3:48 AM Christian Brabandt  wrote:
>
>
> On Mi, 24 Apr 2019, tooth pik wrote:
>
> > clipboard is available in xterm, but accessing it is different than in
> > konsole -- so
> > i tried testing in a konsole and got a different looking mess of
> > errors -- i will
> > attach that to this email
>
> Not sure what you mean with "accessing the clipboard in xterm is
> different than in konsole". That shouldn't not make a difference from
> the X-Server clients perspective. Perhaps, your $DISPLAY variable is not
> set? Is vim able to access the clipboard from xterm?
>
> As for your errors: Again, those are screen dump failures. Please run
> the result of the term_dumpdiff() command as indicated in the error
> logs.

all i can make it tell me is "executing job failed: No such file or directory"

i've tried from the src path as current, the testdir path, and the
failed path --
i must be missing something very basic and too obvious for me to see

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: more testing questions

[tooth pik]

On Wed, Apr 24, 2019 at 1:52 AM Christian Brabandt  wrote:
>
>
> On Di, 23 Apr 2019, tooth pik wrote:
>
> > it occurs to me to ask if testing is supposed to succeed if you run it
> > in its own xterm --
> > i do that so as not to mess up any of my konsole tabs
> >
> > my xterm reports it is version X.Org 7.7.0(308) which is current for
> > my opensuse Leap 4.3
> >
> > nothing else was running from vim (except a gvim with a hidden buffer
> > displaying a calendar) so "parallel" shouldn't be relevant
> >
> > it failed several ways this time, none i think the same as the last
> > time -- i will attach a paste from the failures...
>
> You got one failure when testing the clipboard support. I guess your vim
> is not able to connect to your X11 system or something like that.

clipboard is available in xterm, but accessing it is different than in
konsole -- so
i tried testing in a konsole and got a different looking mess of
errors -- i will
attach that to this email

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


testfailure2
Description: Binary data

more testing questions

[tooth pik]

it occurs to me to ask if testing is supposed to succeed if you run it
in its own xterm --
i do that so as not to mess up any of my konsole tabs

my xterm reports it is version X.Org 7.7.0(308) which is current for
my opensuse Leap 4.3

nothing else was running from vim (except a gvim with a hidden buffer
displaying a calendar) so "parallel" shouldn't be relevant

it failed several ways this time, none i think the same as the last
time -- i will attach a paste from the failures...

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


testfailure
Description: Binary data

idle question about testing

[tooth pik]

is "make test" supposed to work currently?  i can't remember the last
time i didn't
get a failed somethingorother from it

this time it's errors in Test_incsearch_substitute_dump()

i don't run make test very often so I'm curious -- are tests supposed
to succeed?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Add a signal allowing a (remote) graceful shutdown of [g]vim in the absence of any unsaved changes (#4162)

[tooth pik]

why signal?

start your vim instance with the --servername option -- when you want
it to quit you can use the
vim --servername  --remote-send {cmd} to send a quit which
will issue an error if
there are unsaved changes -- or the sky's the limit if you write a
function to be called with a
--remote-send

On Sun, Mar 24, 2019 at 2:03 PM Tormen  wrote:
>
> I am opting to add the possibility to send some signal (does not need to be 
> SIGINT),
> that detects if there are unsaved changes ?
>
> without unsaved-changes: it gracefully shuts down gvim (e.g. behaves like a 
> :q, so it quits vim and removes the swapfile)
> with unsaved-chages: it stops and displays the message: that currently is 
> displayed when a SIGINT is received:
> Type :qa! and press  to abandon all changes and exit Vim
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: modeline stopped working

[tooth pik]

i've been staring at that all morning and didn't see that -- thx gary
i owe you a beer

On Fri, Mar 15, 2019 at 2:19 PM Gary Johnson  wrote:
>
> On 2019-03-15, tooth pik wrote:
>
> > On Fri, Mar 15, 2019 at 1:10 PM Gary Johnson wrote:
> > >
> > > On 2019-03-15, tooth pik wrote:
> > > > i've got
> > > >
> > > > "   vim: set foldmethod=marker
> > > >
> > > > at the bottom of my ~/.vimrc and for reasons i have yet to discover it
> > > > opens up with
> > > > foldmethod=manual and
> > > >
> > > > :verb set fdm?
> > > >
> > > > tells me nothing about who set it, just that it's manual
> > > >
> > > > have there been any recent updates to the processing of modelines?
> > > >
> > > > the modelines option is 5, and i've tried putting it at the top and
> > > > bottom, but it still
> > > > is being ignored
> > >
> > > There haven't been any such changes to Vim that I know of, but
> > > recent Ubuntu (e.g., 18.04) Vim packages include
> > > /usr/share/vim/vim80/debian.vim which includes this:
> > >
> > > " modelines have historically been a source of security/resource
> > > " vulnerabilities -- disable by default, even when 'nocompatible' is 
> > > set
> > > set nomodeline
> > >
> > > You might try executing
> > >
> > > :verbose set modeline?
> > >
> > > to see if that might be the problem.
>
> > thx, but modeline is set
>
> OK, now I see the problem.  I can reproduce it.  The problem is the
> syntax of your modeline.  Vim supports two forms of modelines.  The
> second form uses the word "set" and ends with a colon (:), e.g.,
>
> "   vim: set foldmethod=marker:
>
> The first form does not end with a colon, but also does not include
> the word "set", e.g.,
>
> "   vim: foldmethod=marker
>
> Change your modeline to either of those two forms and it should work
> fine.
>
> Regards,
> Gary
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: modeline stopped working

[tooth pik]

thx, but modeline is set

On Fri, Mar 15, 2019 at 1:10 PM Gary Johnson  wrote:
>
> On 2019-03-15, tooth pik wrote:
> > i've got
> >
> > "   vim: set foldmethod=marker
> >
> > at the bottom of my ~/.vimrc and for reasons i have yet to discover it
> > opens up with
> > foldmethod=manual and
> >
> > :verb set fdm?
> >
> > tells me nothing about who set it, just that it's manual
> >
> > have there been any recent updates to the processing of modelines?
> >
> > the modelines option is 5, and i've tried putting it at the top and
> > bottom, but it still
> > is being ignored
>
> There haven't been any such changes to Vim that I know of, but
> recent Ubuntu (e.g., 18.04) Vim packages include
> /usr/share/vim/vim80/debian.vim which includes this:
>
> " modelines have historically been a source of security/resource
> " vulnerabilities -- disable by default, even when 'nocompatible' is set
> set nomodeline
>
> You might try executing
>
> :verbose set modeline?
>
> to see if that might be the problem.
>
> Regards,
> Gary
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

modeline stopped working

[tooth pik]

i've got

"   vim: set foldmethod=marker

at the bottom of my ~/.vimrc and for reasons i have yet to discover it
opens up with
foldmethod=manual and

:verb set fdm?

tells me nothing about who set it, just that it's manual

have there been any recent updates to the processing of modelines?

the modelines option is 5, and i've tried putting it at the top and
bottom, but it still
is being ignored

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] patch 8.1.0814: :mksession cannot handle a very long 'runtimepath' (ed18f2c)

[tooth pik]

VIM - Vi IMproved 8.1 (2018 May 18, compiled Jan 24 2019 14:20:14)
Included patches: 1-813, 84

i guess i'm not the only one seeing this

On Thu, Jan 24, 2019 at 2:20 PM Jason Franklin
 wrote:
>
> Thanks for this!!!
>
> Looks like there's a bad patch number here.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] New search is horrible and difficult to disable (MINT19) (#3663)

[tooth pik]

i apologize for not following this sooner, but i build my own vim and
i have a vimrc so i never noticed
it was happening

i would have voted to have noincsearch be the default had i been
paying attention -- incsearch would
be horribly hard to live with and i don't get why anyone would want it
turned on, let alone the majority?
On Wed, Dec 5, 2018 at 6:41 AM Christian Brabandt
 wrote:
>
> Closed #3663.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gdk-CRITICAL when I use -geometry with offset

[tooth pik]

i get a similar error from gtk -- my vim is built with gtk3 and i've
had that problem so
long i've taken all offsets out of all my scripts and just move the
window after it's
painted

this is one of those problems where everyone points the finger at
everyone else...

my os is opensuse
On Wed, Nov 14, 2018 at 3:27 PM Mun  wrote:
>
> Hi Tony,
>
> On Wed, Nov 14, 2018 at 1:18 PM Tony Mechelynck
>  wrote:
> >
> > On Wed, Nov 14, 2018 at 9:34 PM Mun  wrote:
> > >
> > > Hi all,
> > >
> > > I'm not sure when this started, but it was sometime after v8.1 patch
> > > 119 .  I'm on v8.1 patch 524 now, and when I start vim thusly (e.g.):
> > > $ vim -u NONE -U NONE --noplugin -g -geometry 80x40+100 .vimrc
> > >
> > > I get the following error on my console (although, vim seems to work just 
> > > fine):
> > >
> > > (gvim:5756): Gdk-CRITICAL **: IA__gdk_window_get_origin: assertion
> > > `GDK_IS_WINDOW (window)' failed
> > >
> > > If instead I execute the following:
> > > $ vim -geometry 80x40 .vimrc
> > >
> > > All is well; no error.  The only real difference is that I am not
> > > placing the window at an offset.
> > >
> > > I get the same results on the following systems:
> > > 1. Red Hat Enterprise Linux v6.8
> > > 2. Ubuntu 16.04.5 LTS
> > >
> > > In both cases I am using GTK2.
> > >
> > > Is this a vim issue?  Or did I miss something that would require
> > > action on my part?
> > >
> > > Best regards,
> >
> > Have you tried specifying not one but two values (Δx and Δy, as shown
> > at ":help -geometry-example")? E.g. -geometry 80x40+100+0 for a
> > horizontal offset, or -geometry 80x40+0+10 for a vertical offset?
>
> Good question: Yes, I have.  That also causes the error to be output.
> I chose to only show the delta-X because in my mind that implied that
> any offset--even to only one dimension--caused the problem.  But I
> probably should have been more verbose about the situation.  My
> apologies.
>
> Kind regards,
>
> --
> Mun
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] patch 8.1.0515: reloading a script gives errors for existing functions (ded5f1b)

[tooth pik]

so the [!] is changing what it's for
On Sat, Nov 10, 2018 at 2:03 PM Bram Moolenaar
 wrote:
>
>
> > My point was that, although the *code* suggests that, the
> > documentation just added fails to make that clear. Maybe it should
> > say "When sourcing a script for the second time (and only the second
> > time)...".
>
> And the third time, fourth time, etc. It's not how many times the
> script is sourced but how often in that script the same function is
> defined.
>
> --
> A poem: read aloud:
>
> <> !*''# Waka waka bang splat tick tick hash,
> ^"`$$- Caret quote back-tick dollar dollar dash,
> !*=@$_ Bang splat equal at dollar under-score,
> %*<> ~#4 Percent splat waka waka tilde number four,
> &[]../ Ampersand bracket bracket dot dot slash,
> |{,,SYSTEM HALTED Vertical-bar curly-bracket comma comma CRASH.
>
> Fred Bremmer and Steve Kroese (Calvin College & Seminary of Grand Rapids, MI.)
>
> /// Bram Moolenaar -- b...@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 are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

improvement to my problem with GTK3

[tooth pik]

gui vim:

my problem, which has many work-arounds, is that my build with GTK3 provides a
dialog box that was unresponsive to the Tab key -- now it responds,
but there is no
visible indication on the buttons which one will react to Enter

the specific dialog box is the one that appears when you have
'confirm' set and perform a :quall after making changes

without hitting Tab, if you just hit Enter, it defaults to Yes and
saves before quitting

now, (not before all the recent GTK activity) if you hit Tab once, Enter sends a
keystroke to No and changes are lost

dunno if anyone cares, but thought it interesting that this is
incrementally changing

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

hitting 'y' in auto-confirm dialog has no effect

[tooth pik]

my problem is with the gui, specifically gtk3 in opensuse leap 42.3

i like to keep 'confirm' set, because it's so often quicker to quit and
confirm a save than to save then quit (it's my workflow so i get to
decide) -- anyway when i started building with gtk3 instead of gtk2
i noticed that the dialog that appears for the gui offering to save
my changes does not respond to the 'y' key or highlight different
buttons in response to the tab key -- it defaults to Yes so if i just
hit Enter then it responds to that as a press of the Yes button and
saves my changes, but it niggles at me and i wonder if anyone has
some ideas as to how i might make that silly dialog act right

also it responds appropriately to Esc and puts you back in the buffer,
so i can't claim this is a life threatening problem -- oh it responds to
mouse clicks too, but dammit i'm a vimmer!

terminal vim has no such problem and responds appropriately to
a press of 'y'

my vim at last glance was at 8.1.300

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: current version funny

[tooth pik]

thx tony -- at least now i know it wasn't something i did wrong

On Sun, Aug 12, 2018 at 6:17 PM, Tony Mechelynck
 wrote:
> On Mon, Aug 13, 2018 at 12:13 AM, tooth pik  wrote:
>> i see a patch 279 in the list, but my vim is 278 and git is telling me
>> i have current
>> source
>
> Mercurial tells me the same thing. Apparently the latest patch,
> «'incsearch' highlighting does not skip white space.», did not make it
> to the repository.
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

current version funny

[tooth pik]

i see a patch 279 in the list, but my vim is 278 and git is telling me
i have current
source

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to determine the x and y position of the Vim text window on screen

[tooth pik]

are you looking for :winpos?

On Fri, Jul 13, 2018 at 5:30 PM, Shidong Wang  wrote:
> I want to get the position of a window, but my vim has no +py/+py3 support.
>
> 发自我的华为手机
>
>  原始邮件 
> 主题：Re: How to determine the x and y position of the Vim text window on
> screen
> 发件人：Christian Brabandt
> 收件人：vim_dev
> 抄送：
>
>
> On Sa, 07 Jul 2018, Shidong Wang wrote:
>
>> Hello, any update on this topic? I want to use vim script to get the
>> windows position instead of using `pyeval('vim.current.window.col') `.
>
> What exactly is your problem?
>
> Best,
> Christian
> --
> Es ist falsch, mit dem Zahnstocher an Probleme heranzugehen, wenn der
> Abbruchhammer verlangt wird.
> -- M.S. Salomon (eigentl. Michael Schmidt-Salomon)
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "vim_dev" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vim_dev/_5rtuXn7w7E/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

re-grateful, i think

[tooth pik]

looking further i trip over something called varsofttabstop

sounds like just the thing, if options.txt is to be believed

forgive the hyperbole, i think

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: i am such an ingrate, forgive me

[tooth pik]

yes, as i believe i stated several times

having expandtab set is how i live -- if 'vartabstop' is rendered useless
from that then useless it will remain

i will go back to the drawing board for my own home-brew tab stop manager,
although as a possible cheat i'll be peaking in some syntax/cobol.vim or
other syntax modules for anyone mapping  to something interesting

On Sat, Jun 23, 2018 at 4:29 PM, Christ van Willegen 
wrote:

> Do you have expandtabs set? That would explain this, I think...
>
> Christ van Willegen
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: i am such an ingrate, forgive me

[tooth pik]

as would i, but see for yourself

i've tried, however hysterically, and failed at every attempt to get useful
activity out of them

On Sat, Jun 23, 2018 at 5:13 PM, Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:

> On Sat, Jun 23, 2018 at 11:29 PM, Christ van Willegen
>  wrote:
> > Do you have expandtabs set? That would explain this, I think...
> >
> > Christ van Willegen
>
> I haven't tried them yet, but I would expect
>
> :set vartabstop=4,20,10,8
>
> to mean that hitting the tab key moves the cursor forward to the first
> one encountered among columns 5, 25, 35, 43, 51, 59, 67, 75, …,
> filling the intervening columns either with one hard tab (if
> 'noexpandtab') or with as many spaces as necessary (if 'expandtab'),
> similarly to what happened some 60 or so years ago when I set the tabs
> on the backside of the paper carriage guide of my Underwood
> typewriter, an old hand-me-down from my grandfather who had got
> himself a newer model. (That typewriter looked more or less like the
> one at https://commons.wikimedia.org/wiki/File:The_Childrens_
> Museum_of_Indianapolis_-_Typewriter.jpg
> and it had adjustable tabs.)
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

i am such an ingrate, forgive me

[tooth pik]

i did pop the champagne when vartabs were announced, but find my excitement
dampened when i try them out -- they are not column-centric, like tabs on
the typewriters of yore, but something else entirely

indeed, when i turn on expandtabs, as i like to do, with

set vartabs=4,20,10,8

as the help implies, it interprets each tab as the first, because expandtab
has expanded the last one into spaces making each subsequent tab into the
first, so it just keeps adding 4 spaces

the meaning of vartabs, to me, are tabs that i can define like column
numbers -- as anyone old enough to have used an actual typewriter knows,
and might be coerced into describing if plyed with gin

first i define a set of tabs

then i start typing -- any time i hit the tab key spaces are inserted up to
the next defined tab key -- if i type past the first three tabstops and hit
the tab key it will insert spaces to make the line as long as defined by
the 4th tabstop position

this would be useful for cobol and other programmers for whom column
numbers are so significant, not just ingrates like me who want them to
align columns in his Plan

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

weird textwidth for vim files

[tooth pik]

I apologize in advance if this has already been discussed, but I was
editing a vim file today and noticed textwidth was sitting at 78

:verbose set tw? informed me it had been set by
/usr/local/shr/vim/vim81/ftplugin/vim.vim

dunno since when that's been the default but for me it's an immediate
candidate for an after/ftplugin entry

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

variable tab re-ask

[tooth pik]

bram--

if right before a version upgrade is a bad time to introduce new features,
does that mean right after one is a good time?

i really believe variable tabs would improve my vim experience

please?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: insertmode abbreviation gives newest/oldest change message

[tooth pik]

dunno if this breaks anything else, but it for sure fixes my problem

thx Christian

On Thu, Apr 26, 2018 at 4:44 AM, Christian Brabandt <cbli...@256bit.org>
wrote:

>
> On Do, 26 Apr 2018, Christian Brabandt wrote:
>
> >
> > On Mi, 25 Apr 2018, tooth pik wrote:
> >
> > > not all my insertmode abbreviations are broken, many are
> > >
> > > i just pulled and built 8.0.1765 -- i was at 1755 and they
> > > all worked then
> > >
> > > i have
> > >
> > > iabbrev  ~~7 =repeat('~', 72)=Eatchar('\s')
> > >
> > > (one line) in my .vimrc, and when I try to make my squiggle
> > > line it inserts ~~7 in the buffer without expansion, moves
> > > the cursor up a line, and gives the message:
> > >
> > > Already at newest change (if i've modified the buffer) or
> > > Already at oldest chante (if the insert is my first change to
> > > the buffer
> > >
> > > anyone have a clue what gives?
> >
> > Looks like patch 8.0.1758 broke it.
>
> I think the attached patch fixes it.
>
> Best,
> Christian
> --
> Der Newtonische Irrtum steht so nett im Konversationslexikon,
> dass man die Oktavseite nur auswendig lernen darf, um die Farbe fürs
> ganze Leben los zu sein.
> -- Goethe, Maximen und Reflektionen, Nr. 979
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

still more on insertmode abbreviations

[tooth pik]

when I create an iabb without the Eatchar function the bug
continues exactly the same:  if I trigger it with a space it
inserts the expanded text fine, but if I trigger with Enter
it bugs and moves the cursor up (or in one instance to the
command-line!)

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

more on the insertmode confufle

[tooth pik]

it doesn't expand and it gives the error if I hit Enter to
trigger it -- if I type a space it works fine

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

insertmode abbreviation gives newest/oldest change message

[tooth pik]

not all my insertmode abbreviations are broken, many are

i just pulled and built 8.0.1765 -- i was at 1755 and they
all worked then

i have

iabbrev  ~~7 =repeat('~', 72)=Eatchar('\s')

(one line) in my .vimrc, and when I try to make my squiggle
line it inserts ~~7 in the buffer without expansion, moves
the cursor up a line, and gives the message:

Already at newest change (if i've modified the buffer) or
Already at oldest chante (if the insert is my first change to
the buffer

anyone have a clue what gives?

(Eatchar is from line 957 in map.txt)

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

weird error

[tooth pik]

um

I rebooted (cold) and it went away

never mind

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Invalid MIT-MAGIC-COOKIE-1 keyInvalid WTF?

[tooth pik]

is anyone else getting this?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: test failure in Test_quoteplus()

[tooth pik]

I've got xclip installed but I don't think it runs as a background
process, you have to invoke it to use it

On Tue, Mar 27, 2018 at 1:46 AM, Chr. von Stuckrad <stu...@mi.fu-berlin.de>
wrote:

> On Mon, 26 Mar 2018, tooth pik wrote:
>
> > function RunTheTest[38]..Test_quoteplus line 35: Expected 'Yes, I can.'
> but
> > got 'Can you hear me?'
>
> I had some 'Can you hear me' a while ago in LINUX. Those went away after
> I killed all 'clipboard managers' (in my case 'diodon' or 'glipper').
> They seem to grab the contents and vim then blocks.
>
> Stucki
>
> --
> Christoph von Stuckrad* * | also XMPP = |Mail <stu...@mi.fu-berlin.de>
> \
> Freie Universitaet Berlin |/_*| 'jabber' via|Tel(Mo.,Mi.):+49 30 838-75
> 459|
> IT Mathematik & Informatik|\ *|stucki@jabber|  (Di,Do,Fr):+49 30 77 39
> 6600|
> Takustr. 9 / 14195 Berlin * * |.fu-berlin.de|Fax(home):   +49 30 77 39
> 6601/
>
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

test failure in Test_quoteplus()

[tooth pik]

First run:
function RunTheTest[38]..Test_quoteplus line 35: Expected 'Yes, I can.' but
got 'Can you hear me?'
Second run:
function RunTheTest[38]..Test_quoteplus line 35: Expected 'Yes, I can.' but
got 'Can you hear me?'

anyone else getting this?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Test_terminal_response_to_control_sequence still failing for me

[tooth pik]

I've been watching and no-one else seems to be reporting a
problem with this test -- it's been failing for me
consistently for several weeks

function RunTheTest[38]..Test_terminal_response_to_control_sequence line
17: Pattern '\\<\\d\\+R' does not match 'sh-4.3$ R'

question:  does this test make assumptions about the value
of $PS1?

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

doc nit redux

[tooth pik]

excuse me but really:  echo
trim("rmrrmm",
"rm")
echoes "any_chars" not any_chas

trim() is intended, and does, remove characters from the
beginning and/or end of strings, not out of the middle

I need to learn to have more faith in myself

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: doc nit

[tooth pik]

fine -- I'll shutup now

On Fri, Mar 23, 2018 at 1:44 AM, Christ van Willegen <cvwille...@gmail.com>
wrote:

> On Thu, Mar 22, 2018 at 11:54 PM, tooth pik <toothp...@gmail.com> wrote:
> > cool new function trim(), but it appears to have a typo in
> > the doc:  it says in the 3rd example it will return "any_chas"
> > where it appears to return "any_chars"
>
> No, because one of the characters in the 'mask' parameter is an 'r'...
>
> Christ van Willegen
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

doc nit

[tooth pik]

cool new function trim(), but it appears to have a typo in
the doc:  it says in the 3rd example it will return "any_chas"
where it appears to return "any_chars"

stupid little stuff like that gives a bad impression...

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How about a release?

[tooth pik]

nikolay:

don't worry about other people being able to see the properly formatted
columns

users of this feature will more than likely have 'expandtab' set

On Mon, Mar 12, 2018 at 5:06 PM, Nikolay Aleksandrovich Pavlov <
zyx@gmail.com> wrote:

> 2018-03-12 0:36 GMT+03:00 Matthew Winn :
> > On 11/03/18 15:04, Bram Moolenaar wrote:
> >>
> >> First of all, I'm sorry to disappoint you.  This patch has been floating
> >> around for a long time and has never made it in.  It's not urgent, and
> >> not a small thing to include, with the result I have been postponing it
> >> for a long time.
> >
> >
> > But it is a small thing to include. Vim already includes code that is
> called
> > when a tab needs to be displayed and works out how many columns need to
> be
> > skipped to get to the next multiple of the tabstop setting. From what I
> > remember all the variable tabs change does is check to see if the new
> > setting has been set and if so it looks up how many columns to skip
> instead
> > of calculating it. It's really not that complicated, and it has the
> > advantage that if the new setting isn't set then the only line of new
> code
> > that is called is the one that checks whether the setting is used. If not
> > then only the existing code runs, which means that anyone who doesn't use
> > the new setting has no chance of seeing any alteration in behaviour.
> >
> > The only slightly iffy thing about it is that it doesn't play well with
> the
> > linebreak setting, but that's a known issue with the current tab
> > implementation as well.
> >
> > If Vim was in some sort of feature freeze state where it was considered
> to
> > be complete for all time and no changes apart from bug fixes would ever
> be
> > made then I could understand your reluctance to add this, but you've been
> > perfectly willing to add far larger and far more disruptive changes to
> Vim
> > even when there's been no user-driven request for them at all. Why is
> this
> > one such a big problem?
> >
> >> A few statements needs further discussion though.  I have recently been
> >> involved in a product launch, which fortunately had the resources to do
> >> user studies and gather statistics about usage from different kinds of
> >> users.  Including doing user surveys that are statistically sound.
> >>
> >> What has become very clear is that there is no direct relation between
> >> what comes up in forums and what users really need or want.  For bugs
> >> and things that are hard to understand it can work, the more people
> >> complain the more likely it is a real problem.
> >>
> >> When it comes to new features or changes in existing features, it can go
> >> in any direction.  Some user may loudly express their opinion, and also
> >> get other users to say they also want it.  But when asking the average
> >> user, it turns out they won't need it, or even get confused by it.
> >> And in other cases users don't ask for functionality, but when we add it
> >> then lots of users find it very useful.
> >
> >
> > You can tell what sorts of functions people are likely to find useful by
> > looking at the sort of tasks people are likely to do. Very few people are
> > likely to want a terminal emulator built into an editor because they
> already
> > have ways to get at command lines outside the editor. They may certainly
> > make use of the feature once it's there, but there are very few tasks
> that
> > they couldn't do in an external command line that they can now do inside
> a
> > Vim terminal window. Very few people are likely to want interprocess
> > communication because it's not the sort of function people would even
> expect
> > an editor to have.
>
> Many people use Vim as an IDE, and IDE *is* expected to have some kind
> of asynchronous communication with external processes: IDE frozen
> because it runs even a compilation triggered by user would upset that
> user, not to mention the idea of running compilation on file save, to
> get the errors if nothing else, is simply impossible on any large
> project without upsetting user further or using some kind of
> asynchronous communications. And there are more tasks like linting or
> running static analyzer, or running related unit tests, … I am far
> from thinking that Vim users do not understand what asynchronous IPC
> is needed for, even if they would never use it directly and not via
> plugins.
>
> Also `system()` and `:{range}!` existed in Vim for years and served
> well for many tasks, and that *is* interprocess communication by
> definition. Also note that Wikipedia mentions files as one way of
> interprocess communication. You do expect editor to be able to edit
> files, don’t you?
>
> >
> > But editing tabular information is something that a great many people do.
> > It's not just a matter of working with tab-separated data files. How
> often
> > do you want to assemble columns of information in a text file where the
> > columns are inconvenient sizes? You wrote 

test failure in test_terminal redux

[tooth pik]

make test fails for me too -- in a different place so I started a new email:

>From test_terminal.vim:
Found errors in Test_terminal_response_to_control_sequence():
function RunTheTest[38]..Test_terminal_response_to_control_sequence line
20: Pattern '\\<\\d\\+R' does not match 'sh-4.3$ R'
TEST FAILURE
Makefile:40: recipe for target 'report' failed

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How about a release?

[tooth pik]

would this be a bad time to ask about variable tab stops?

On Thu, Mar 8, 2018 at 11:05 AM, Bram Moolenaar  wrote:

>
> I'm thinking of creating the 8.1 release.  The main new feature is the
> terminal window, with the debugger plugin.  And lots of smaller
> additions and plenty of bug fixes.
>
> Is there is something important that should still be included?
> Or something in the terminal window that should be changed before
> putting it in an official release?
>
> --
> Team-building exercises come in many forms but they all trace their roots
> back
> to the prison system.  In your typical team-building exercise the employees
> are subjected to a variety of unpleasant situations until they become
> either a
> cohesive team or a ring of car jackers.
> (Scott Adams - The Dilbert principle)
>
>  /// Bram Moolenaar -- b...@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_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: perl VIM::Msg("Error", "error msg here") not working for me

[tooth pik]

or, more accurately, the doc has it wrong in the example

On Thu, Nov 23, 2017 at 1:12 PM, Christian J. Robinson <hept...@gmail.com>
wrote:

> On Thu, 23 Nov 2017, tooth pik wrote:
>
> vim version 8.0.1331
>> os opensuse 43.2, gtk2
>> perl 5.18.2
>>
>> all the subjectline msg produces is "Error", not in red -- is that
>> supposed to work?  if not it should be removed from if_perl
>>
>
> You have your order wrong:
>
> :perl VIM::Msg("error message here, "Error")
>
> --
> Christian J. Robinson <hept...@gmail.com>
> "When the people fear their government, there is tyranny; when the
> government fears the people, there is liberty."  -- Thomas Jefferson
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> --- You received this message because you are subscribed to the Google
> Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

perl VIM::Msg("Error", "error msg here") not working for me

[tooth pik]

vim version 8.0.1331
os opensuse 43.2, gtk2
perl 5.18.2

all the subjectline msg produces is "Error", not in red -- is that supposed
to work?  if not it should be removed from if_perl

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: vim 7.3

[tooth pik]

you don't use git?

On Wed, Oct 25, 2017 at 12:00 PM, Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:

> On Wed, Oct 25, 2017 at 11:26 AM, Shubham Purwar
>  wrote:
> > Hi,
> >
> > I haved faced same issue in centos 6.6 while upgrading vim to latest vim
> version(vim 8).
> >
> > In my machine it is gcc compiler version problem. My previous gcc
> version in centos 6.6 is 4.8
> >
> > I have resolved it by upgrading my gcc to gcc 5.5. After that it has
> installed.
>
> FWIW, my present gcc version is 4.8.5 (from my openSUSE distro,
> release Leap 42.3) and I have no problems compiling Vim. The way I do
> it is described at:
>
> http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> (getting the source)
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm (once the
> source is downloaded)
>
> Sometimes I've seen Vim stop functioning after an OS release upgrade;
> running "make reconfig" (which reconfigures and recompiles everything
> from the ground up) cured the problem it every time.
>
> Note that my configure settings are set by means of environment
> variables, so that I never run configure other than through make, and
> that whenever make decides to reconfigure it does so according to my
> own configure settings.
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

can't build w current source

[tooth pik]

I'm getting a *** No rule to make target 'terminal.c'
error...

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Is it possible that vim support php like Python? (#1172)

[tooth pik]

imho the best vim is a vim built with no added interpreters -- lean and
mean and no surprises

any time I want to use another language I build a filter script, send the
relevant lines out to fmt,
or a python or perl or tcl or awk script coded to return those lines with
my beautiful enhancements

On Sun, Dec 25, 2016 at 5:05 PM, vim-dev ML 
wrote:

> 2016-12-25 18:36 GMT+03:00 Rick Woo :
> > I know you are meaning, but as @char101 says: if_python.c, if_ruby.c,
> > if_perl.xs just over 1000 lines, it's not big. And We can choose whether
> to
> > install these support, do not need to put whole php, python compiled into
> > Vim.
>
> if_python*.c files are not enough (they contain only
> python-version-specific code), most code is in if_py_both.h and it has
> 6837 lines (+ 1597 lines of if_python.c or 1682 lines of
> if_python3.c). if_ruby.c and if_perl.xs are very bad examples, the API
> they provide does not have many features Python has and even Python
> API does not have enough features to allow Python developers to avoid
> learning VimL in complex cases.
>
> >
> > I have learned VimScript, but when I write a plugin still not as good as
> php
> > language, if you are python programmer, you like python write plugin too.
>
> For any more or less complex plugin you can’t write it in Python, only
> in Python+VimL. Or find some third-party library which wraps things
> for which you need to use VimL and prepare to face leaking
> abstractions.
>
> >
> > We just want to find an good editor, not a new language? We use Vim is
> not
> > to learn new things happily, just want using Vim happily.
> >
> > We don't want to write a plugin without VimScript, just want to write
> plugin
> > like python.
> >
> > Vim can be used as a glue language, then programmers can write plugin in
> > their favorite language.
>
> I think that Neovim is following the right path here: Vim just needs
> IPC features with normal RPC API (no, channels are way too limited
> compared to Neovim API). Add `-heredoc` argument to `:command` there
> and you can create wrappers for any external language you like without
> changing the core.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> 
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Gtk3 warnings on stderr (#1149)

[tooth pik]

I get gtk warnings all the time, from both gtk2 and gtk3, and I can
reproduce them reliably.  Just set confirm, so that when you try to quit a
modified buffer in gvim it'll throw up that dialog box asking if you want
to save the buffer -- that dialog box generates no less than 6 gtk warnings
-- very ugly but apparently harmless

On Wed, Oct 5, 2016 at 10:37 AM, Matěj Cepl 
wrote:

> WHAT??? It is quite definitely problem of vim, but it is hidden on Ubuntu!
> "I don't see it, there is no problem"?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> 
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.