Happy birthday!
Hello Vim users, 29 years ago the very first version of Vim was built and distributed. And Vim is more popular than ever before! So, what's going on these days? VIM 9 DEVELOPMENTS - MAKING VIM SCRIPT FASTER AND EASIER TO USE This is a big project. A lot of progress has been made, but it will take time until we'll have "version 1.0". To make it possible to compile a Vim script function, so that it can be executed 10-100 times faster, it was required to make changes that are not backwards compatible. Such as not having a dictionary and list for the function arguments, since that causes too much overhead for every function call. Once making changes that are not backwards compatible, it seemed like a good idea to also make it easier to use Vim script. Or in other words: "less weird". Using keywords and syntax that is similar to popular programming languages helps a lot. At the same time we can make the semantics more predictable and avoid mistakes. Type checking is a great help with that, especially when writing a large plugin. In case you don't like Vim 9 script, you can keep using the legacy one, it won't go away and remain backwards compatible. RELIABILITY - MAKING SURE VIM NEVER FAILS The functionality included with Vim for testing has been greatly improved. Besides unit testing, it is now also possible to write screendump tests. That is especially useful for highlighting and dynamic behavior, such as with completion. We now have continuous integration on three platforms. Neither of them is perfect, but together it gives very good coverage of systems and variations in configuration. The main challenge is to avoid flaky tests. Source code coverage is now at 88.75%. It keeps increasing, although it's getting harder to cover the last few lines, especially related to running out of memory. We have also several people running fuzzers and other tools to uncover problems. I dare to say that Vim is more reliable than ever before. Thanks to everybody who helped with that. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 178. You look for an icon to double-click to open your bedroom window. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202011021819.0A2IJc1o3563112%40masaka.moolenaar.net.
Re: Yahoogroups is closing down
Ottavio Caruso wrote: > On Wed, 14 Oct 2020 at 08:37, Christian Brabandt wrote: > > > > Hi, > > not sure if you have noticed this (or even still uses it), but Yahoo > > announced, that the Yahoogroups will be shutdown on Dec 15th, 2020. > > > > https://uk.help.yahoo.com/kb/groups/SLN35505.html > > > > If I understand the implications correctly, this means the mailinglist > > archive before the move to Google Groups will be lost. > > I don't know what can be done fo the past, but, for the future, this > is a reminder that Google can do the same in the future with Google > Groups. Maybe moving all discussions to the good old Usenet? Google groups just got a refresh, it's very unlikely it will go away. And if it does, Google has a good reputation of allowing for exporting all information before shutting down. -- >From "know your smileys": ;-0Can't find shift key ,-9Kann Umschalttaste nicht finden /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202010141808.09EI8sRR653867%40masaka.moolenaar.net.
Re: Yahoogroups is closing down
Christian wrote: > not sure if you have noticed this (or even still uses it), but Yahoo > announced, that the Yahoogroups will be shutdown on Dec 15th, 2020. > > https://uk.help.yahoo.com/kb/groups/SLN35505.html > > If I understand the implications correctly, this means the mailinglist > archive before the move to Google Groups will be lost. > > @Bram, > You might want to remove the link to Yahoogroups from > https://www.vim.org/maillist.php I had given up on Yahoo a long time ago. I have attempted to make some updates, but it refuses my login and there is no way to retrieve or reset the password. I don't see a way to access the archives. -- hundred-and-one symptoms of being an internet addict: 87. Everyone you know asks why your phone line is always busy ...and you tell them to send an e-mail. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202010141004.09EA44Qr554490%40masaka.moolenaar.net.
Re: How to grep #tag?
> On 2020-10-11, Shlomi Fish wrote: > > On Sat, 10 Oct 2020 21:09:26 - (UTC) > > Lifepillar wrote: > > > >> How can I grep text with a special symbol, such as #? > > > > Either: > > > > :grep \\#p > > > > Or: > > > > :grep '\#p' > > > > Seem to work here in gvim (Linux; shell is either bash or zsh). > > That does it! Double-escaping is always tricking me. You can use any special character to surround the pattern, it's a lot easier than escaping. I often use ":grep /pattern/ *", unless the pattern contains a slash. -- I'm trying to be an optimist, but I don't think it'll work. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202010111222.09BCMkFq3991128%40masaka.moolenaar.net.
Re: `set t_Co=16` in vimrc file has no effect
Christian wrote: > On Mi, 30 Sep 2020, Bram Moolenaar wrote: > > > > As I recall, VimEnter is too early. > > Would a timer work? > > > > I often work remotely, with a terminal on my desktop at home or in > > > an office and the host on which Vim is running many miles away, > > > often through a relatively slow network. For a while, after either > > > my xterm changed or Vim changed so that t_Co was reset after > > > receiving the termresponse, my vim screen would flash at startup > > > because it would first be drawn using t_Co=16 as set in my vimrc, > > > then be redrawn a moment later at t_Co=256 when the termresponse was > > > received. > > > > That's why I was thinking of disabling the mechanism, to avoid the > > flicker. Of course you then need to manually set the value. > > Do you mean, if the option is set manually in vimrc, disable the > termresponse? That would be a good compromise, I think. Not the termresponse, it is used for several other things, but disabling the mechanism to fetch the values from xterm, which is what causes t_Co to change later, at an unpredictable time. -- Don't Panic! -- The Hitchhiker's Guide to the Galaxy /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202010011437.091EbrpN1272303%40masaka.moolenaar.net.
Re: `set t_Co=16` in vimrc file has no effect
Gary Johnson wrote: > On 2020-09-30, Christian Brabandt wrote: > > On Di, 29 Sep 2020, Gary Johnson wrote: > > > > > I'm too busy at the moment to give this a very thoughtful response, > > > and it was a while ago that I looked at that code, but it seems that > > > there were several things done in response to receiving the > > > termresponse, so I don't know that one option would serve all needs. > > > In the present case, the only problem seems to be the setting of > > > t_Co. > > > > > > The problem I've had is that I want to set various options and > > > highlights depending on the terminal type, but the type is not > > > accurately known when vimrc is read, and when the TermResponse event > > > is triggered, not everything can be set correctly. > > > > > > I've resorted to having the termresponse queried in my ~/.bashrc, > > > which sets an environment variable that vimrc can then read. It > > > works very well for making terminal-dependent settings in my vimrc > > > and colorscheme files. When vim queries and receives the > > > termresponse itself, it then makes the additional settings you > > > mentioned. It would be nice, though, if this could all be done > > > within Vim. > > > > > > I think maybe the whole termresponse behavior should be thought > > > through and made more useful, perhaps by adding a later > > > TermResponse-like event. I'll try to find some time. > > > > I think this was suggested before. Also the todo file contains a couple > > of statements regarding termresponse, e.g. > > > > , > > | Add another autocommand like TermResponse that is fired for the other > > terminal > > | responses, such as bg and fg. Use "bg", "fg", "blink", etc. for the name. > > ` > > > > I think Bram also suggested to add additional TermResponse for > > the various term events before. > > > > BTW: Why wouldn't the VimEnter autocommand work? Is that, because > > changing terminal options would then require some more initialization or > > is that triggered too early? > > Thanks for the pointers. > > I had been thinking of having a single TermResponsePost event, but > having multiple events might be better, especially if each of the > other responses is sent separately. > > As I recall, VimEnter is too early. Talking back and forth with xterm can take some time. I have thought of another mechanism that would exchange a hash code of all the codes. If Vim recognizes it (cashed response) it's done quickly. If not then Vim would request the termcap/terminfo settings from the terminal. This way you have a delay only once and accurate codes all the time. But no work has been done for it, and it would require talking to xterm clones and other program authors to get it widely accepted. > I often work remotely, with a terminal on my desktop at home or in > an office and the host on which Vim is running many miles away, > often through a relatively slow network. For a while, after either > my xterm changed or Vim changed so that t_Co was reset after > receiving the termresponse, my vim screen would flash at startup > because it would first be drawn using t_Co=16 as set in my vimrc, > then be redrawn a moment later at t_Co=256 when the termresponse was > received. That's why I was thinking of disabling the mechanism, to avoid the flicker. Of course you then need to manually set the value. > I am currently working from home and all my Vim sessions are local > or within my home network, so I don't have the delay problem. I'll > have to determine which of the VimEnter and TermResponse events > occurs first, but a general solution should assume that TermResponse > occurs later. It's possible, but the flicker would still happen. -- Q: What is the difference between open-source and commercial software? A: If you have a problem with commercial software you can call a phone number and they will tell you it might be solved in a future version. For open-source software there isn't a phone number to call, but you get the solution within a day. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202009302050.08UKo8341065768%40masaka.moolenaar.net.
Re: `set t_Co=16` in vimrc file has no effect
Gary Johnson wrote: > On 2020-09-26, Nikolay Belikov wrote: > > Hello all, > > > > I've stumbled upon strange behavior in Vim 8.2 regarding `t_Co` > > variable. This might be a bug, but more probably is just a case of > > PEBCAK, so maybe someone could point me towards what I'm doing wrong. > > > > Background: I want to use my terminal emulator (which is plain old > > `xterm`) color scheme across all TUI programs, including Vim. I've > > added `set t_Co=16` to my `.vim/vimrc` file and expected Vim to limit > > itself to 16 base colors (at least this is what all sources on Internet > > say to do, which I managed to find). However, it appears that Vim does > > not honor my will and resets `t_Co` to 256, unless I manually type `:set > > t_Co=16` in command-line mode. > > > > I reduced my `vimrc` to the bare minimum needed to reproduce the > > problem, and now it contains a single line: > > > > set t_Co=16 > > > > At this point I'm unsure what to do and ask for your assistance. I > > attach a log captured by running `vim -V100vim.log` as well as version > > info (`vim --version >vim.version`), and I'm willing to provide any > > other info that may be of help. > > Vim may change t_Co when it receives a terminal's termresponse. > I noticed the same strange behavior some years ago with Vim setting > t_Co to 256 in an xterm. See > > :help v:termresponse > :help t_RV > :helpgrep termresponse > > You can test this by adding this to your vimrc, > > set t_RV= > > and seeing if t_Co is still mysteriously reset to 256. > > You may be able to reset t_Co to 16 with this in your vimrc: > > autocmd TermResponse * set t_Co=16 > > I say "may" because I've found that not everything works as I would > expect it to in the environment of a TermResponse autocommand. > > See > > :help TermResponse Vim has a special mechanism to request the actual termcap codes from xterm. This happens after receiving the termresponse. Using the TermResponse autocommand may do this too early. There is actually no way to disable this mechanism without also disabling some other stuff. It might be helpful to add an option to disable the mechanism. 'termgetcodes', default on? The function that sends the requests is req_more_codes_from_term(). -- hundred-and-one symptoms of being an internet addict: 15. Your heart races faster and beats irregularly each time you see a new WWW site address in print or on TV, even though you've never had heart problems before. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202009291834.08TIYxSX757996%40masaka.moolenaar.net.
Re: Lambdas and "typedefs" in Vim9
> This is what I have tried:
>
> vim9script
>
> def Filter(l: list, Cond: func(string): bool): list
> let res = []
> for item in l
> if Cond(item)
> add(res, item)
> endif
> endfor
> return res
> enddef
>
> def Filter2(l: list, Cond: func(string): bool): list
> return filter(copy(l), Cond)
> enddef
>
> def MyCond(v: string): bool
> return v =~ '^a'
> enddef
>
> let x = ['a', 'b', 'c']
>
> Filter(x, MyCond)
> # OK
>
> Filter(x, funcref(MyCond))
> # OK
>
> Filter(x, { v -> v =~ '^b' })
> # E1013
Well, in a sense that is correct. The Filter() functions accepts a
function reference with a specific type, and what is passed in is a
function reference without any known type. Using that function
reference might fail, thus requires a runtime check, which is what we
want to avoid in a compiled function.
This works:
def Func()
Filter(x, { v -> v =~ '^b' })
enddef
Func()
Because the lambda is compiled.
I suppose what we could do is that when an argument is a lambda, first
compile it, so that we have the type. This would also make execution
faster. It gets a bit more complicated if it's a nested structure, e.g.
dict with a lambda.
--
A)bort, R)etry, B)ang it with a large hammer
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202009271545.08RFjj4L186795%40masaka.moolenaar.net.
Re: Lambdas and "typedefs" in Vim9
> I have not followed the development of Vim9 script closely, but
> yesterday I have started to play with it. I was pleasantly surprised to
> see how far it's got already: I could convert some scripts of mine
> without much effort and make them run just fine!
Glad to hear. Note that some things still change.
> I have two questions/curiosities:
>
> 1. I was not able to pass lambdas to defs, only funcrefs. Can/will this
>be supported?
Can you give an example of what does not work?
> 2. Has a type aliasing or "typedef" mechanism been considered or,
>perhaps, already planned? My use case is defining a library of opaque
>types, which I can change without the need to modify client code.
Yes, typedefs are planned to be added at some point. We can make
everything work without it, so it's for later.
--
The average life of an organization chart is six months. You can safely
ignore any order from your boss that would take six months to complete.
(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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202009271151.08RBpfkI137035%40masaka.moolenaar.net.
Re: Real laws, yet funny (For Bram's, or anyone's, collection of signature quotes)
Tony wrote:
> Since March 2007, it is a real standing law in the US state of
> Arkansas (whose name is to be pronounced as "Arkansaw"), that the
> "possessive" (i.e. genitive) form of the state's name must be written
> «Arkansas's» and not «Arkansas'». (I'm using French quotes to
> emphasize the difference with the apostrophe).
>
> Reference: Arkansas Apostrophe Act, mentioned in ABC News [USA] on 6
> March 2007, see item 38 under
> https://en.wikipedia.org/wiki/Apostrophe#References
It's interesting, but I don't find it funny. Perhaps linguists
(linguists's ?) find that funny.
--
DENNIS: Look, strange women lying on their backs in ponds handing out
swords ... that's no basis for a system of government. Supreme
executive power derives from a mandate from the masses, not from some
farcical aquatic ceremony.
"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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202009211805.08LI5a7J3456579%40masaka.moolenaar.net.
Re: Vim9 syntax and ftdetect
NiVa wrote: > I Wonder if there is a syntax file for Vim9 script. > Suppose that ftdetect would be based on file content 'vim9' string. There is no sepate syntax file. It's work in progress, but I think it works with just one file. -- BEDEVERE: How do you know so much about swallows? ARTHUR: Well you have to know these things when you're a king, you know. "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202009121254.08CCsRX31118672%40masaka.moolenaar.net.
Re: Archives of vimconf 2020
Christian wrote: > On Mo, 07 Sep 2020, het jagani wrote: > > > I missed the conference. Is there anyway I can watch talks now.? > > Looks like they should appear here earlier or later: > https://www.youtube.com/channel/UCPK_UHtbfcWABCi0F0GPG6w > > currently there are only 4 videos here. The number increased up to 14. I started to watch a few, but then they got all switched to "private" and can't be seen anymore... -- ARTHUR: Did you say shrubberies? ROGER: Yes. Shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies. "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202009071538.087Fcfc71206706%40masaka.moolenaar.net.
Re: Vim online conference - hopin.to account required
Sven wrote: > * Bram Moolenaar [2020-09-05 14:00]: > > Sven wrote: > > > here are some more links to the vimconf: > > > homepage: https://www.vimconf.live/ > > > webpage: https://hopin.to/events/vimconf-live > > That works, but there are no links in the events. > > i dont think the talks can be linked individually at all. :-/ > in case i am missing these - please let me know so i can add them I can't find links to individual talks, best I could find is a link to the agenda: https://www.vimconf.live/#agenda > > Is it possible to just watch without registering? > > The Terms & Conditions take some time to read... > > official word: > > ABD Today at 3:39 PM: > @guckes unfortunately not, you need to register > for hopin.to's service to enter the conference > it's free of course, but unfortunately > you do need an account > > by the way: > > Vimconf.live > Sep 5, 6:00PM to Sep 6, 6:00PM CEST > 949 people attending > > join us! :) I'm probably not the only one who can't watch live. I would prefer a recording, so I can watch at a time my own choice. Hopefully the recordings will be made available, e.g. on youtube, which doesn't require an account. Having the presentation slides available would also be nice. Anyway, I appreciate setting up the conference! -- ARTHUR: Bloody peasant! DENNIS: Oh, what a give away. Did you hear that, did you hear that, eh? That's what I'm on about -- did you see him repressing me, you saw it didn't you? 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/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202009051504.085F49TN630376%40masaka.moolenaar.net.
Re: Vim online conference - schedule.txt
Sven wrote: > * Yegappan Lakshmanan [2020-09-01 18:14]: > > The Vim online conference is this weekend: > > https://hopin.to/events/vimconf-live > > here are some more links to the vimconf: > > eventname: Vim Conference 2020 > duration: 2020-09-05+06 Sat+Sun > homepage: https://www.vimconf.live/ > webpage: https://hopin.to/events/vimconf-live > schedule: https://hopin.to/events/vimconf-live#schedule > speakers: https://hopin.to/events/vimconf-live#speakers > twitter: @VimconfLive #vimconf > stream: https://discord.gg/Cz9J4ZD > > here is my version of the schedule (text/plain and text/html): > schedule: http://www.guckes.net/vimconf/schedule.txt > schedule: http://www.guckes.net/vimconf/schedule.html > > apropos: does anyone have a way to turn those > calendar files (ics) into a table like i did? > > here is that ICS file: > calendar_shorturl: https://tinyurl.com/vimconf -> > calendar: > https://calendar.google.com/calendar/ical/c_pmamnjmfa6b2ii3v1ei1te5mm4%40group.calendar.google.com/public/basic.ics That works, but there are no links in the events. Is it possible to just watch without registering? The Terms & Conditions take some time to read... -- Q: How does a UNIX Guru pick up a girl? A: look; grep; which; eval; nice; uname; talk; date; /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202009051149.085BnaB7576102%40masaka.moolenaar.net.
Re: Using vimgrep to find files NOT containing a string
Marius Gedminas wrote:
> On Wed, Sep 02, 2020 at 07:14:37PM +, russurquhart1 via vim_use wrote:
> > I generally use:
> >
> > :vim `beta: ` **/*.md | copen
> >
> > To traverse my Markdown files to find those containing 'beta: '.
> >
> > I need to do the opposite but can get the pattern right. I tried
> >
> > :vim -v `beta: ` **/*.md | copen
> >
> > thinking that might work but no dice.
> >
> > I looked through teh vimgrep help but couldn't find anything.
> >
> > Does anyone know how to do this?
>
> Not with vimgrep, but on the command line to find files that don't
> contain a pattern I generally do
>
> grep -c "beta: " **/*.md | grep ':0$' | sed -e 's/:0$//'
>
> this assumes your shell can do ** and it's probably not the most
> elegant/efficient way of doing it, but it's one that I can remember how
> to spell.
>
> And then I opened the grep manual page to see if there's an easier way,
> and lo and behold:
>
>-L, --files-without-match
> Suppress normal output; instead print the name of each
> input file from which no output would normally have been
> printed. The scanning will stop on the first match.
>
> Just what the doctor ordered!
Not exactly. This switches from reporting matches to reporting file
names with matches. The output won't be parsed properly.
> To feed these files to to vim you could play with temporarily setting
> 'grepprg', or use :args `grep -L "beta: " **/*.md`
>
> If your shell doesn't do **, you may need to use something a bit more
> complicated like
>
>find -name '*.md' -exec grep -L "beta: " {} +
The grep program has a long list of options, I don't think we will
want to add them all to :vimgrep. Especially if it's about listing
files with/without matches, there are several other ways to do that.
--
You know you use Vim too much when you have this alias in your
~/.bashrc file: alias :e=/bin/vim (Eljay Love-Jensen)
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202009031450.083Eolqu060864%40masaka.moolenaar.net.
Re: Meta: How to read this forum/board now that Google Groups is busted
J S wrote: > As many of you are no doubt aware, GG broke its interface this week so > that you have to be logged in in order to read group content. I had > been using email to post to this forum (vim) and using GG to read it. > I can no longer read GG, because of the aforementioned breakage. None > of my old GG ids work and it is impossible to create a new one (so > don't even go there). > > Are there any alternatives for reading this forum? I tried the Yahoo > version of the archive, but soon ran into the same security nonsense > as GG is currently infected with. > > Any other ideas? > > P.S. Be sure to CC to my email any response on this thread, as > (obviously) I won't otherwise be able to read them. Thanks. Not sure what you are doing. I can can read your message using an incognito window, thus without logging in, through: https://groups.google.com/forum/#!topic/vim_use/EceYG0L5Vyw The Yahoo archive has been broken for a long time, and the account I used to maintain it is no longer valid, and Yahoo refuses any way to fix that. I can't even delete the contents there. -- hundred-and-one symptoms of being an internet addict: 267. You get an extra phone line so you can get phone calls. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202008221909.07MJ9HAe790019%40masaka.moolenaar.net.
Re: gv bug?
Tim Chase wrote: > > > To replicate > > > > > > $ vi -u NONE > > > :r !jot 15 > > > > > > (or use `seq 15` to get the numbers 1-15 in your file) > > > > > > 3GVG:g/5/d > > > > > > This should delete lines 5 and 15 because they contain a "5". > > > However, issueing > > > > > > gv > > > > > > does not reselect the text. > > > > For me it does. I cannot guess why it doesn't work for you. > > I just went to reproduce it and there seems to be something to the > order of how the lines are selected. I slightly tweaked the order of > the commands to make it clear what range I was selecting, assuming > that a-range-was-a-range. Sorry about that confusion. > > If I do the selection from top to bottom, it does indeed work as you > encountered: > > $ vim -u NONE > :r !jot 15 > 3GVG:g/5/d > gv > > But if I select them from bottom-to-top > > $ vim -u NONE > :r !jot 15 > V3G:g/5/d > gv > > I get the (mis)behavior I was seeing...the "gv" doesn't reselect the > available range. > > Again, sorry I messed up reproducing that situation. Hmm, now I can reproduce it. The mark on the last line has become invalid. ":marks" shows the "<" mark as "invalid". Weird thing is that when using "'<" it works, but it actually jumps to the ">" mark position. The code shows that this is intentional. I suppose that when the Visual mark is beyond the end of the file, it's best to put it on the last line. -- Light travels faster than sound. This is why some people appear bright until you hear them speak /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202007192010.06JKA8At313362%40masaka.moolenaar.net.
Re: gv bug?
Tim Chase wrote: > To replicate > > $ vi -u NONE > :r !jot 15 > > (or use `seq 15` to get the numbers 1-15 in your file) > > 3GVG:g/5/d > > This should delete lines 5 and 15 because they contain a "5". > However, issueing > > gv > > does not reselect the text. For me it does. I cannot guess why it doesn't work for you. > If instead you have 16 numbers > > $ vim -u NONE > :r !jot 16 > > and do > > 3GVGk:g/5/d > > (selecting through the penultimate line, so the same text selected > as before, followed by the same command, just with a line below '> > containing "16") followed by > > gv > > it works, adjusting the '> mark to the line containing "16". So > there's clearly some "the last line of my visual range was deleted, > so we need to adjust it" logic, but it doesn't seem to check if that > adjusment runs of the end of the file and back it off instead. > > Thanks! -- It was recently discovered that research causes cancer in rats. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202007191518.06JFI61v237518%40masaka.moolenaar.net.
Re: Not sure if bug, accurate message, or whether there's a better way
Tim Chase wrote:
> Issued the following
>
> $ vim -u NONE
>
> then did
>
> ou
>
> This gave me an E19 ("Mark has invalid line number").
>
> In contrast, starting a bare vim
>
> $ vim -u NONE
>
> and just using
>
>
>
> doesn't balk, even though there's also no valid previous-line-number
> to jump to.
>
> My gut says the two should behave the same. Either both should E19,
> or neither should.
>
> I'm also not sure what to do with it other than to mention the
> peculiarity and let core devs take a crack at why there
> should/shouldn't be some sort of difference.
>
> No big deal, just a minor bugaboo/wart I encountered.
It looks correct. The "u" command sets a mark and then in this case
deletes the line that the mark is on. Thus you can't go back there.
--
How To Keep A Healthy Level Of Insanity:
7. Finish all your sentences with "in accordance with the prophecy".
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202007141954.06EJsuU43141105%40masaka.moolenaar.net.
Re: Status of sound support in Vim
Dominique wrote: > Lifepillar wrote: > > > What is the status of +sound in Vim? In particular, is anyone working on > > adding support for macOS? > > > > The manual has examples mentioning Ubuntu, so I infer that Ubuntu should > > be supported, but I cannot get any sound. I have tried with .wav, .oga > > and .ogg files, so I don't think it's a format issue. Audio is working > > in my platform, as I can play sound files with ffplay and other tools > > from the command line. Using Vim 8.1.2269 with +sound. Any idea how to > > troubleshoot that? > > Sound works for me on Xubuntu-18.04. > I don't really use it, it works fine with e.g. the demo game: > https://github.com/vim/killersheep > > For macOs, I see that ":help todo" has this item: > > === BEGIN QUOTE :help todo === > Sound: support on Mac? Or does libcanberra work there? > === END QUOTE === Right, it requires someone to find out the way to implement it on Mac. It should be able to play .mp3 or .ogg file. Hopefully both. -- FIRST VILLAGER: We have found a witch. May we burn her? "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202007051322.065DMQpb571366%40masaka.moolenaar.net.
Re: VimScript for Python developers
Prabir Shrestha wrote: > There is also Vim Script for JavaScripters. > https://w0rp.com/blog/post/vim-script-for-the-javascripter/ Thanks, that also looks useful. I'll add the link to usr_41.txt. -- CUSTOMER: You're not fooling anyone y'know. Look, isn't there something you can do? DEAD PERSON: I feel happy... I feel happy. [whop] CUSTOMER: Ah, thanks very much. MORTICIAN:Not at all. See you on Thursday. CUSTOMER: Right. 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/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202006131121.05DBLTmc555163%40masaka.moolenaar.net.
Re: VimScript for Python developers
Yegappan wrote:
> I have put together the following gist to help Python developers
> with VimScript:
>
> https://gist.github.com/yegappan/16d964a37ead0979b05e655aa036cad0
Very useful!
> Let me know if you have any comments/suggestions.
Some things are identical. Instead of the reader staring at the text to
spot any differences, how about just saying "the same". E.g. at the
start of "Comparison Operators".
For dictionaries it would be useful to mention the #{} form:
let d = {'red' : 10, 'blue' : 20} or #{red : 10, blue : 20}
let x = {}
Some day it would be nice to do the same for Vim9 script.
--
"The amigos also appear to be guilty of not citing the work of others who had
gone before them. Even worse, they have a chapter about modeling time and
space without making a single reference to Star Trek!"
(Scott Ambler, reviewing the UML User Guide)
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202006011209.051C90JK890555%40masaka.moolenaar.net.
Re: Vim9 - Python/Lua interface
> I first came into contact with Vim about 15 years ago. > A few times I uninstalled it and reinstalled it a while later. After a few > months I was convinced it was the best text editor I had ever seen. > I only noticed how much value it had when I wrote scripts in vimrc myself > and changed plugins/menu. > Still, I had to get used to Vimscript. A whole new language, not something > similar I already knew. > However, I got completely excited when I understood that I could write > scripts in Lua and Python. > Why? Because it was not easy to get used to Vimscript and the help I asked > on internet sites was rarely answered. > Anyway, I did benefit from the vim_use group but I noticed that I found > solutions faster writing in Python. > I knew the language better and there was a huge amount of information > online. > > Now I recently read on Reddit that there would be some changes in Vim9 and > not everyone thought it was a good idea. > Vimscript is going to change in Vim9 to make Vim respond faster. That's a > good idea, although Vim is fast enough for me. The fastest editor I've ever > seen. > Reading further I read that Vim9 will be without its Python/Lua interface. > That is really a pity. Not sure what gave you that idea. We don't plan to do much work on these interfaces, but they are certainly not going away. I suggested to remove the least used one, Scheme, and immediately got objection from a few people. Python is widely used, and some people like Lua. Might also help for people who come from Neovim, which did some more Lua stuff. Otherwise Lua isn't widely used and it doesn't appear to grow: https://trends.google.com/trends/explore?date=today%205-y&geo=IT&q=%2Fm%2F0chpd,%2Fm%2F0n50hxv,%2Fm%2F05z1_ > Instead of removing the Python and Lua interface, why not integrate them > even more? > It would be great if we could search in Vim with python regex. > Even if we could program the user input in python code. > People often already know Python and Lua. I think it will bring a much > larger amount of users to Vim. This has existed as an idea for a long time, but nothing much has happened. Clearly there are more plugin writers using Vim script than anything else. > Is it true that the Python and Lua interface will disappear? No. -- I AM THANKFUL... ...for all the complaining I hear about the government because it means we have freedom of speech. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202005131805.04DI5CsL021855%40masaka.moolenaar.net.
Re: Encryption is not considered a change by the :x command
Eli the Bearded wrote: > Tony Mechelynck wrote: > > Ninu-Ciprian Marginean wrote: > >> When we look at the quickref documentation we find: > >> If we open an existing file and we do not do any changes except for > >> changing the encryption key(with the ":X" command) and then use the ":x" > >> command to exit, the changes to the encryption key will not be applied. > ... > >> Is this a bug? Is it intended? Anyways, I just wanted to leave this > >> here for people to know the workaround. If it's a bug, I'm willing to > >> report one on github. > > If it's a bug (I'm not sure) most developers read this mailing list too > > anyway. > > I don't think it is a bug. I make use of encrypted files regularly. I > believe it is that way to prevent any accidental encryption of a > previously plaintext file. Because that is a real pain in the neck.[*] > > There are many ways cryptmethod and key can be set: $HOME/.vimrc, "set > exrc" and ./.vimrc, "set modeline" and modelines, etc. Vim can try (and > may actually do so) to protect you against key being set > non-deliberately, but it can only go so far. > > Additionally using :X to encrypt-save the file is the recommended way to > set the encryption key because it is the most robust against the key > being exposed. > > [*] That one time in the early 1990s when I hit with capslock > on and vi (or vim2 or vim3) accepted a password of a bunch of > control keys like backspace, , , etc, is seared into > *my* memory. It really made me hate programming languages with > all caps keywords and case-sensitivity. Isn't that avoided by Vim requiring you to enter the same password again? Can hardly accidentlly type the same random text twice. It really only makes a difference when using ZZ or a similar "write only when changed" command. -- Warning label on a superhero Halloween costume: "Caution: Cape does not enable user to fly." /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202005111747.04BHl8BN017662%40masaka.moolenaar.net.
Re: Encryption is not considered a change by the :x command
Ninu-Ciprian Marginean wrote: > When we look at the quickref documentation we find: > > :xit:x[it][!] [file] like ":wq" but write only when changes have >been made > > If we open an existing file and we do not do any changes except for > changing the encryption key(with the ":X" command) and then use the ":x" > command to exit, the changes to the encryption key will not be applied. > Note that the ":X" is not mandatory to be used, the behavior is the same > even if we use ":set key=value". By changing the encryption key I mean all > 3 scenarios(1 - file is not encrypted to file is encrypted; 2 - file is > encrypted to file is encrypted, but with a different key; 3 - file is > encrypted to file is not encrypted), since a key with an empty value means > the file is not encrypted. > > Note that ":wq" does change the encryption. > > Is this a bug? Is it intended? Anyways, I just wanted to leave this here > for people to know the workaround. If it's a bug, I'm willing to report one > on github. This is similar to changing the 'fileformat' option. The buffer is considered modified then. So yes, I think we can call this a bug. I'll add it to the todo list. You can create an issue on github for more visibility. -- hundred-and-one symptoms of being an internet addict: 78. You find yourself dialing IP numbers on the phone. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202005091540.049Fe0ur003568%40masaka.moolenaar.net.
Re: X error and vim dies
Manfred Lotz wrote:
> On Tue, 5 May 2020 23:31:02 -0700 (PDT)
> John Little wrote:
>
> > If this problem has consequences (vim dying in the middle of your
> > work can be bad), if you build your own vim a workaround is to modify
> > os_unix.c in the x_error_handler function, to replace the
> > preserve_exit() call with
> >
> > g_print("%s", IObuff);
> >
> > or just comment out the preserve_exit() call. I have used this
> > workaround for a BadWindow error for about a decade, with no ill
> > effect.
> >
>
> Sounds like a good idea. But why isn't this changed this way in the
> official vim sources?
This is "not supposed to happen". But there was already a comment that
it might be possible to silently continue.
Let's make it a bit safer by preserving swap files, in case X does
decide to exit or we crash.
In a terminal we can show the message. The comment mentions that in the
GUI, using the X server may fail in the error handler. So we'll not
show the message.
--
hundred-and-one symptoms of being an internet addict:
75. You start wondering whether you could actually upgrade your brain
with a Pentium Pro microprocessor 80. The upgrade works just fine.
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202005091411.049EBvvo010653%40masaka.moolenaar.net.
Re: Format of persistent history undofiles
Brian Lew wrote: > I was wondering if there is any documentation about the format of the > persistent history undofiles generated when the undofile option is set. > > I am looking to read them in programmatically (outside of vim) and noticed > that they are in a binary format. > > Any information would be greatly appreciated! There is no documentation other than the source code. The format is private to Vim, it's not supposed to be used in any other way. However, since existing undo files must be readable by future versions of Vim, they can be expected to be backwards compatible. -- hundred-and-one symptoms of being an internet addict: 26. You check your mail. It says "no new messages." So you check it again. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202004261741.03QHff6X005313%40masaka.moolenaar.net.
Re: removing past start position
> On Wed, Apr 15, 2020 at 08:06:14PM +0200, Bram Moolenaar wrote: > > > > To make CTRL-W delete all text until the start of the file: > > :set bs=7 > > > > To make CTRL_W delete all text you ever wrote: > > :set bs=42 > > > > Intermediate values TBD. > > > > ITYM all the text you ever wrote *up to* the insertion point ;-) Birth. -- ARTHUR: You are indeed brave Sir knight, but the fight is mine. BLACK KNIGHT: Had enough? ARTHUR: You stupid bastard. You havn't got any arms left. "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202004151908.03FJ8PlA014637%40masaka.moolenaar.net.
Re: Question on test_increment_dbcs.vim
Brian Matthews wrote:
> I'm trying to get vim to compile on my Mac running Mojave and it's
> failing. I've grabbed the latest sources:
>
> $ git reset --hard origin/master
> HEAD is now at 4d5d0dfe9 patch 8.2.0579: Coverity warns for unused value
>
> My configure command is:
>
> ./configure --disable-gui --enable-largefile --enable-multibyte
> --enable-pythoninterp --prefix=/usr/local
>
> make succeeds then make test results in:
>
> Executed: 2870 Tests
> Skipped: 33 Tests
> FAILED: 1 Tests
>
>
> Failures:
> From test_increment_dbcs.vim:
> Found errors in Test_increment_dbcs_1():
> function RunTheTest[39]..Test_increment_dbcs_1 line 4: Expected
> ['?R2'] but got ['?S1']
> function RunTheTest[39]..Test_increment_dbcs_1 line 5: Expected [0,
> 1, 3, 0] but got [0, 1, 2, 0]
> function RunTheTest[39]..Test_increment_dbcs_1 line 9: Expected
> ['?`?a?b0xDD?e'] but got ['?`?a?b0xDE?e']
> function RunTheTest[39]..Test_increment_dbcs_1 line 10: Expected
> [0, 1, 10, 0] but got [0, 1, 4, 0]
>
> TEST FAILURE
> make[2]: *** [report] Error 1
> make[1]: *** [scripttests] Error 2
> make: *** [test] Error 2
>
> After studying test_increment_dbcs.vim, it appears it's failing because
> the vim under test isn't recognizing <8e> as "shifting" the next
> character, so in <8e>R1, CTRL-A is incrementing the R (alpha has been
> added to nrformats) as if it's just a regular alphabetical character,
> instead of the 1 (and similarly for the CTRL-X test later in the file),
> while it shouldn't be treating R as alphabetical because the encoding
> has been set to cp932 and it's preceeded by an <8e>.
>
> If I modify the test so it doesn't added alpha to nrformats, it works,
> but for the wrong reason (I think). Does anyone have any idea why it
> might be doing this? For now I've just ignored the failure because it's
> the only one and it's not something I'll ever use (until after I've
> forgotten I've ignored it not working :-) ), but I'd like all the tests
> to actually succeed.
The test sets 'encoding' to "cp932". When you do that, do you get a
warning or error? Vim uses mblen() to decide which bytes start a
double-byte character, perhaps that doesn't work in your case.
We could skip the test if cp932 doesn't work, but we need to detect that
somehow. Perhaps check with strchars()? Can you do this:
:set enc=cp932
:echo strlen("\x8eR")
:echo strchars("\x8eR")
--
Hanson's Treatment of Time:
There are never enough hours in a day, but always too
many days before Saturday.
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/202004151906.03FJ60ml013966%40masaka.moolenaar.net.
Re: removing past start position
Tavis Ormandy wrote: > On Tue, Apr 14, 2020 at 01:44:50PM -0700, Brian L. Matthews wrote: > > > You don't need CTRL-W at all if you don't mind hitting more keys, but > > > since we do have it and configurable behaviour, why not cover all the > > > variations people could want? > > > > While this is more software design philosophy than vim-specific, it's > > because every configurable behavior requires code to parse the new option > > (however minimal), code to use the new option, one or more tests, > > documentation changes, it makes the code that little bit harder to maintain > > and learn, and it makes learning to use the software a little bit harder. If > > the new behavior is significantly better, then yes, why not. I'm not sure if > > this qualifies. > > > If you want software minimalism, you have a ton of editors to choose > from. > > > There's a difference between changing long-existing behavior and adding new > > behavior. Yes, I wouldn't be happy if bs=2 went away, I use that all the > > time (with BS). > > Umm, bs already has three options. Arguing that 3 is the perfect number > seems really odd. Any option that you wouldn't use doesn't make vim > better for you, but it sure does for other people... that's a good thing! > > I happily volunteer any of the options you use that I don't to make the > option counts neutral, how's that ;-) To make CTRL-W delete all text until the start of the file: :set bs=7 To make CTRL_W delete all text you ever wrote: :set bs=42 Intermediate values TBD. -- 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202004151806.03FI6E2A001307%40masaka.moolenaar.net.
Re: removing past start position
Christian wrote: > On Di, 14 Apr 2020, Tavis Ormandy wrote: > > > To be clear, very detailed reproduction steps: > > > > 1. In a new file, write this: > > > > one two three > > > > 2. Enter normal mode, position the cursor after "two" and enter insert > >mode, then type "four". It should look like this: > > > > one twofour three > > > > 3. *before* leaving insert mode, hit CTRL-W. I think it will now look > > like this: > > > > one two three > > > > But I want this: > > > > one three > > Ah got it. That must have been there very long (and I actually like this > behaviour). > > I suppose you want something like this: > > diff --git a/src/edit.c b/src/edit.c > index edd2374e8..5be76db07 100644 > --- a/src/edit.c > +++ b/src/edit.c > @@ -4883,9 +4883,7 @@ ins_bs( > #ifdef FEAT_RIGHTLEFT > revins_on || > #endif > - (curwin->w_cursor.col > mincol > - && (curwin->w_cursor.lnum != Insstart_orig.lnum > - || curwin->w_cursor.col != Insstart_orig.col))); > + curwin->w_cursor.col > mincol); > } > did_backspace = TRUE; > } > > > If you want to have this included into propper vim, we probably need > another CPOPTION value (or backspace value?), to make this configurable > and a test. Yeah, would need another value in 'backspace'. CTRL-W stopping at the insert point has always been the behavior. :set backspace=indent,eol,start,nostop Can't think of a good name for "nostop", could be improved. Or just: :set bs=3 -- Friends? I have lots of friends! In fact, I have all episodes ever made. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202004141823.03EIN9KE025404%40masaka.moolenaar.net.
RE: [EXTERNAL] Re: Mouse not working last 20% of screen
> >> I cannot use the mouse when it is in the last 20% of the screen > > > >I don't want to be a nuisance, but the whole idea of Vim is that you > >only use the keyboard, because it is faster and more precise. > > > >Admit it takes some time to re-train using your computer, but believe > >me: using just Vim keystrokes is the best thing in editing. > > > >//meine > > > Thanks for the suggestion meine! > > I'm old. I'm old school. October of '93 when I started with vim and Linux > there was no > GUI, only the ttys on Alt-F1 - Alt-F7. There was no mouse either as I > usually used my > two serial comports as modem connections (PS2 didn't come out until later and > I couldn't > afford a Cyclades). > > The mouse is useful sometimes. Usually when I'm attempting to scroll one of > the right > windows up or down without moving my cursor from the place I'm at. > > So, yes, I use the keyboard about 90% of the time. > > That other 10% was beginning to bug me ;)! Maybe you have an idea what to do with that pile of punched cards? Somehow I don't have any papertape... :-) -- Ten bugs in the hand is better than one as yet undetected. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202003162009.02GK9Coj019858%40masaka.moolenaar.net.
Re: vim undo
Tim Chase wrote: > On 2020-03-04 13:00, Chris Jones wrote: > > Scenario: > > > > - I open a file > > - I make one big global change (C0)... say via substitute+regex > > - I proceed to make more changes (C1, C2, ... Cn). > > > > While *still editing the file* I realize that the initial change > > (C0) was in error. > > > > Can I undo the initial change (C0) and keep all the ensuing changes? > > > > Or... > > > > Go back to the initial state of the buffer, and make vim reapply > > all the C1-Cn changes? > > > > Standard vim only please, no plugins. > > I don't think there's a native way to play back all the changes as a > rebase. If I had a dire need to do as much, I'd do a little > do/undo/diff/patch tango, something like > > :w current.txt > > then undo to C1 > > :w c1.txt > > then undo once more take you back to the pre-C0 change and save that: > > :w pre-c0.txt > > Then, in the shell > > $ diff -u c1.txt current.txt > rest_of_the_changes.txt > > and run that patch against the pre-c0.txt > > You might be able to use git to checkin various points and then > use its rebasing to help you out. > > But in pure vim? Not much. You can do it without leaving Vim: :w new_version (undo until the big change is undone) :vimdiff new_version (diffget to get the changes you want) If there are overlaps it's more work. If there are many changes then the diff + patch tools might work better, but likely "patch" will find conflicts and it's not good at dealing with those. -- hundred-and-one symptoms of being an internet addict: 175. You send yourself e-mail before you go to bed to remind you what to do when you wake up. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20200304.024MM7du020885%40masaka.moolenaar.net.
Re: combined keys don't work with 8.2
Jacky Liu wrote: > I'm talking about the input mode. I'm using these key mappings to move the > cursor under the input mode: > > inoremap > inoremap > inoremap > inoremap > inoremap > inoremap > > These mappings work perfectly with 8.1, They just move the cursor and don't > change the text. To my surprise, If you press the arrow keys under the input > mode, Then vim would interpret them as the escape-leading sequences and > resulting in the text being changed. > > Now with 8.2 vim would always interpret the arrow keys as the escape-leading > sequences. I think if it's possible to avoid such behaviour with key mappings > (like with 8.1), It surely would be preferable. Please check out ":help modifyOtherkeys". You may have to use something else thatn , perhaps . If you can't figure it out, you can disable modifyOtherkeys and see if it works then. -- "Hit any key to continue" it said, but nothing happened after F sharp. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202003031152.023BqKQW008024%40masaka.moolenaar.net.
Re: Small grammar issue in 'langmap'/'langremap' help
Tim Chase wrote: > Reading the help on 'langmap' today, I encountered this > > Also consider resetting 'langremap' to avoid 'langmap' > applies to characters resulting from a mapping. > > Despite reading this multiple times, I'm not quite sure what this is > trying to say. Confusion includes > > - what does it mean to "reset"? (usually "reset" for a setting means > `set langmap&`, but in this case it defaults to *on*, so resetting > would do the opposite of what is intended). This also applies in > the help for 'langremap' where it says "reset in defaults.vim") Resetting means setting it off. > - the grammar of "applies" is peculiar. > > Maybe something like > > Also consider setting 'nolangremap' to prevent 'langmap' > from applying to characters used in a mapping. How about: Also consider setting 'langremap' to off, to avoid that 'langmap' applies to characters resulting from a mapping. > in the help for 'langmap', and > > boolean (default on, turned off in defaults.vim) > > for the help on 'lrm'. I like to keep "set" in there, since that's the command that is used. "set to off" is less ambiguous, but it doesn't sound very nice. -- hundred-and-one symptoms of being an internet addict: 165. You have a web page burned into your glasses /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202003021955.022Jt9aI008943%40masaka.moolenaar.net.
Vim charity financial results
Hello Vim users, Vim is open source and you can use it for free. But you are encouraged to make a donation for needy children in Uganda. The ICCF Holland foundation collects the money and sends it to the project in Kibaale. Last year had a nice increase in donations. The revenue went up by about 12 percent, compared to 2018. That means we can help 12% more children! I'm also happy that we managed to keep the cost at the same level: only 0.5% of the donations goes into costs, 99.5% goes to Uganda. You can find the financial report here: https://www.iccf.nl/jaarrekening2019en.pdf And the Dutch version: https://www.iccf.nl/jaarrekening2019nl.pdf A big thanks to all who helped! -- "A clear conscience is usually the sign of a bad memory." -- Steven Wright /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202002252124.01PLOrYm019368%40masaka.moolenaar.net.
Re: Retrive old inserts
Alessandro Falcione wrote: > I wrote something in a file and then accidentally removed the file, is > there any possibility to retrive what I've inserted in that file? Check for any backup file (ending in ~), in the directory of the ile or 'backupdir'. Check for an undo file, ending in .un~. -- hundred-and-one symptoms of being an internet addict: 87. Everyone you know asks why your phone line is always busy ...and you tell them to send an e-mail. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202002152208.01FM8MMe020415%40masaka.moolenaar.net.
Re:How about dropping the MzScheme interface?
> >So, who would complain if we drop the MzScheme interface? > >Please reply to the vim-use and/or vim-dev maillist. > > I would. It is the only interface I use myself. OK, that is good to know. Is this with scripts you only write for yourself, or something you publish? -- For humans, honesty is a matter of degree. Engineers are always honest in matters of technology and human relationships. That's why it's a good idea to keep engineers away from customers, romantic interests, and other people who can't handle the truth. (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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202001261757.00QHvNWp019746%40masaka.moolenaar.net.
How about dropping the MzScheme interface?
Over time many features have been added to Vim. Currently I'm looking into making Vim script faster, which will eventually lead to Vim9 script (faster, better, etc.). Besides adding more, we should also consider dropping functionality that hardly anyone uses. I'm careful with that, I like to support even a small group of users. That is why I'm asking here. Vim provides optional built-in interfaces for several languages. Out of these Python is clearly the most popular. It looks like the MzScheme interface is the least popular. It doesn't even build on most systems and requires compiling racket from source. The code itself has not had changes, other than refactorings, for two years. Note that I'm not talking about editing Scheme or Racket code with Vim, that will still be possible. It's about the :mzscheme and :mzfile commands. So, who would complain if we drop the MzScheme interface? Please reply to the vim-use and/or vim-dev maillist. -- "You're fired." (1980) "You're laid off." (1985) "You're downsized." (1990) "You're rightsized." (1992) (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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202001242021.00OKLweB015845%40masaka.moolenaar.net.
Re: set all - each option one line
Andy Wokula wrote: > Am 15.01.2020 um 22:22 schrieb Erhy: > > Hello! > > I want to compare the options set in VIM. > > > > Do you know, how to format of set all output > > that I have *for each option a separate line *? > > > > Thank you for tips > > Erhy > > Apparently > :set > always (?) produces multi-column output. > (sounds like one of those little annoyances that others didn't bother > to ask for years) How about ":set!" only using one column? Currently ! isn't used and I can't think of anything we would want to use it for when listing options. > You could redirect to a buffer with very small temporary 'columns' > setting (at least 12), but that's awful. > > Or :substitute the (redirected) multi-column output to get single column > output: > > :%s/ \+\ze\%(no\l\+\%(\s\|$\)\| \S\)/\r/gIe > > Obviously the problem is how to not split within option values. > My example output (not given here) shows a statusline with spaces and > these don't appear escaped, so one just cannot skip escaped spaces -- > just make it a bit more unlikely to split there. -- 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202001171839.00HIdRQO010196%40masaka.moolenaar.net.
Re: Vim logo tatoo
Albie Janse van Rensburg wrote: > On Tuesday, January 14, 2020 at 1:12:01 PM UTC+2, Bryan Tidwell wrote: > > > > Hello fellow Vimmers, > > > > I know this is an unusual question, but am I allowed by copyright law to > > get a tatoo of the vim logo? > > -- > > Thanks, > > Bryan > > > > A quick web search for "tattoo legal logo" revealed this Quora discussion > (https://www.quora.com/Can-I-legally-get-myself-tattooed-with-a-trademarked-logo). > > Maybe you will find it of use. > > I believe the Vim logo is governed by the GPL (at least, the wikipedia page > seems to think so. See https://en.wikipedia.org/wiki/File:Vimlogo.svg), so > you yourself may virally become GPL as well. A logo is not code thus the GPL doesn't really work. I definitely hope no virus is involved! It's fine to use the Vim logo for the good of Vim. So using it for a tattoo on a normal body part is allowed. Not so much on buttocks. -- MICHAEL PALIN PLAYED: 1ST SOLDIER WITH A KEEN INTEREST IN BIRDS, DENNIS, MR DUCK (A VILLAGE CARPENTER WHO IS ALMOST KEENER THAN ANYONE ELSE TO BURN WITCHES), THREE-HEADED KNIGHT, SIR GALAHAD, KING OF SWAMP CASTLE, BROTHER MAYNARD'S ROOMATE "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/202001141531.00EFV8ej010762%40masaka.moolenaar.net.
Re: automatic redraw for multi-line syntax highlighting patterns
> the docs state (:help syn-multi-line) that syntax highlighting with > multi-line patterns "mostly works as expected". I am not sure if this > "mostly" includes automatic highlighting change of a multi-line syntax > group when it's modified. Especially as soon as the pattern's end is > destroyed. For example, take the commands of a session file ~/tmp/s.vim: > > call append(0, ['( comment?', ')'])syntax sync fromstarthi link m > Commentsyntax match m /(.*\n)/ > > They give us two lines highlighted as a comment (:hi Comment): > > ( comment?) > > Now, let's change the ')' into an 'x' via "2gg0rx". The test in the two > lines does not match the defined syntax group anymore. But the display does > not reflect this change right away. Instead I get something that's > displayed partly as a comment (line 1) and partly as normal text (line 2): > > ( comment?) > > Note the different color of the two parentheses. I have to press CTRL-L to > see the comment highlighting disappear completely. Having set syntax > syncing to start from the very start of the file I would expect this to > happen automatically. Is this imperfection the reason why the help says > "mostly works" instead of "always works"? Or am I missing something? > > This is Vim 8.1.2337 (Huge version with GTK2 GUI) on Debian GNU/Linux, > started with: > vim --clean -S ~/tmp/s.vim > > Thanks in advance for all your insights, When the text changes Vim by default assumes only that line needs to be updated for syntax highlighting. In other words: the cached syntax state at the start of the line is assumed to be valid. If there are multi-line patterns, the sync mechanism needs to take care of any syntax items where more state becomes invalid. The extreme version is to use "syn sync fromstart". See ":help syn-sync". -- ARTHUR: Be quiet! DENNIS: --but by a two-thirds majority in the case of more-- ARTHUR: Be quiet! I order you to be quiet! WOMAN: Order, eh -- who does he think he is? ARTHUR: I am your king! 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/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912282157.xBSLvhPG001161%40masaka.moolenaar.net.
Vim calendar for 2020 available
Happy New Year to all Vim users! 2019 was a good Vim year with a few new features, many bug fixes and improved test coverage. This is included in the recent 8.2 release, which went out smoothly. For the coming year the main goal is to improve the execution speed of Vim script. I have started experimenting with some ideas, and it looks hopeful. An increase of 10 to 100 times can be expected. More about that soon. I have updated the handy desktop calendar for 2020. It prints on one sheet of paper and, after folding and applying a bit of glue, stands on your desk. It is available in English and Dutch. You can find the PDF files on my website: https://moolenaar.net/#Calendar Happy Vimming! -- FATHER:Did you kill all those guards? LAUNCELOT: Yes ... I'm very sorry ... FATHER:They cost fifty pounds each! "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912231705.xBNH55sD015131%40masaka.moolenaar.net.
Re: Vim 8.2 on OpenBSD
Johannes Degen wrote: > I noticed OpenBSD was missing from the OS's where building Vim's latest > installment were tested. I can confirm it builds without any problems on > two of my machines running recent snapshots of OBSD 6.6. > After years of just going with the binaries I'm an even happier Vimmer. Perhaps OpenBSD can be tested on Cirrus? https://cirrus-ci.com/github/vim/vim This currently uses https://github.com/vim/vim/blob/master/.cirrus.yml Hmm, it seems they only support FreeBSD. -- Edison's greatest achievement came in 1879, when he invented the electric company. Edison's design was a brilliant adaptation of the simple electrical circuit: the electric company sends electricity through a wire to a customer, then immediately gets the electricity back through another wire /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912141625.xBEGPwmo018555%40masaka.moolenaar.net.
Re: syntax highlighting for IPv6 in resolv.conf (resolv.vim)
> I now understand those two other two entries. If I would have looked at > them for a few more seconds. :-) Wish I would have gotten this in before > 8.2. At any rate, this should be good to go in. What's the preferred method > to submit a patch (if even required for such a simple change)? You can send me the new version of the file. Please update the header, changing "Maintainer" to "Previous Maintainer" and adding yourself as the maintainer. Thanks for updating this syntax file. -- hundred-and-one symptoms of being an internet addict: 10E. You start counting in hex. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912141217.xBECHuSE024733%40masaka.moolenaar.net.
Re: Vim 8.2 is released!
Christian wrote: > On Fr, 13 Dez 2019, Bram Moolenaar wrote: > > > So should I still hold off on adding patches? > > > > Can you somehow make the automatic job run more often? > > No, I would say just keep on and don't let yourself hold off by the > failing build script. Since there are no changes, to the vim repository, > the ci build won't try to build new releases. > > I hope the build will start soon again, (I just tried again, and it is > still failing). If it doesn't work by monday, I'll go ahead and disable > racket in the build) Racket hasn't worked for me for quite a while. Looks like the only way is to get the sources and build that. I don't think any users require this interface. -- hundred-and-one symptoms of being an internet addict: 265. Your reason for not staying in touch with family is that they do not have e-mail addresses. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912131536.xBDFaWFn008093%40masaka.moolenaar.net.
Re: Vim 8.2 is released!
Christian - > On Do, 12 Dez 2019, Bram Moolenaar wrote: > > > Announcing: Vim (Vi IMproved) version 8.2 > > Congratulations! > > > Signed versions will appear soon at: > > https://github.com/vim/vim-win32-installer/releases > > For some reason, the automatic job failed today because of a download > timeout when trying to download the racket dependencies. I tried to > manually trigger a build, but that fails again every time. > > I can download it locally fine, so not sure what problem Appveyor has. > Hopefully this is just a hickup, that goes away. So should I still hold off on adding patches? Can you somehow make the automatic job run more often? - Bram -- hundred-and-one symptoms of being an internet addict: 264. You turn to the teletext page "surfing report" and are surprised that it is about sizes of waves and a weather forecast for seaside resorts. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912131257.xBDCvQss008890%40masaka.moolenaar.net.
Vim 8.2 is released!
ypes. Plugins are the main audience for the popup window feature, there are many options to change the positioning, size and highlighting. Gratitude - If you like Vim, please consider helping poor children in the south of Uganda: http://iccf-holland.org Where to get it --- The best way to obtain the latest Vim is using Git. Summary: git clone https://github.com/vim/vim.git More information here: https://www.vim.org/git.php For MS-Windows most of you will want the self-installing executable: https://ftp.nluug.nl/pub/vim/pc/gvim82.exe Signed versions will appear soon at: https://github.com/vim/vim-win32-installer/releases Information about which files to download for what system: https://www.vim.org/download.php A list of mirror sites can be found here: https://www.vim.org/mirrors.php Files available for download: UNIX: sources + runtime files, bzip2 compressed: https://ftp.nluug.nl/pub/vim/unix/vim-8.2.tar.bz2 VARIOUS: help files converted to HTML: https://ftp.nluug.nl/pub/vim/doc/vim82html.zip MS-WINDOWS one-size-fits-all: Self-installing, includes all runtime files, loads libraries dynamically: https://ftp.nluug.nl/pub/vim/pc/gvim82.exe MS-WINDOWS separate files: Runtime files: https://ftp.nluug.nl/pub/vim/pc/vim82rt.zip GUI binary for Windows NT/2000/XP/7/8/10: https://ftp.nluug.nl/pub/vim/pc/gvim82.zip GUI binary with OLE support: https://ftp.nluug.nl/pub/vim/pc/gvim82ole.zip Console version for Windows NT/2000/XP/7/8/10: https://ftp.nluug.nl/pub/vim/pc/vim82w32.zip Sources for PC (with CR-LF): https://ftp.nluug.nl/pub/vim/pc/vim82src.zip For debugging: https://ftp.nluug.nl/pub/vim/pc/gvim82.pdb https://ftp.nluug.nl/pub/vim/pc/gvim82ole.pdb https://ftp.nluug.nl/pub/vim/pc/vim82w32.pdb AMIGA: Only runtime and sources are provided, no binary: https://ftp.nluug.nl/pub/vim/amiga/vim82rt.tgz https://ftp.nluug.nl/pub/vim/amiga/vim82src.tgz Omitted in this version are: - The 16-bit DOS, OS/2 and Amiga versions, these are obsolete. - The 32-bit console version for MS-DOS/Windows 95/98 Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See https://www.vim.org/maillist.php#vim If you want to help Vim development, discuss new features or get the latest patches, subscribe to the vim-dev mailing list. See https://www.vim.org/maillist.php#vim-dev Subject specific lists: Macintosh issues: https://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Create an issue at github and/or a pull request: https://github.com/vim/vim Alternatively send your problem to . Please describe the problem precisely. Try to write a test that reproduces the problem and will pass once it is fixed. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: "vim -u NONE". Try different machines if possible. See ":help bugs" in Vim. Happy Vimming! -- INSPECTOR END OF FILM: Move along. There's nothing to see! Keep moving! [Suddenly he notices the cameras.] INSPECTOR END OF FILM: (to Camera) All right, put that away sonny. [He walks over to it and puts his hand over the lens.] "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912121508.xBCF80JL011280%40masaka.moolenaar.net.
Re: Vim executable for Windows updated
Christian wrote: > > On Mo, 09 Dez 2019, Bram Moolenaar wrote: > > > > > Is that possible for the gvim.exe that I create? Or do we need to pick > > > the right one from your site? I'm sure many users would prefer a signed > > > binary. Not sure if it runs everywhere, e.g. on Windows XP? That's why > > > I have been using MSVC 2015. > > > > Let me check. > > I checked it out, it seems only possible, if you build using appveyor. > So it is no option currently. Hmm, then let me build the executable and roll out the first 8.2 build. Once you have created a build (and checked that it works), we can also mention it on the download page as "signed version" and mention the other one as an alternative. -- hundred-and-one symptoms of being an internet addict: 248. You sign your letters with your e-mail address instead of your name. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912111835.xBBIZLsh005103%40masaka.moolenaar.net.
Re: "Press ENTER" prompt when edit file with long path
On 2019-12-11, Gary Johnson wrote: > > On 2019-12-10, J. Lewis Muir wrote: > > > Hello! > > > > > > In an 80-column terminal, when I invoke vim on an existing empty file > > > with a name that is 56 'x' characters, it displays the following prompt > > > before I can edit the file: > > > > > > > > > "" 0 lines, 0 > > > characters > > > > > > Press ENTER or type command to continue > > > > > > > > > How can I stop it from doing that? > > > > > > NOTE: The file has to exist for it to do this. If it's a new file that > > > Vim will create, Vim does not show the prompt. > > > > This looks like a new bug. The presence of the 't' flag in the > > 'shortmess' option should prevent this, and that flag is there by > > default. I just verified that it used to work in 7.4.1689 and > > 8.0.1453 but is now broken in my 8.1.2352 (on Linux) as well as your > > 8.1.2400. > > I used git bisect and tested with > > $ src/vim -N -u NONE > ../xxxx > > where the file had already been created, to determine that the > commit that introduced this bug was: > > 473952e85286eb9c6098801f1819981ba61ad153 is the first bad commit > commit 473952e85286eb9c6098801f1819981ba61ad153 > Author: Bram Moolenaar > Date: Sat Sep 28 16:30:04 2019 +0200 > > patch 8.1.2094: the fileio.c file is too big > > Problem:The fileio.c file is too big. > Solution: Move buf_write() to bufwrite.c. (Yegappan Lakshmanan, > closes #4990) > > :100644 100644 2d05b4a3af6a96a04f446789b5c9ca69ab905e9c > dfc06245e585e883459dfa04416addce91d3d8ce M Filelist > :04 04 506a68f58e09932cd2b29e2f3eaec5e16e197a9f > b5166a4265c3536326785a13e29336e7f778448a M src I don't think it is related to that CL. The problem appears to be in msg_puts_display(). When outputting the CR it thinks the text is going to wrap, but it won't. -- hundred-and-one symptoms of being an internet addict: 245. You use Real Audio to listen to a radio station from a distant city rather than turn on your stereo system. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912111801.xBBI1BCb031040%40masaka.moolenaar.net.
Re: Vim executable for Windows updated
Christian wrote: > On Sa, 07 Dez 2019, Bram Moolenaar wrote: > > > As a tryout for the upcoming Vim 8.2 release I created an MS-Windows > > self-installing binary from the current Vim version. This should be > > very close to the Vim 8.2 release. Give it a try. > > > > This uses the new Windows installer, which is nicer than the old one. > > It also has translations for a few languages. > > > > You can download it from here: > > https://ftp.nluug.nl/pub/vim/pc/gvim81.exe > > > > You can find the individual zip archives with runtime files and three > > versions of the executable in the same directory. See the README file > > for what is in which archive: > > https://ftp.nluug.nl/pub/vim/pc/README > > > > Let me know if you run into any trouble, we want to make sure the Vim > > 8.2 release doesn't have any problems. > > I think it would be nice, if we could sign the resulting official > installer. Is that possible for the gvim.exe that I create? Or do we need to pick the right one from your site? I'm sure many users would prefer a signed binary. Not sure if it runs everywhere, e.g. on Windows XP? That's why I have been using MSVC 2015. -- "The amigos also appear to be guilty of not citing the work of others who had gone before them. Even worse, they have a chapter about modeling time and space without making a single reference to Star Trek!" (Scott Ambler, reviewing the UML User Guide) /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912092210.xB9MAG20006856%40masaka.moolenaar.net.
Re: Vim executable for Windows updated
Rob Solumon wrote: > I've been using gvim for windows 10 installed from gvim_8.1.0451_x86.exe > since that came out. That was the first version that fixed the bug in > vim (non-gui mode) in which and were not recognized. > > That has worked fine for me. > > At Bram's request, I installed gvim_8.1.2410_x64.exe and _x86.exe. Both > versions of vim (non-gui) are not compatible with Take Command console > program by JPSoft.com. I have been using some version of take command > for 25+ years. > > There is an incompatibility w/ take command and the latest windows > version of non-gui vim. > > The display is unstable, jumping more often than 2 per second (I > think). The prompt line appears midway in the screen. I am able to > blindly issue :q and it quits. > > I reverted to the version that works for me, ie, 8.1.0451_x86. > > > Thought you'd want to know. > > FWIW, I also reported this to Rexx Conn of JPSoft.com, who is the > principal programmer and owner (I think). This might be related to the changes done to support the new console stuff, VTP and ConPTY. I'll CC Nobuhiro. -- hundred-and-one symptoms of being an internet addict: 233. You start dreaming about web pages...in html. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912091141.xB9BffvR015587%40masaka.moolenaar.net.
Vim executable for Windows updated
As a tryout for the upcoming Vim 8.2 release I created an MS-Windows self-installing binary from the current Vim version. This should be very close to the Vim 8.2 release. Give it a try. This uses the new Windows installer, which is nicer than the old one. It also has translations for a few languages. You can download it from here: https://ftp.nluug.nl/pub/vim/pc/gvim81.exe You can find the individual zip archives with runtime files and three versions of the executable in the same directory. See the README file for what is in which archive: https://ftp.nluug.nl/pub/vim/pc/README Let me know if you run into any trouble, we want to make sure the Vim 8.2 release doesn't have any problems. -- How do I set the laser printer to stun? /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201912071958.xB7JwVUD027134%40masaka.moolenaar.net.
Re: Mapping erases search count message
t that using nmap (not nnoremap) to map
> n to a rhs including n would cause an infinite recursion, but it
> doesn't.
>
> Those mappings solve part of the problem. That is, if AdjCursor()
> is an empty function, they work fine--the search count message is
> always visible. But if AdjCursor() is the actual function (which
> scrolls the window when needed to keep the cursor at least two lines
> from the top and bottom), then whenever the window is scrolled, the
> message disappears.
>
> In fact, removing all the mappings and just executing Ctrl-E or
> Ctrl-Y to scroll the window after a search erases the search count
> message. I think that's a bug. I can see no reason why scrolling
> should erase that message unless scrolling moves the cursor.
>
> Further, certain motion commands such as j, k and gg _don't_ erase
> the search count message, even though it would make sense for them
> to do so. It's weird to jump from the bottom of a buffer to the top
> with gg and still see the last search count message in the command
> line.
>
> The purpose of AdjCursor () is to scroll the window after a search
> moves the cursor near the top or bottom of the window so as to
> provide at least two lines of context around the cursor. (It should
> really be named AdjWindow().) It behaves like scrolloff=2, but only
> after certain commands. I don't want 'scrolloff' on all the time.
>
> That gave me an idea, a different solution to the problem:
> temporarily enable 'scrolloff' instead of scrolling the window.
> Here is what I just came up with and it seems to work well.
>
> nmap n :call ScrolloffCmd('n')
> nmap N :call ScrolloffCmd('N')
> function! ScrolloffCmd(cmd)
> set scrolloff=2
> try
> exe 'normal!' a:cmd
> catch
> echohl ErrorMsg
> echomsg matchstr(v:exception, ':\zs.*')
> echohl NONE
> endtry
> set scrolloff=0
> endfunction
Looking through older problems...
I tried the example with remapping "n", but it works OK for me.
Was this problem fixed already? Or is only that example fixed and there
a remaining problem?
--
FIXME and XXX are two common keywords used to mark broken or incomplete code
not only since XXX as a sex reference would grab everybody's attention but
simply due to the fact that Vim would highlight these words.
-- Hendrik Scholz
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/201911232215.xANMFexv031914%40masaka.moolenaar.net.
Re: How to use "tail -f" in Vim's 8.1 :terminal command window?
Brian Matthews wrote:
> On 11/23/19 10:12 AM, Matteo Landi wrote:
> > Did you try the same, tail - f, but from outside vim?
> >
> > If not wrong, vim is dumping the whole buffer to the file on save
> (not 'appending' new content) so I wouldn't be surprised it tail - f did
> not work because of it.
> >
>
> And I think by default vim renames the current file then writes to a
> completely new file, so the file you're tailing never changes, in fact
> it gets deleted. You can modify that behavior with various options
> (backup, writebackup, backupcopy). I got tail -f to show something by
> setting nobackup (which is the default) and nowritebackup (which isn't),
> then modifying a file I was tailing. Because of the way tail works, this
> would only do something useful if you're just adding lines to the file,
> but it does work.
It works fine for me. It might indeed depend on the value of
'backupcopy'.
--
Nobody will ever need more than 640 kB RAM.
-- Bill Gates, 1983
Windows 98 requires 16 MB RAM.
-- Bill Gates, 1999
Logical conclusion: Nobody will ever need Windows 98.
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/201911232058.xANKw3BP020260%40masaka.moolenaar.net.
Re: Are the --enable-hangulinput and --enable-xim confilct?
Namsh wrote: > >> 2019-08-25 오후 2:25에 Hongyi Zhao 이(가) 쓴 글: > >>> Hi, > >>> > >>> I try to build vim with the --enable-hangulinput and --enable-xim > >>> confilct at the same time, but failed with error: > >>> > >>> - > >>> vim.h:1585:63: error: called object ‘size_t’ is not a function or > >>> function pointer > >>>#define STRNCMP(d, s, n)strncmp((char *)(d), (char *)(s), > >>> (size_t)(n)) > >>> ^ > >>> ex_docmd.c:8459:6: note: in expansion of macro ‘STRNCMP’ > >>> if (STRNCMP(arg, "FALLBACK ", 9) == 0) > >>> ^~~ > >>> In file included from /usr/include/wchar.h:887:0, > >>>from spell.h:250, > >>>from vim.h:2110, > >>>from ex_docmd.c:14: > >>> /usr/include/x86_64-linux-gnu/bits/wchar2.h:507:20: note: declared here > >>>__fortify_function size_t > >>> ^~ > >>> Makefile:3059: recipe for target 'objects/ex_docmd.o' failed > >>> make[1]: *** [objects/ex_docmd.o] Error 1 > >>> make[1]: Leaving directory '/home/werner/software/editor/vim/vim.git/src' > >>> Makefile:26: recipe for target 'first' failed > >>> make: *** [first] Error 2 > >>> - > >>> > >>> Are these two options conflict? > >> > >> Regardless of compilation error, the hangulin feature is for > >> environments where XIM is not available. > >> > >> You can find next line with ':help hangul'. > >>./configure --with-x --enable-multibyte --enable-hangulinput \ > >> --disable-xim > > > > That's a bit of a disadvantage when someone tries to build a version > > that works with multiple languages. Can we make this a runtime choice > > instead of a compile time choice? No idea how much work that would be. > > Here is a minimal patch (no documentation, no indenting to minimize). > If vim supports both xim and hangulinpt and user set 'imdisable', > hangulinput feature is selected. > > I tested this patch by adding '--enable-xim --enable-hangulinput' to my > default configure option. >$ auto/configure --enable-perlinterp=no --disable-gpm > --enable-python3interp=dynamic --enable-tclinterp=no --enable-cscope > --with-features=huge --enable-terminal --enable-multibyte --enable-xim > --enable-hangulinput --prefix=/opt/local --with-x --enable-gui=gtk3 > > While testing this patch, I noticed one glitch. > Though I set 'imdisable' in the vimrc and I confirmed the setting with > ':set imdisable?', when I typed S-Space for the first time, vim connects > to XIM. After that, go to english input mode and type S-Space again, vim > enters to hangulinput mode. My system environement may cause this glitch?? Now that I try this patch I notice that hangulin.c doesn't build. Since nobody complained and this input method is unmaintained, let's just remove it. I hope someone can re-implement this for utf-8 encoding. -- hundred-and-one symptoms of being an internet addict: 98. The Alta Vista administrators ask you what sites are missing in their index files. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911211546.xALFkrp9004253%40masaka.moolenaar.net.
Re: Un-POSIX-like behavior of join command
I wrote: > Brennan Vincent wrote: > > > When joining a line that is followed by an empty line (or one with only > > spaces), POSIX specifies that it should be deleted without the current > > line being affected. See the section "Join" in > > https://pubs.opengroup.org/onlinepubs/9699919799/ . > > > > However, vim appends a space to the current line in this case. For > > example, if line 1 is "foo", and line 2 is blank, after executing :1j > > line 1 will be "foo ", as can be seen by executing the following (`ex` > > is provided by `vi` on my system) > > > > $ echo -e 'foo\n' > test.txt && echo -e '1j\nwq' | ex test.txt && wc -c > > test.txt > > 5 test.txt > > > > nvi/nex give the POSIX behavior: > > > > $ echo -e 'foo\n' > test.txt && echo -e '1j\nwq' | nex test.txt && wc -c > > test.txt > > 4 test.txt > > > > Is this a bug, or intentional? > > I can't think of a reason why it works this way. And the trailing space > is useless. So we should call it a bug. > > What should happen if the second line is blank, not empty? The spec apparently says that blank lines are also not resulting in a trailing space: 1. Discard leading characters from the line to be joined. 2. If the line to be joined is now empty, delete it, and skip steps 3 through 5. -- hundred-and-one symptoms of being an internet addict: 78. You find yourself dialing IP numbers on the phone. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911121926.xACJQwXE009034%40masaka.moolenaar.net.
Re: Un-POSIX-like behavior of join command
Brennan Vincent wrote: > When joining a line that is followed by an empty line (or one with only > spaces), POSIX specifies that it should be deleted without the current > line being affected. See the section "Join" in > https://pubs.opengroup.org/onlinepubs/9699919799/ . > > However, vim appends a space to the current line in this case. For > example, if line 1 is "foo", and line 2 is blank, after executing :1j > line 1 will be "foo ", as can be seen by executing the following (`ex` > is provided by `vi` on my system) > > $ echo -e 'foo\n' > test.txt && echo -e '1j\nwq' | ex test.txt && wc -c > test.txt > 5 test.txt > > nvi/nex give the POSIX behavior: > > $ echo -e 'foo\n' > test.txt && echo -e '1j\nwq' | nex test.txt && wc -c > test.txt > 4 test.txt > > Is this a bug, or intentional? I can't think of a reason why it works this way. And the trailing space is useless. So we should call it a bug. What should happen if the second line is blank, not empty? -- hundred-and-one symptoms of being an internet addict: 77. The phone company asks you to test drive their new PBX system /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911121912.xACJC0wr001498%40masaka.moolenaar.net.
Re: CTRL-P broken in version 8.1.2267
> add following to .vimrc to fix this issue > > let &t_TI = "" > let &t_TE = "" It should work without this. And it does for me. Thus I'm still wondering why it fails for you. -- Well, you come from nothing, you go back to nothing... What have you lost? Nothing! -- Monty Python: The life of Brian /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911081550.xA8Fok2K010871%40masaka.moolenaar.net.
Re: CTRL-P broken in version 8.1.2267
> I have do following test on debian 10 > 1. Xterm v 350 and v330 , with vim 8.1.2267. > CTRL P can't work as expected > 2. Xtrem v350 and v330, with vim 8.1.2111 , > CTRL P can works as expected > 3. vim 8.1.2111 and 8.1.2267 can works as expected in gnome terminal > 4. vim 8.1.2111 and 8.1.2267 can works as expected in native framebuffer > console I just installed xterm 350 and it works fine for me. With 'noesckeys' and with 'esckeys'. -- It was recently discovered that research causes cancer in rats. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911072157.xA7LvPjs005448%40masaka.moolenaar.net.
Re: CTRL-P broken in version 8.1.2267
Marius Gedminas wrote: > On Wed, Nov 06, 2019 at 10:58:13PM -0800, WU RUXU wrote: > > 1. Debian Linux > > 2. Console mode > > 3. xterm-250 > > 4. vim in INSERT mode, after user press CTRL-P , should be active keyword > > completion. > > > > When I vim 8.0, this feature is work very well, but vim 8.1.2267, I found > > that > > this feature is broken > > > > In INSERT mode, after I press CTRL-P , vim cann't active keyword completion > > Does this affect only Ctrl-P or every Ctrl-letter key? You can test by > pressing Ctrl-V Ctrl-A and you should see ^A inserted. > > This might be related to xterm's modifyOtherKeys support added in recent > Vim versions. > > (I'm not entirely sure how modifyOtherKeys work as I don't use xterm > myself. Does one have to enable it via ~/.Xresources or does vim detect > an xterm and enable it automatically via magic OSI sequences?) Vim uses t_TI and t_TE to enable and disable modifyOtherKeys. They are set from the builtin xterm termcap. Most xterm versions support it, very old ones should ignore the codes. When the terminal is not actually an xterm (screen, tmux, etc.) it should ignore the codes, but we can't be sure about that. -- I wonder how much deeper the ocean would be without sponges. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911071518.xA7FIU8W024765%40masaka.moolenaar.net.
Re: CTRL-P broken in version 8.1.2267
> I have do following test on debian 10 > 1. Xterm v 350 and v330 , with vim 8.1.2267. > CTRL P can't work as expected > 2. Xtrem v350 and v330, with vim 8.1.2111 , > CTRL P can works as expected > 3. vim 8.1.2111 and 8.1.2267 can works as expected in gnome terminal > 4. vim 8.1.2111 and 8.1.2267 can works as expected in native framebuffer > console Check: verbose set t_TI verbose set esckeys? You might work around it by settint t_TI and t_TE to empty (and running a shell command, e.g.. :!ls). -- You have the right to remain silent. Anything you say will be misquoted, then used against you. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201911071518.xA7FIVYT024771%40masaka.moolenaar.net.
Re: Help about missing mails
Christian wrote: > I just received a help request from a subscriber of this list, who > doesn't receive mails anymore. Looking into the groups admin page, > showed his mail address being flagged as "undeliverable" yesterday, but > today it isn't flagged anymore and looks good. So theoretically, google > should try to deliver to his account. However he doesn't see any > attempts in his MTA logs that a delivery attempt from google is made. > > There is https://support.google.com/a/topic/1262452 but that does not > mention the particular problem here. I am out of ideas here and since > the google groups interface changed a couple of months ago, it doesn't > seem to be possible to get into contact with google itself. It wants me > to sign up for G Suite Admin account (which costs money) before I can > get support. > > So to make a long story short, does anybody here knows a personal > contact to google support that could help us resolve this issue here? Most likely that's not going to help. I guess what happened is that the mail server could not be found. I have seen DNS flakiness in the past. -- If you only have a hammer, you tend to see every problem as a nail. If you only have MS-Windows, you tend to solve every problem by rebooting. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201910161207.x9GC7GLT004956%40masaka.moolenaar.net.
Re: sed whole file
Jorge Almeida wrote: > I just noticed an obnoxious behaviour that I think is a new "feature". > Or maybe it was always like this and I forgot. Or maybe I did > something wrong, in which case I apologize in advance. > > It goes like this: > I want to replace each occurrence of "foo" by "bar". In command mode I > start typing > :%s/foo > > and the cursor moves to the first occurrence of foo, even if it means > moving the page down. Maybe the user would like to copy something in > the original page? Maybe that's where the string "bar" occurs and the > user didn't memorize it? > > Please help me to restore a sane behaviour You can reset 'incsearch'. Perhaps we could go back to the original view when typing the search separator. So long as the user is typing the search pattern it is useful to show the match, but when typing ":%s/foo/", thus starting to type the replacement, it is useful to jump back? I actually cannot guess if the user wants to see the original text or the context of what is going to be replaced. If you have something specific, you can copy it beforehand. And the jumping around can be annoying. Thus I rather leave it like it is. -- Save the plankton - eat a whale. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201910061025.x96APKFo032403%40masaka.moolenaar.net.
Re: Vim crashes when executing system()
Salman wrote: > I upgraded my GVim on Windows 10 to 8.1-2102 yesterday and now every call > to system() crashed Vim. The command line just says,"Segmentation Fault" > with no other details. > > This is new and happens even when started with -u NONE -U NONE. What was the version when it was still working? What is 'shell' set to? And other related options: set shell? set shellpipe? set shellcmdflag? set shellquote? set shellredir? set shellslash? set shelltemp? set shellxescape? set shellxquote? -- ARTHUR:I command you as King of the Britons to stand aside! BLACK KNIGHT: I move for no man. 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/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201909301940.x8UJengC030856%40masaka.moolenaar.net.
Re: What happened to "Search hit BOTTOM, continuing at TOP"?
> Speaking of this " W' indicator, why was it chosen to _add_ it to the > '[N/M]' string instead of _prepending_ "W " before one? > > The point is, if _appended_, then at the moment of wrapping, the expected > position of '[N/M]' changes slightly to the left, which isn't exactly nice > (like, why the information is jumping in front of our eyes, etc). While if > _prepended_, the counter itself stays exactly where it was, and only this > sign "W" appears on the left. Don't know if I'm right or wrong here but I > personally certainly like the prepended option better. > > If you agree, then here's a patch for src/search.c, which seems to fix it > (I'm not a programmer, I also don't know ANYTHING about C at all, and these > few lines here may be completely wrong and stupid, so, please, feel > absolutely free to change it if needed): > > > 5014c5014,5017 > < STRCPY(t + len, " W"); > --- > > char t_tmp[len + 2]; > > STRCPY(t_tmp, t); > > STRCPY(t + 0, "W "); > > STRCPY(t + 2, t_tmp); > I like it. No need to send a patch. -- hundred-and-one symptoms of being an internet addict: 199. You read this entire list of symptoms, looking for something that doesn't describe you. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201909061840.x86IeeuF023010%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian wrote: > On Mi, 04 Sep 2019, Bram Moolenaar wrote: > > > Hmm, since nobody runs the tests manually that doesn't help much. > > How about using a screendump? That makes these things a lot easier to > > write. > > Okay, how about the attached patch then? That fails with v8.1.1965 and > should work with v8.1.1970 Yes, this works, thanks! -- hundred-and-one symptoms of being an internet addict: 178. You look for an icon to double-click to open your bedroom window. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201909041433.x84EX3AW000703%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian wrote:
> > > > > On Fr, 30 Aug 2019, Bram Moolenaar wrote:
> > > > >
> > > > > > Thanks. Yes, I think we should do this. But the allocation should
> > > > > > probably be done differently, it looks like with cmd_silent set it
> > > > > > still
> > > > > > computes the size of the command. This will require some more "if"
> > > > > > statements, but makes the size computation more accurate.
> > > > >
> > > > > Well, yeah I thought this wouldn't hurt.
> > > > >
> > > > > So how about the attached patch then? It will simply use all
> > > > > available
> > > > > space in the command line. Not sure this is correct however.
> > > >
> > > > It's tricky with all the conditions. But it looks OK. All tests pass.
> > > > Let's include this and check that nothing goes wrong. Can we cover this
> > > > with a test?
> > >
> > > Apologizes, the last patch was wrong and caused a strtrunc message
> > > ('...')
> > >
> > > Perhaps we don't even need the added condition `|| cmd_silent` at all?
> > >
> > > Here is a fix including a test.
> >
> > Thanks. The test doesn't fail without the fix though.
>
> Yeah, I did not update the test, I tried, but the message is not
> truncated when running the test. I think this happens because the output
> of `execute()` is actually scrolled. Not sure.
>
> This patch should do it, but only works when run interactively.
>
> diff --git a/src/testdir/test_search_stat.vim
> b/src/testdir/test_search_stat.vim
> index f23952915..33c3858bc 100644
> --- a/src/testdir/test_search_stat.vim
> +++ b/src/testdir/test_search_stat.vim
> @@ -176,7 +176,9 @@ func! Test_search_stat()
>let g:b = split(g:a, "\n")[-1]
>let stat = '\[1/2\]'
>call assert_notmatch(pat .. stat, g:b)
> - call assert_match(stat, g:b)
> + " Test that the message is not truncated
> + " it would insert '...' into the output.
> + call assert_match('^\s\+' .. stat, g:b)
>unmap n
>
>" Clean up
Hmm, since nobody runs the tests manually that doesn't help much.
How about using a screendump? That makes these things a lot easier to
write.
--
I'm so disorganized my keyboard isn't even in alphabetical order!
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/201909041121.x84BLsTM024711%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian wrote:
> > > On Fr, 30 Aug 2019, Bram Moolenaar wrote:
> > >
> > > > Thanks. Yes, I think we should do this. But the allocation should
> > > > probably be done differently, it looks like with cmd_silent set it still
> > > > computes the size of the command. This will require some more "if"
> > > > statements, but makes the size computation more accurate.
> > >
> > > Well, yeah I thought this wouldn't hurt.
> > >
> > > So how about the attached patch then? It will simply use all available
> > > space in the command line. Not sure this is correct however.
> >
> > It's tricky with all the conditions. But it looks OK. All tests pass.
> > Let's include this and check that nothing goes wrong. Can we cover this
> > with a test?
>
> Apologizes, the last patch was wrong and caused a strtrunc message
> ('...')
>
> Perhaps we don't even need the added condition `|| cmd_silent` at all?
>
> Here is a fix including a test.
Thanks. The test doesn't fail without the fix though.
--
hundred-and-one symptoms of being an internet addict:
172. You join listservers just for the extra e-mail.
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/201909032024.x83KO53f022044%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian wrote: > On Fr, 30 Aug 2019, Bram Moolenaar wrote: > > > Thanks. Yes, I think we should do this. But the allocation should > > probably be done differently, it looks like with cmd_silent set it still > > computes the size of the command. This will require some more "if" > > statements, but makes the size computation more accurate. > > Well, yeah I thought this wouldn't hurt. > > So how about the attached patch then? It will simply use all available > space in the command line. Not sure this is correct however. It's tricky with all the conditions. But it looks OK. All tests pass. Let's include this and check that nothing goes wrong. Can we cover this with a test? -- "Hit any key to continue" is very confusing when you have two keyboards. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201909021945.x82JjHVh019218%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian wrote: > On Do, 29 Aug 2019, Gary Johnson wrote: > > > In fact, removing all the mappings and just executing Ctrl-E or > > Ctrl-Y to scroll the window after a search erases the search count > > message. I think that's a bug. I can see no reason why scrolling > > should erase that message unless scrolling moves the cursor. > > > > Further, certain motion commands such as j, k and gg _don't_ erase > > the search count message, even though it would make sense for them > > to do so. It's weird to jump from the bottom of a buffer to the top > > with gg and still see the last search count message in the command > > line. > > Hm, yeah I can reproduce it. I am not sure yet, what causes the extra > redraw of the command line. It's probably just the scrolling. And it's probably tricky to keep the counts when moving around in the file. I don't mind too much, so long as it shows right after the search navigation. -- "The sun oozed over the horizon, shoved aside darkness, crept along the greensward, and, with sickly fingers, pushed through the castle window, revealing the pillaged princess, hand at throat, crown asunder, gaping in frenzied horror at the sated, sodden amphibian lying beside her, disbelieving the magnitude of the frog's deception, screaming madly, "You lied!" - Winner of the Bulwer-Lytton contest (San Jose State University), wherein one writes only the first line of a bad novel /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908301112.x7UBCrfx004773%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian wrote: > On Do, 29 Aug 2019, Bram Moolenaar wrote: > > > The argument means that the command won't be echoed. But it > > does not suppress the output of the command like the ":silent" modifier > > does. > > Yeah, but it felt natural to me, to only show the search index feature, > if the command is echoed. I actually played with a simple patch > yesterday, but then thought that works as expected. > > > How about removing the check for cmd_silent in search.c, where > > search_stat() is called? > > It's a bit more convoluted, since msgbuf needs to be properly allocated > and initialized. > > The attached patch does it. Let me know if you think that is okay. I can > write a test then. Thanks. Yes, I think we should do this. But the allocation should probably be done differently, it looks like with cmd_silent set it still computes the size of the command. This will require some more "if" statements, but makes the size computation more accurate. -- Birthdays are healthy. The more you have them, the longer you live. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908301112.x7UBCrnm004785%40masaka.moolenaar.net.
Re: Mapping erases search count message
Christian Brabandt wrote: > On Do, 29 Aug 2019, Christian Brabandt wrote: > > > > > On Di, 27 Aug 2019, Gary Johnson wrote: > > > > > On 2019-08-28, Christian Brabandt wrote: > > > > On Di, 27 Aug 2019, Gary Johnson wrote: > > > > > > > > > I just tried exposing the search count message by removing 'S' from > > > > > 'shortmess', but I couldn't see it. I discovered that it is hidden, > > > > > erased and/or not updated by a couple of my mappings. > > > > > > > > > > nnoremap n nzv:call AdjCursor() > > > > > nnoremap N Nzv:call AdjCursor() > > > > > > > > > > Here is a simple experiment that demonstrates the problem. Create > > > > > a file, test.vim, that contains the following. > > > > > > > > > > set shortmess-=S > > > > > nnoremap n n > > > > > help map.txt > > > > > > > > > > Open a standard-sized, 80x24 terminal, and in it run > > > > > > > > > > $ vim -N -u NONE -i NONE -S test.vim > > > > > > > > > > Then search for "command": > > > > > > > > > > /command > > > > > > > > > > After hitting Enter, the cursor will be at the start of "commands" > > > > > on line 7 and the command line will contain this: > > > > > > > > > > /command [1/>99] > > > > > > > > > > After hitting 'n', the cursor advances to line 13 and the command > > > > > line stays the same, even showing "[1/>99]" when it should be > > > > > showing "[2/>99]". > > > > > > > > > > Another 'n' advances the cursor to line 17, the screen scrolls > > > > > up so that that line is at the bottom of the window, and the command > > > > > line is empty--no search count message at all. > > > > > > > > > > I would think that would prevent the mapping from > > > > > disturbing the command line, in which case this is a bug. > > > > > > > > > > If it's not a bug, then is there some way of defining a mapping that > > > > > does not interfere with the search count message, or some way of > > > > > restoring that message at the end of a mapping? > > > > > > > > Is that with patch 8.1.1288 included? > > > > > > Sorry, I forgot to include the version information. Yes, I used the > > > latest version, 8.1.1933. > > > > Hm, I need to investigate. > > I see what is happening. A mapping with the `` flag will set the > internal variable cmd_silent to prevent it from being output the command > line. So what your mapping does is it acts like 'n' without outputting > anything on the command line. > > But this is not what you want. You want the default behaviour of n, > which does output the command to search + the new search index feature. > > (See the difference on the commandline between a plain `n` and a n > mapped with `nnoremap n n`). > > So the obvious fix would be to remove the `` command. While this > fixes your minimal test case, it most likely is no fix for your actual > issue, that calling the AdjCursor() function will be output in the > command line in addition (possibly overwriting the command line). > > What might work (depending on the complexity of your AdjCursor() > function) is to use an expression mapping that simply returns 'n' after > having done whatever action it needs to be doing. However, this might be > a bit difficult since you want this to happen after the cursor has been > placed. > > Another alternative might be a mapping like this: > > nmap n nzv > nnoremap zv zv:call AdjCursor() The argument means that the command won't be echoed. But it does not suppress the output of the command like the ":silent" modifier does. How about removing the check for cmd_silent in search.c, where search_stat() is called? -- hundred-and-one symptoms of being an internet addict: 131. You challenge authority and society by portnuking people /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908291859.x7TIx2gh026578%40masaka.moolenaar.net.
Re: Are the --enable-hangulinput and --enable-xim confilct?
Namsh wrote: > >> 2019-08-25 오후 2:25에 Hongyi Zhao 이(가) 쓴 글: > >>> Hi, > >>> > >>> I try to build vim with the --enable-hangulinput and --enable-xim > >>> confilct at the same time, but failed with error: > >>> > >>> - > >>> vim.h:1585:63: error: called object ‘size_t’ is not a function or > >>> function pointer > >>>#define STRNCMP(d, s, n)strncmp((char *)(d), (char *)(s), > >>> (size_t)(n)) > >>> ^ > >>> ex_docmd.c:8459:6: note: in expansion of macro ‘STRNCMP’ > >>> if (STRNCMP(arg, "FALLBACK ", 9) == 0) > >>> ^~~ > >>> In file included from /usr/include/wchar.h:887:0, > >>>from spell.h:250, > >>>from vim.h:2110, > >>>from ex_docmd.c:14: > >>> /usr/include/x86_64-linux-gnu/bits/wchar2.h:507:20: note: declared here > >>>__fortify_function size_t > >>> ^~ > >>> Makefile:3059: recipe for target 'objects/ex_docmd.o' failed > >>> make[1]: *** [objects/ex_docmd.o] Error 1 > >>> make[1]: Leaving directory '/home/werner/software/editor/vim/vim.git/src' > >>> Makefile:26: recipe for target 'first' failed > >>> make: *** [first] Error 2 > >>> - > >>> > >>> Are these two options conflict? > >> > >> Regardless of compilation error, the hangulin feature is for > >> environments where XIM is not available. > >> > >> You can find next line with ':help hangul'. > >>./configure --with-x --enable-multibyte --enable-hangulinput \ > >> --disable-xim > > > > That's a bit of a disadvantage when someone tries to build a version > > that works with multiple languages. Can we make this a runtime choice > > instead of a compile time choice? No idea how much work that would be. > > Here is a minimal patch (no documentation, no indenting to minimize). > If vim supports both xim and hangulinpt and user set 'imdisable', > hangulinput feature is selected. > > I tested this patch by adding '--enable-xim --enable-hangulinput' to my > default configure option. >$ auto/configure --enable-perlinterp=no --disable-gpm > --enable-python3interp=dynamic --enable-tclinterp=no --enable-cscope > --with-features=huge --enable-terminal --enable-multibyte --enable-xim > --enable-hangulinput --prefix=/opt/local --with-x --enable-gui=gtk3 > > While testing this patch, I noticed one glitch. > Though I set 'imdisable' in the vimrc and I confirmed the setting with > ':set imdisable?', when I typed S-Space for the first time, vim connects > to XIM. After that, go to english input mode and type S-Space again, vim > enters to hangulinput mode. My system environement may cause this glitch?? Thanks. I think it always creates the "xim" object, also when 'imdisable' is set. Perhaps it starts in the wrong mode? It is possible that a check for 'imdisable' is missing somewhere. -- hundred-and-one symptoms of being an internet addict: 129. You cancel your newspaper subscription. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908291716.x7THG3Cj003761%40masaka.moolenaar.net.
Re: Are the --enable-hangulinput and --enable-xim confilct?
Namsh wrote: > 2019-08-25 오후 2:25에 Hongyi Zhao 이(가) 쓴 글: > > Hi, > > > > I try to build vim with the --enable-hangulinput and --enable-xim > > confilct at the same time, but failed with error: > > > > - > > vim.h:1585:63: error: called object ‘size_t’ is not a function or > > function pointer > > #define STRNCMP(d, s, n)strncmp((char *)(d), (char *)(s), (size_t)(n)) > > ^ > > ex_docmd.c:8459:6: note: in expansion of macro ‘STRNCMP’ > >if (STRNCMP(arg, "FALLBACK ", 9) == 0) > >^~~ > > In file included from /usr/include/wchar.h:887:0, > > from spell.h:250, > > from vim.h:2110, > > from ex_docmd.c:14: > > /usr/include/x86_64-linux-gnu/bits/wchar2.h:507:20: note: declared here > > __fortify_function size_t > > ^~ > > Makefile:3059: recipe for target 'objects/ex_docmd.o' failed > > make[1]: *** [objects/ex_docmd.o] Error 1 > > make[1]: Leaving directory '/home/werner/software/editor/vim/vim.git/src' > > Makefile:26: recipe for target 'first' failed > > make: *** [first] Error 2 > > - > > > > Are these two options conflict? > > Regardless of compilation error, the hangulin feature is for > environments where XIM is not available. > > You can find next line with ':help hangul'. > ./configure --with-x --enable-multibyte --enable-hangulinput \ > --disable-xim That's a bit of a disadvantage when someone tries to build a version that works with multiple languages. Can we make this a runtime choice instead of a compile time choice? No idea how much work that would be. -- ~ ~ ~ ".signature" 4 lines, 50 characters written /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908261925.x7QJPSQt023692%40masaka.moolenaar.net.
Re: Are the --enable-hangulinput and --enable-xim confilct?
Hongyi Zhao wrote: > I try to build vim with the --enable-hangulinput and --enable-xim > confilct at the same time, but failed with error: > > - > vim.h:1585:63: error: called object ‘size_t’ is not a function or > function pointer > #define STRNCMP(d, s, n)strncmp((char *)(d), (char *)(s), (size_t)(n)) >^ > ex_docmd.c:8459:6: note: in expansion of macro ‘STRNCMP’ > if (STRNCMP(arg, "FALLBACK ", 9) == 0) > ^~~ > In file included from /usr/include/wchar.h:887:0, > from spell.h:250, > from vim.h:2110, > from ex_docmd.c:14: > /usr/include/x86_64-linux-gnu/bits/wchar2.h:507:20: note: declared here > __fortify_function size_t > ^~ > Makefile:3059: recipe for target 'objects/ex_docmd.o' failed > make[1]: *** [objects/ex_docmd.o] Error 1 > make[1]: Leaving directory '/home/werner/software/editor/vim/vim.git/src' > Makefile:26: recipe for target 'first' failed > make: *** [first] Error 2 > - > > Are these two options conflict? Looks more like a problem with your wchar.h file. It uses __fortify_function but it's probably not defined. Perhaps you need to use another compiler or compilation flags. -- hundred-and-one symptoms of being an internet addict: 115. You are late picking up your kid from school and try to explain to the teacher you were stuck in Web traffic. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908251249.x7PCn8xo013794%40masaka.moolenaar.net.
Re: List of mirrors - help needed
Anton Shepelev wrote: > > The ftp protocol is slowly fading away. Still, we provide > > the Vim sources through ftp. > > Anonymous FTP is great. It means I can download software > without a bloated browser that updates once a week. And it > does not force me to upgrade my software, then the OS, then > the PC, simply to keep abrest with the constant development > of new protocols and APIs. I can access FTP archives with > the same software that I used twenty years ago, which will > continue to work in another twenty years. A stable > data-exchage protocol is a blessing. > > > I would like someone to take the current list, remove the > > links that no longer work, and find more https links. > > Many https: links no longer work for me in Windows XP. Is > there any reason for providing public software via HTTPS? > > Anyway, please keep the FTP and HTTP mirrors, in addition > to the HTTPS ones. Nothing is going away, we just cleaned up the list and put https and http first, because that's what most people prefer to use. Quite a few people prefer the secure connection, but it indeed has many more dependencies. -- hundred-and-one symptoms of being an internet addict: 111. You and your friends get together regularly on IRC, even though all of you live in the same city. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908241724.x7OHOZoM031941%40masaka.moolenaar.net.
Re: increasing default read size? & using direct read?
> I was noticing that it took a LONG time to read in a 606.9MB file in > a "local" gvim session (local meaning gvim running on same machine > as file is located). > > I finally figured that it was reading 64KB at a time > using async reads. > > That is really slow compared to using a direct > read of say, 16M at a time > > I.e. using the async reads, for a 8M file takes 2.14s. > It averages 4MB/s, > > Using a direct read of 16M/read takes .18s averaging 3.5GB/s. > > Is there anyway to speed up vim's reading of large files? Vim is optimized for text files, which are usually not that big. Besides Reading Vim does other things, such as splitting the text into lines, checking encoding, etc. And the text has to be copied into data blocks. The actual read might not be the most important thing, it requires profiling and perhaps trying out some changes to see what the effect of a bigger buffer really is. One thing that has been on the todo list for a very long time is to avoid the extra copy, but reversing the way text is stored in data blocks. But that is complicated... -- hundred-and-one symptoms of being an internet addict: 102. When filling out your driver's license application, you give your IP address. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908231913.x7NJDGvA002288%40masaka.moolenaar.net.
Re: List of mirrors - help needed
Rafal Maszkowski wrote: > On Wed, Aug 21, 2019 at 01:33:54PM +0200, Christian Brabandt wrote: > > On Mi, 21 Aug 2019, Bram Moolenaar wrote: > … > > > You can find the current list here: https://www.vim.org/mirrors.php > > > I would like someone to take the current list, remove the links that no > > > longer work, and find more https links. I susped quite of few of the > > > http links also support https, but that needs to be tried, and the > > > domain might be different to match the certificate. > … > > > Is there someone who can take care of this, and send me to cleaned up > > > list? > > Let me take care of this. > > Our site (Poland, Warsaw, ICM) is listed as > ftp://ftp.pl.vim.org/pub/vim/ only. The complete set of our protocols > is: > > ftp://ftp.pl.vim.org/pub/vim/ > http://ftp.pl.vim.org/pub/vim/ > https://ftp.pl.vim.org/pub/vim/ > rsync://ftp.pl.vim.org/pub/vim/ > gopher://ftp.pl.vim.org/1/pub/vim/ > > The main name of the site is ftp.icm.edu.pl or sunsite.icm.edu.pl. Typical case of where the https link doesn't work with the vim.org domain. This one does work: https://ftp.icm.edu.pl/pub/vim/ -- I AM THANKFUL... ...for the taxes that I pay because it means that I am employed. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908211202.x7LC2KHi023549%40masaka.moolenaar.net.
List of mirrors - help needed
The ftp protocol is slowly fading away. Still, we provide the Vim sources through ftp. Many sites also support using http or https. The list of mirrors is outdated now, and I would like to change the order to put the https sites first. You can find the current list here: https://www.vim.org/mirrors.php I would like someone to take the current list, remove the links that no longer work, and find more https links. I susped quite of few of the http links also support https, but that needs to be tried, and the domain might be different to match the certificate. For example, the main site is linked to with ftp://ftp.home.vim.org/pub/vim/ but is also available as http://ftp.vim.org/pub/vim/ and https://ftp.nluug.nl/pub/vim/ Is there someone who can take care of this, and send me to cleaned up list? -- There's no place like $(HOME)! /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908211129.x7LBTxqU016000%40masaka.moolenaar.net.
Re: mutex ?
> I use job channels and things run async as far as I can tell ? Yes, things happen asynchronously, bit all in the same thread. Thus you can use a normal variable as a flag. -- >From "know your smileys": :-DBig smile /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201908211055.x7LAt9Gb003852%40masaka.moolenaar.net.
Re: New compiler/perl.vim
Christian J. Robinson wrote: > Small change to escape the filename. I'll include it, thanks. -- The problem with political jokes is that they get elected. /// Bram Moolenaar -- 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201907232015.x6NKFsoC015479%40masaka.moolenaar.net.
Re: Vin crashes with "Caught deadly signal ABRT" unless launched without .vimrc
Ottavio Caruso wrote: > I'd like to have the opinion of this list before reporting this issue > as a bug on github. > > I have compiled and installed Vim using pkgsrc on my Linux Mint Debian > Edition. > I've already reported the issue on the pkgsrc-users list and it has > been suggested that I report the issue upstream. > > The build has run fine, but, and this seems to be a common failure, > when Vim is launched, it crashes like this: > > $vim > Vim: Caught deadly signal > Vim: Finished. > > Full vim --version here: > http://paste.debian.net/hidden/ded7a246/ > > Full build log here: > http://paste.debian.net/hidden/5ebf5480/ > > I've made a gdb capture here: > http://paste.debian.net/hidden/4ca4bed2/ > > Temporary workarounds: > > 1) `vim -u NONE` # works, but without modules > > 2) recompiling with the option: "CFLAGS=-g INSTALL_UNSTRIPPED=yes" # > produces a binary without crashes. > > Any input will be appreciated. It looks like you run into the false-positive fortify check. Although the build log mentiones -D_FORTIFY_SOURCE=1 it behaves like a higher fortify level was used. -- FATHER:You only killed the bride's father - that's all - LAUNCELOT: Oh dear, I didn't really mean to... FATHER:Didn't mean to? You put your sword right through his head! LAUNCELOT: Gosh - Is he all right? "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201907121337.x6CDbUqT011874%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: Problem with signcolum=number
Yegappan wrote: > On Mon, Jul 1, 2019 at 7:57 AM Salman Halim wrote: > >> > >> On Mon, Jul 1, 2019 at 7:09 AM Salman Halim wrote: > >> > > >> > Hello, > >> > > >> > When setting 'signcolumn' to number, if I edit a file containing fewer > >> > than ten lines and have a plug-in that shows marks as signs (or have > >> > manually created signs), the signs are occasionally three columns > >> > wide, thus wider than the number column. This breaks editing, such as > >> > pressing x to remove a character (it removes the wrong character). > >> > > >> > >> Can you post the sign definition? When you say "occasionally", do you > >> know which operation or movement triggers this? > >> > >> Thanks, > >> Yegappan > > > > > > It's a trivial case. > > Start with an empty file: gvim -u NONE -U NONE > > (I use Windows, gvim 8.1-1608) > > > > :set number numberwidth=1 signcolumn=number > > > > As the sign text takes two columns, the minimum supported value for > 'numberwidth' is 3 with 'signcolumn' set to 'number'. > > When 'signcolumn' is set to 'number', I think we should change the value > of 'numberwidth' to a minimum of 3 (if it is less than 3)? Yes, can be added to number_width(). Would appreciate if you add a test. -- You cannot propel yourself forward by patting yourself on the back. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201907011856.x61IuXkx031979%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: encryption with vim
Mathieu Roux wrote: > I use encryption with vim. > I just do :X > and then i write 2 times my password. > After my file is crypted. > > 1) What about now, if i want to cancel encryption (i don't want > password anymore). > If i tryset key= > it does not work: again the same password when i open vim again. You need to write the file: :set key= :write > 2) And what about now if i want to change password? > If i do :X in the open file, and enter 2 times my new password, it is > the same... when i close the file and open it again, only the old > password is ok. Sounds like you are missing the write here as well. -- hundred-and-one symptoms of being an internet addict: 216. Your pet rock leaves home. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906171838.x5HIcbHL016821%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: gvim visual mode very slow, even with -u NONE
> Hi all, > I am having problems with graphical vim since not too long ago; > terminal version works as great as always. > > The problem is that it became very choppy - there's about 500ms-1s > lag between any keypress and reaction. Keypresses are queued, so if > I rapidly type, they're executed in sequence, slowly. > > I am running archlinux with xmonad wm. Most of my apps run inside > urxvt, with browser (palemoon) and gvim being the only graphical > apps. > I am running the compositor (compton), but killing it changed > nothing. > The hardware is nothing spectacular, 4y old laptop. > > What follows is list of things I tried before posting here: > > * updating my system, rebooting. No change. > * vim -g -u NONE -U NONE. No change. > * killing all other apps. No change. > * comparing vim vs. vim -g. Terminal version runs normally. > * strace $(pidof gvim). A gigazillion of failed recvmsg calls and > few istats. I assumed this is normal behavior because it happens > in terminal version too. > * research on open issues: stackoverflow, stackexchange, vim wiki. > Followed advice on changing fonts, didn't help. I don't use cursor > lines and columns. > * asked on #vim on Freenode. Got told to try with -u NONE, and try > disabling compositor. Didn't help. > * ldd vim to check which libs are used, went to check libpango and > libcairo bug trackers for potential issues. Didn't find anything. > > > I am not sure what is causing the issue. I found an advice to try > alternative builds of gvim (using Athena), but before going down > that road I'd like to try and see if I can fix this, especially > because it might be affecting other parts of my system too - its > just that the only symptom I see is in gvim. > > I don't know what else might be relevant. If there's anything, > please ask. What system is this on? Some kind of Linux? What GUI are you using? Since it works OK in the terminal version the selection mechanism probably works OK. But having half a second for updating the highlighting is unlikely. Can't guess what the problem is. -- hundred-and-one symptoms of being an internet addict: 171. You invent another person and chat with yourself in empty chat rooms. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906141112.x5EBCcxf022595%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: :help :check inconsistent with :check
John Little wrote: > On Sunday, June 2, 2019 at 1:54:53 PM UTC+12, Tony Mechelynck wrote: > > for this, line 827 of doc/tagsrch.txt would have had to be: > > *che* *chec* *check* *checkp* *checkpa* *checkpat* *checkpath* > > instead of just the first and last ones of these; similarly for _all_ > > other ex-commands, which I believe would have made the doc/tags file > > much bigger. > > Extra tags would only be needed where there's ambiguity. I compiled a > list; the middle column is what you get if you type the given at the : > command prompt, and the third column is the topic you get if you ask > for help for the given: Thanks, that is very useful. I don't know how you generated this, but I assume these are the useful ones. > > given | :| :help : > +--+- > arg | args | arga > bre | brewind | break > cab | cabbrev | cabclear > cadd| caddbuffer | caddexpr > chec| checkpath| checktime > cne | cnext| cnewer > cnor| cnoremap | cnoreabbrev > cun | cunmap | cunabbrev > diff| diffupdate | diffget > doaut | doautocmd| doautoall > end | endif| endfunction > folddo | folddopen| folddoc > inor| inoremap | inoreabbrev > keep| keepmarks| keepalt > ladd| laddbuffer | laddexpr This one is the wrong way around, :ladd stands for :laddexpr. > lfi | lfile| lfirst > lge | lgetfile | lgetbuffer > lma | lmap | lmake > lock| lockmarks| lockvar > mkvi| mkvimrc | mkview > sfi | sfind| sfirst > snore | snoremap | snoremenu > ver | version | verbose > > One or two extra tags for each of these is not going to significantly > add to vim's 10,000 or so. > > > :help :check (with 'wildmenu' on) or :help :check would > > have shown you all helptags beginning with :check > > How would I have known to do that, when I did not know that there > might be another command starting with "check"? I use the help when I > don't know stuff, that's the point of it. -- Ed's Radiator Shop: The Best Place in Town to Take a Leak. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906021148.x52BmXEI007959%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: :help :check inconsistent with :check
John Little wrote: > I just struck an inconsistency that had me confused. > > I was watching a steadily growing log file, and with autoread set, I used the > command > > :check > > and nothing happened (but for a message I didn't understand). So I went to > the help and ran > > :help :check > > and got the help for the command I thought I was running. Eventually I > worked out that :check is actually :checkpath, and I should have used > :checktime. > > But surely ":h :xyz" should give the help for ":xyz", but am I missing > something? The tag of :checkpath is ":che", which is the shortest form. Apparently for ":help :check" it finds ":checkt" or ":checktime" first. I'll add a tag for ":check" at ":checkpath", that will fix it. -- hundred-and-one symptoms of being an internet addict: 83. Batteries in the TV remote now last for months. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906021122.x52BMdJu003159%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: Has window-toolbar feature?
> How do you check whether Vim has the window-toolbar (WinBar) feature?
if has('menu')
--
hundred-and-one symptoms of being an internet addict:
29. Your phone bill comes to your doorstep in a box.
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/201905261114.x4QBEL9m025106%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
Re: Vim "by far the best editor on the iPad"
Eric Weir wrote: > > On May 18, 2019, at 2:17 PM, Eric Weir wrote: > > > > As I indicated in my initial post, I’ve largely been away from Vim for a > > few years. Lotsa things have become Greek to me that once we’re not. Help > > Appreciated. > > When I do :vimtutor in iVim on my iPad or in MacVim on my MacBook I > get “not an editor command.” Anyone have any ideas about why? It is a shell command, not a command to use inside Vim. % vimtutor -- hundred-and-one symptoms of being an internet addict: 5. You find yourself brainstorming for new subjects to search. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201905211919.x4LJJBaA016550%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: download statistics from the daily win builds
Christian wrote: > I thought, that I share some download statistics from the daily Vim > builds from the vim-win32-installer repository that I created today. Very nice, thanks for making this work. > So here are some statistics for the releases 8.1.1201 (Apr 25th, 2019) - > 8.1.1336 (May 17th, 2019). > > |Version |x86 zip|x64 zip|x86 exe|x64 exe|32bit|64bit| Sum | % x64| % EXE| > ||---|---|---|---|-|-|--|--|--| > |8.1.1336| 0 | 340 |0 | 290 | 0 | 630| 630 | 100% | 46% | > |8.1.1330| 0 | 711 |0 | 1000 | 0 | 1711| 1711 | 100% | 58% | > |8.1.1329| 0 | 389 |0 | 310 | 0 | 699| 699 | 100% | 44% | > |8.1.1324| 42 | 226 | 59 | 184 | 101 | 410| 511 | 80% | 48% | > |8.1.1315| 33 | 209 | 38 | 207 | 71 | 416| 487 | 85% | 50% | > |8.1.1312| 0 | 335 |0 | 290 | 0 | 625| 625 | 100% | 46% | > |8.1.1302| 69 | 372 | 66 | 298 | 135 | 670| 805 | 83% | 45% | > |8.1.1286| 53 | 533 | 72 | 590 | 125 | 1123| 1248 | 90% | 53% | > |8.1.1282| 50 | 420 | 61 | 339 | 111 | 759| 870 | 87% | 46% | > |8.1.1248| 0 | 575 |0 | 590 | 0 | 1165| 1165 | 100% | 51% | > |8.1.1244| 52 | 494 | 72 | 251 | 124 | 745| 869 | 86% | 37% | > |8.1.1240| 36 | 286 | 48 | 193 | 84 | 479| 563 | 85% | 43% | > |8.1.1239| 49 | 359 | 61 | 277 | 110 | 636| 746 | 85% | 45% | > |8.1.1234| 0 | 267 | 48 | 214 | 48 | 481| 529 | 91% | 50% | > |8.1.1222| 53 | 137 | 48 | 214 | 101 | 351| 452 | 78% | 58% | > |8.1.1201| 80 | 315 | 115 | 833 | 195 | 1148| 1343 | 85% | 71% | > ||--|--|--| > | Total |13.253| 90% | 49% | > ||--|--|--| > > So in general, about 90% of all downloads will be for the 64bit version > of the Vim builds. At the same time the ratio between installer and zip > file is roughly 50%. While the download of the pdb/debug zip files is > negligible I find it quite surprising, that the 32bit downloads is only > about 10% on average. Also I would certainly not have expected that the > installer makes up about half of the downloads. At the same time around > 14.000 downloads in total is quite impressing for a 3 week period. I'm not surprised that 90% is 64 bit, I would expect users who get the latest Vim also have recent hardware and plenty of memory. And "64 bit" just sounds better than "32 bit". It's indeed surprising there are many downloads for the zip files. Perhaps there is some script at work? > The statistics is also available at > https://github.com/vim/vim-win32-installer/wiki/Download-Statistics > > On a related note: Since today there is a signed win32 installer > available. Signing the releases is provided by SignPath.io that provides > a free signing feature for OpenSource projects. It still requires some > manual effort to upload the signed artifacts back on github, so I will > only upload those signed artifacts every once in a while (if I don't > forget :)) Let's see how the signed version fares. I should try it myself... -- An easy way to determine if you have enough teamwork to be doomed is simply to measure how long it takes from the time you decide to go to lunch together until the time you actually eat. (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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201905172107.x4HL7MNQ028109%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: ERR?: Doubled paste from clipboard (Linux)...
Meino wrote:
> every time, when I do this und Linux:
>
> * copy some text from a terminalo
How? Do you use the mouse or something else?
> * start another terminal
> * start vim (vim in an terminal, not gvim)
> * go into insert mode
> * click the middle mouse button to insert
>
> I get the text inserted twice.
>
> But this only happens when vim is started freshly.
> Using the same vim for further pasteing -- even
> with the same clipboard contenst -- does not expose
> this feature.
Strange, I cannot guess what causes this.
> This was not the case with previous versions of vim.
> I am using vim version 1315...this feature was shown
> since aboyt a week or so
>
> The feature is also active, when vim was started with
> --noplugin
>
> The terminal used is:
>
>
> [I] x11-terms/rxvt-unicode
> Available versions: 9.21^t 9.22-r1^t (~)9.22-r3^t **^t {256-color
> alt-font-width blink buffer-on-clear fading-colors +focused-urgency
> +font-styles gdk-pixbuf iso14755 +mousewheel +perl secondary-wheel
> startup-notification unicode3 +utmp +vanilla wcwidth +wtmp xft}
> Installed versions: 9.22-r3^t(05:47:43 AM 04/28/2019)(256-color
> font-styles mousewheel perl utmp wtmp xft -blink -fading-colors -gdk-pixbuf
> -iso14755 -startup-notification -unicode3)
> Homepage:http://software.schmorp.de/pkg/rxvt-unicode.html
> Description: rxvt clone with xft and unicode support
>
> I am running GENTOO Linux which is updated on a daily basis. Last
> update was this morning.
>
> How can I fix it?
--
Clothes make the man. Naked people have little or no influence on society.
-- Mark Twain (Samuel Clemens) (1835-1910)
/// 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_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/201905121154.x4CBsCnN027990%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
Re: A question about highlight-cterm
> I am a bit puzzled by the note in `:help highlight-cterm`: > > Note: Many terminals (e.g., DOS console) can't mix these attributes with > coloring. Use only one of "cterm=" OR "ctermfg=" OR "ctermbg=“. > > Virtually all colorschemes I have seen use ctermfg AND ctermbg AND cterm. > > The note above is also at odds with `:help cterm-colors`, which states: > > If you want to set the bold attribute in a different way, put a "cterm=" > argument AFTER the "ctermfg=" or "ctermbg=" argument. > > Which implies that cterm and ctermfg/ctermbg can coexist. > > Perhaps, the above note is a thing of the past and should be removed? It is not of the past, the basic ANSI terminal still only has 8 or 16 colors. But most users would be using 256 colors whenever they can. Let's rephrase this: Note: Some terminals (e.g., DOS console) can't mix these attributes with coloring. To be portable, use only one of "cterm=" OR "ctermfg=" OR "ctermbg=". -- This message contains 78% recycled characters. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190510.x4BBA4Kk009445%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
Re: Fwd: ":helptags $VIMRUNTIME/doc" gives Error E154: Duplicate tag ":cbe" in quickfix.txt
Tony wrote: > *:cbe* is found twice in quickfix.txt: at line 142 as a synonym of > :cbelow and at line 157 as a synonym of :cbefore. AFAICT it means the > latter but ":help :cbe" goes to the former. > > This is after the runtime update which is part of patch 8.1.1280. It should be *:cbel* and ":lbel*. Also *:lbef* should be *:lbe*. -- BEDEVERE: How do you know so much about swallows? ARTHUR: Well you have to know these things when you're a king, you know. "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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Documentation error for change 8.1.1116
Tony wrote: > > > In helpfile repeat.txt line 331, a few lines below *:scriptversion* > > > there is: > > > Does not apply to sourced scripts. > > > there should be: > > > Only valid in a sourced script. > > > > Let's make that a bit clearer: > > > > Specify the version of Vim for the lines that follow > > in the same file. Only applies at the toplevel of > > sourced scripts. > > In view of what you said below, I suggest: "Only applies at the > toplevel of sourced scripts (i.e. outside of any function)". > > Can it be used inside a conditional sequence (between :if and :else, > :while and :endwhile, etc.?) Yes. > Using an ex-command for that kind of status change makes me feel > uncomfortable. Wouldn't a 'cpoptions' flag have been better suited? > (Since the full stop is already taken, I suggest a colon.) No, because every script that uses a non-default script version must state so. There are always multiple scripts, and you can't expect them all to be the same version. -- hundred-and-one symptoms of being an internet addict: 206. You religiously respond immediately to e-mail, while ignoring your growing pile of snail mail. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Documentation error for change 8.1.1116
Tony wrote: > In helpfile repeat.txt line 331, a few lines below *:scriptversion* > there is: > Does not apply to sourced scripts. > there should be: > Only valid in a sourced script. Let's make that a bit clearer: Specify the version of Vim for the lines that follow in the same file. Only applies at the toplevel of sourced scripts. > Trying to use the :scriptversion command outside of a sourced script > gives error E984: :scriptversion used outside of a sourced script > > Testcase: type the following: > :scriptversion 2 | echo .5 | scriptversion 1 > then hit It also doesn't work inside a function. I was wondering if it makes sense there. Would only be if you change style halfway a function, which I would not expect to be useful. -- Spam seems to be something useful to novices. Later you realize that it's a bunch of indigestable junk that only clogs your system. Applies to both the food and the e-mail! /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: v8.1 indentation change?
> On Monday, 25 March 2019 10:40:49 UTC, Keith wrote: > > > On Thursday, 21 March 2019 13:55:34 UTC, Paul wrote: > > > > On Tue, Mar 19, 2019 at 05:24:33AM -0700, Keith wrote: > > > > >If I have a line that starts, say, one tab in, and then insert a '#' > > > > >char in col 1, in v8.0 that would be that, but in v8.1, the '#' char > > > > >gets auto-indented to one tab in, and the remainder of the line is > > > > >shifted over accordingly. > > > > > > > > Could this be a plugin interfering? I can't reproduce it here. > > > > I found it in the end by installing v8.0 elsewhere and comparing the > > 'indent.vim' files. The old one had this near the top: > > > > " Don't reindent comments on first column > > if cline =~ '^#.' > > return 0 > > endif > > > > No idea why that was removed, but putting it back works just fine :) > > My bad - it was the 'perl.vim' file in the 'indent' folder. It looks like this was intentionally removed. Perhaps a matter of taste how comments are indented? -- hundred-and-one symptoms of being an internet addict: 118. You are on a first-name basis with your ISP's staff. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: vimdiff + wrap line alignment
> If I set wrap on for vimdiff (in all windows) and there is a wrapped > line in one window long enough to wrap at least once more than the > other window, the lines in the windows are no longer in alignment. > For example, it would seem the "" line in one window to match the > other's new line is only as long as the window width and not as long > as the other window's new line ?? > Anyone have any suggestion for keeping file lines aligned with wrap on > in vimdiff ? This is not supported. Implementing this would require quite a few changes to the code, implementing filler lines to keep the windows in sync. It's also not going to look good. -- "Thou shalt not follow the Null Pointer, for at its end Chaos and Madness lie." /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to keep the cursorline consistent in vim diff?
> I’m using vimdiff on a three-way diff. I first open Vim using the > command “vimdiff file1.txt file2.txt file3.txt”. I have set cursorline > enabled and as I arrow down the cursor stays consistent through each > of the three windows. But when I do a diffput on one of the buffers > the cursorline is no longer consistent. The cursorline on buffer2 is > lower than buffer3. How do I update refresh the page? I cannot reproduce the problem. Please give a step-by-step example. And what is your Vim version? -- Time is money. Especially if you make clocks. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Does gVim has long term plan to support Emacs' frame feature? (For multi monitors)
Kevin Gao wrote: > Basically: I am asking: is there a long term plan to support: run one Vim > instance (single process) across multi monitor? Emacs as well as modern IDE > support this feature. Not really. It would lead to some hard to tackle questions, such as what happens with the command line. Since the size of monitors has been increasing, the demand for this feature has actually been reduced. There are more important features to work on. -- Portable Computer: A device invented to force businessmen to work at home, on vacation, and on business trips. /// 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_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
