Re: Vim after Bram?

2023-09-19 Thread Owajigbanam Ogbuluijah
On Mon, Sep 18, 2023 at 2:27 PM Yegappan Lakshmanan wrote: > Hi, > > On Sun, Sep 17, 2023 at 7:47 PM 'Philip Rhoades' via vim_use > wrote: > > > > People, > > > > I have been using Vim for so many decades that I sort of felt that Bram > > would always be there developing and improving the

Re: Vim9 script performance vs. legacy

2023-08-30 Thread Owajigbanam Ogbuluijah
Amazing! Thank you for doing this benchmarking. On Tue, Aug 29, 2023 at 6:38 PM Salman Halim wrote: > > > On Tue, Aug 29, 2023 at 10:33 AM Christian Brabandt > wrote: > >> >> On Di, 29 Aug 2023, Salman Halim wrote: >> >> > Hello, >> > >> > I've been writing my scripts using Vim 9 recently

Re: The package you uploaded (vim-noweb.tgz) is empty

2023-06-08 Thread Owajigbanam Ogbuluijah
Hey Bram, I've been following this thread for a while now. Is there a team handling the vim.org site? Maybe we can collect a few people interested enough to volunteer? I'm interested for one. That team could be responsible for ensuring issues like these are fixed, and the general updates of the

Re: vim autoformat ?

2023-05-27 Thread Owajigbanam Ogbuluijah
Hey Igor, Formatting in Vim is pretty simple. Vim already understands how to format many filetypes. Try not to use too many plugins to complicate things; especially if you're not mandated or forced to. I'll second what Bram, and the others, said here earlier. You can start by formatting the

Re: Plugins not loading with recent vim on Windows 11

2023-05-13 Thread Owajigbanam Ogbuluijah
Try installing *junegunn/vim-plug* and restarting Vim On Sat, May 13, 2023 at 10:17 PM Steve wrote: > vim version: 9.0.1547 > > Getting the following errors when opening vim: > > Error detected while processing C:\Users\smartin\.vimrc: > > line 188: > > E117: Unknown function: plug#begin > >

Re: Small documentation tweak for :g delimiters

2023-05-01 Thread Owajigbanam Ogbuluijah
If you check the documentation for *help :v*, you'd see it's marked as the same On Mon, May 1, 2023 at 7:50 PM Tim Chase wrote: > Shortly after the help for :v it reads > > Instead of the '/' which surrounds the {pattern}, you can use any > other single byte character, but not an alphabetic

Re: Beginner? How do I fix these error messeges

2023-03-19 Thread Owajigbanam Ogbuluijah
ssible? > Is there a way I can uninstall vim, and then download vim to a directory > of my choosing? > > Thank you > Norman > > On Thursday, March 16, 2023 at 1:02:58 PM UTC-5 Owajigbanam Ogbuluijah > wrote: > >> Are you trying to write out TODO.vim, or does it already exist on

Re: Beginner? How do I fix these error messeges

2023-03-16 Thread Owajigbanam Ogbuluijah
Are you trying to write out TODO.vim, or does it already exist on the interwebs? I asked this because it would be nice to read the code and see what is really going on here. Without this, here are a few tips - You can search the help for any error you see, *:h 484* should tell you give you

Re: Beginner? How do I fix these error messeges

2023-03-16 Thread Owajigbanam Ogbuluijah
Maybe share a screenshot? On Thu, Mar 16, 2023 at 1:03 PM wrote: > > Line1 > > > > line3 > > using unix > > > What error messages? Is something missing from the posting? > > -- > -- > You received this message from the "vim_use" maillist. > Do not top-post! Type your reply below the text you

Re: get better copy backwards

2023-03-06 Thread Owajigbanam Ogbuluijah
I often consider the cursor as the left edge of the block. This way, yanking backwards makes sense. Ensure the left edge of your cursor is outside (i.e. "right-bounding") the text you want to yank. Then the solution in Salman Halim's answer makes sense. This works for all cases except when you

Re: vim9 exported func badly indented

2023-02-13 Thread Owajigbanam Ogbuluijah
FYI this modification indents properly *export def ProfileVimStartup(): void profile start $tmp/vimprofiler.log profile file *; profile func *;enddef* On Thu, Feb 2, 2023 at 4:13 PM N i c o l a s wrote: > Hi, > > Got this vim9 func, visual select all lines, type =, it is indenting >

Re: would my config be used?

2023-01-21 Thread Owajigbanam Ogbuluijah
Can you try adding *set relativenumber* to your configuration in *~/.vim_runtime*? Does this work? There's no place in amix/vimrc which explicitly sets or unsets relativenumber. But my guess is you can customize anything you want in your *my_config.vim* On Sat,

Re: Searching across a range of lines

