Re: error pulling

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 "

error pulling

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"

commit emails

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? --

Re: actual error

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

Re: actual error

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 the

actual error

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

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

-- -- 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

Re: Where is Bram?

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

patch withdrawal

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

Re: X11 requirements -- solved

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 ref

X11 requirements -- solved

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 --

X11 requirements list

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

Re: PS2 prompt appears after quitting vim

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

Re: PS2 prompt appears after quitting vim

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

PS2 prompt appears when quitting vim

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.

PS2 prompt appears after quitting vim

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

gvim bombs

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

gvim bombs with SEGV

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

Re: can't build since 9.0.0752

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" -

can't build since 9.0.0752

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

Re: Removing the rightleft feature?

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: > >

Re: git down?

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&qu

git down?

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

Re: 9.0.0475 segfaults while compiling vim9script

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: > >

need to back out updates

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

caught deadly signal SEGV

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

Re: Zero cmdheight

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

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

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 tel

can't build w/o stropts.h

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

Re: Patch 9.0.0220

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,

warnings from the compiler

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

Re: 3605 installs as 3604

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]

3605 installs as 3604

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

Re: Vim code coverage is now above 90%

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

Re: Patch 8.2.2759

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, >

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

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

GTimeVal warning

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

Re: Patch 8.2.0910

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

latest build

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 ---

Re: Patch 8.1.2187

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

Re: hampered scrolling behavior

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

hampered scrolling behavior

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 --

Re: Patch 8.1.1748

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

Re: script stopped working

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 display horked

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 '^

script stopped working

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

Re: can't pull

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: > >

can't pull

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

Re: How about sound?

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

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

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? > &g

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

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

can't build 1430

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]: ***

Re: Patch 8.1.1308

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

Re: Patch 8.1.1307

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,

Fwd: more testing questions

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,

Re: more testing questions

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: > >

Re: more testing questions

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 &

Re: more testing questions

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

more testing questions

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

idle question about testing

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

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

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

Re: modeline stopped working

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,

Re: modeline stopped working

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 i

modeline stopped working

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

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

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

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

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

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

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

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

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

improvement to my problem with GTK3

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

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

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

Re: current version funny

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 >> sourc

current version funny

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

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

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 >

re-grateful, i think

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

Re: i am such an ingrate, forgive me

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

Re: i am such an ingrate, forgive me

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

i am such an ingrate, forgive me

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

weird textwidth for vim files

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

variable tab re-ask

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

Re: insertmode abbreviation gives newest/oldest change message

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: >

still more on insertmode abbreviations

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

more on the insertmode confufle

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

insertmode abbreviation gives newest/oldest change message

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

weird error

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

Invalid MIT-MAGIC-COOKIE-1 keyInvalid WTF?

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

Re: test failure in Test_quoteplus()

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

test failure in Test_quoteplus()

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

Test_terminal_response_to_control_sequence still failing for me

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

doc nit redux

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"

Re: doc nit

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:

doc nit

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!

Re: How about a release?

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

test failure in test_terminal redux

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

Re: How about a release?

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

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

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

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

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

Re: vim 7.3

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 >

can't build w current source

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

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

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

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

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 --

  1   2   >