2023-01-14 Thread Owajigbanam Ogbuluijah
I don't know if you're into completion engines, but coc-java has an "Organize Imports" which does exactly what you're trying to do. - Igbanam. On Sat, Jan 14, 2023 at 1:52 AM Salman Halim wrote: > On Fri, Jan 13, 2023 at 8:13 PM Tim

Re: Highlighting cursor lines

2023-01-10 Thread Owajigbanam Ogbuluijah
I had thought Vim dims inactive windows the same way TMux does; but this question made me realize I've been hallucinating that feature all these while. One way is to play with your *au!* commands as you've done; finding the right visual cue which works for you. I've always worked around this with

Re: mysterious highlighting

2022-12-19 Thread Owajigbanam Ogbuluijah
Does *:noh* clear the highlights? On Mon, Dec 19, 2022 at 9:28 PM Barry Gold wrote: > I'm editing a file. For some reason all occurrences of the letter "s" > are highlighted in green. > > Notes: > > 1. I've tried searching for something else, but that doesn't change the > colors. > > 2. All

Re: Atom and Substitute carraige return only in part of string

2022-12-18 Thread Owajigbanam Ogbuluijah
*:s/\zs"[^"]\+"\ze/replace_string_here/g* On Sun, Dec 18, 2022 at 11:55 AM N i c o l a s wrote: > Hi, > > Getting this awfull string containing several carriage return, seome of > them would to be substitute with *space*, seome others with *nothing*. > >

Re: How to quickly move to a specific buffer?

2022-12-14 Thread Owajigbanam Ogbuluijah
I have this in my setup *set wildmenuset wildoptions=pum,fuzzy* With this, the command fuzzy-completes in a pop-up window. On Wed, Dec 14, 2022 at 1:55 PM Yegappan Lakshmanan wrote: > > > On Wed, Dec 14, 2022 at 11:09 AM Enan Ajmain <3nan.ajm...@gmail.com> > wrote: > >> On Wed, 14 Dec 2022

Re: List of changed lines

2022-12-01 Thread Owajigbanam Ogbuluijah
Does *:h changes* help? On Thu, Dec 1, 2022 at 3:52 PM Christian Brabandt wrote: > > On Do, 01 Dez 2022, Salman Halim wrote: > > > One obvious way would be to have Vim go to the :earlier state, grab the > > contents of the buffer, come back to 'now' and then manually do a diff > to see > >

Re: Plugin compilation?

2022-11-15 Thread Owajigbanam Ogbuluijah
Hi Gödecke, There are two things that come to mind when people ask me about going deeper into Vim. 1. Writing "plugins" 2. Installing plugins For writing plugins… I'll suggest you take some time and look into Vim help. Then, take a stab at writing some scripts which make your workflow

Re: VimConf 2022 ?

2022-11-08 Thread Owajigbanam Ogbuluijah
Seems like VimConf for 2020 and 2021 were cancelled. Wouldn't be surprised if 2022 was cancelled as well - Igbanam On Tue, Nov 8, 2022 at 6:10 AM Nicolas wrote: > Hi, > > Regarding New features as vim9script, > did i miss VimConf 2022 or is it not planned ? > > Thank you

Re: Embedding Lua in vim9script breaks syntax highlight

2022-10-30 Thread Owajigbanam Ogbuluijah
Hi Nicolas, I'd recommend having Lua code in a Lua file, then using the Lua region in Vim9script to import the Lua file — if you must. A better recommendation would just be to write Vim9script though. I find it easier to write. Best, Igbanam On Sun, Oct 30, 2022 at 5:38 AM Nicolas wrote: >

Re: E117: Unknown function: plug#begin

2022-10-26 Thread Owajigbanam Ogbuluijah
Hi Rellot, >From the syntax, you may be trying to use junegunn/vim-plug . Ensure vim-plug is properly installed. These errors mean Vim can't find the functions which would have normally been registered by the plugin. 3 things 1. Ensure the plugin is

Re: How to autosave files when terminal is closed

2022-10-24 Thread Owajigbanam Ogbuluijah
Hi Dennis, Are you asking for an event which fires when you close the terminal within Vim — opened with *:term* — *or* the terminal window that's housing Vim? If it's the later, I wonder if SigUSR1 may help here? — where SigUSR1 is the interrupt your terminal sends to Vim in the event that it's

Re: vim-plug commands (PlugUpdate, PlugInstall) broken due to vim9 patch or $HOME

2022-10-01 Thread Owajigbanam Ogbuluijah
I currently use Vim9 and vim-plug is working fine. I'm beta-testing switching completely to vim9script at https://github.com/igbanam/dotfiles/pull/16. Where would you need $HOME/vimfile? I'm thinking if that breaks, expanding $HOME may help? Let me know. - Igbanam. On Fri, 30 Sept 2022,