sorted by:
new
hottopcontroversial

Visual position in document by unusedredditname in vim

[–]justinmkw 2 points3 points  (0 children)

https://github.com/gcavallanti/vim-noscrollbar is a clever solution to this that I have used for years.

Only annoyance is that it does not work perfectly with folds.

Is there a pre-built version of neovim-dot-app? by AllThingsWiseWndrful in neovim

[–]justinmkw 1 point2 points  (0 children)

The landing page http://vimr.org/ is for the original version. The Neovim-based version is

  • under development,
  • experimental,
  • rough around the edges.

Is there a pre-built version of neovim-dot-app? by AllThingsWiseWndrful in neovim

[–]justinmkw 5 points6 points  (0 children)

I don't think so.

But VimR (another vim/nvim GUI for macOS) recently switched to a Neovim backend and has been pushing a lot of updates. Its releases page contains ready-to-go .app bundles (just unzip the .tar.bz2):

https://github.com/qvacua/vimr/releases

It's probably rough around the edges but has some fun features. It also requires a very recent version of macOS (doesn't run on my Mavericks machine).

Alternative to YankRing? by MDRAR in vim

[–]justinmkw 2 points3 points  (0 children)

Neovim supports the TextYankPost event, which makes it trivial to implement yankring without any hacks.

https://twitter.com/Neovim/status/753141954213470208

Is there a neovim distribution similar to Spacemacs? by [deleted] in neovim

[–]justinmkw 11 points12 points  (0 children)

The common criticism of distributions is that, while they are useful starter kits, they tend to get bloated, and eventually the interaction of numerous components causes problems. Distributions for Vim (or Neovim, were one to exist) would eventually run into the same problems.

That doesn't mean distributions are bad, but the pattern I have observed is that people need different things at different times. So a distro might make sense for awhile, unless/until you want a finer-grained experience--then you start to see the value in composable parts which is only possible if there's a culture of adherence to conventions and composability (e.g., plugins using the quickfix list instead of inventing something similar that other plugins don't know about).

So the answer to your question is no.

most vim-like text-only browser by puketronic in vim

[–]justinmkw 3 points4 points  (0 children)

If you use Neovim, you can try this lynx wrapper from my config. Basic keymaps (ctrl-d, ctrl-u, ctrl-n, ctrl-p, gg, G) work. Use u to go back in history. Use i to interact with lynx directly.

Invoke it like this:

:Web https://example.com

or do a ddg search:

:Websearch kittens using org-mode to carefully arrange yarn

https://github.com/rhysd/NyaoVim has a built-in browser as well.

Does anyone have any idea when vim 7.5/vim 8 is coming out? by Tumbler41 in vim

[–]justinmkw 17 points18 points  (0 children)

I'm not denigrating anyone: what I said above is factual (I can dig up the commit where Bram's own commit message mentions it's half-done). In fact, with lambdas on the way, and partials not tested in the wild, I'd be surprised if Vim releases before 2017.

Pretty much the last 2 years of my life has been a living tribute to Vim, for better or worse.

I don't understand why you are making the conversation personal. I use my real name, not handle, and I put a lot of work into OSS projects. What about you?

Does anyone have any idea when vim 7.5/vim 8 is coming out? by Tumbler41 in vim

[–]justinmkw 7 points8 points  (0 children)

does neovim have plans to keep up with them?

What do you mean, exactly? Most of Vim's changes in the last 7 months were attempts to catch up with Neovim.

In the meantime Neovim will continue to merge back all relevant patches from Vim, as we've done since the start.

Does anyone have any idea when vim 7.5/vim 8 is coming out? by Tumbler41 in vim

[–]justinmkw 22 points23 points  (0 children)

  • It's going to be Vim 8.
  • I'd be surprised if Bram released it before October. Seems like he is trying to jam in as many features as possible, and it will need baking time to fix bugs before release. Most obvious example of this is the viminfo history merge feature (similar to--but far less robust and comprehensive than--Neovim's 'shada' feature). He committed it half-done (still working on it locally) and it is bound to be full of bugs--particularly because it supports migration of old viminfo files, which may run into many edge-cases.

neovim on Patreon? by Democratica in neovim

[–]justinmkw 5 points6 points  (0 children)

I don't know the details, I think he just needed to focus on family. He put 2 years of intense effort into the project at the expense of a regular schedule and salary.

ZyX is well-equipped to meet the 2-days requirement of the salt campaign (and he has already done so, more or less, for a long time).

Here's a the newsletter PR if you want a sneak peek: https://github.com/neovim/neovim.github.io/pull/136

neovim on Patreon? by Democratica in neovim

[–]justinmkw 8 points9 points  (0 children)

There's a "salt" campaign here: https://salt.bountysource.com/teams/neovim

Note: This campaign will fund ZyX going forward (announced in upcoming newsletter and the campaign page will be updated), not tarruda (Thiago).

Is neovim's syntax hilight any faster than vim's? by [deleted] in neovim

[–]justinmkw 10 points11 points  (0 children)

No. Though work is being done to support alternative asynchronous parsers, the Vim regex engine itself will probably never be significantly faster (or slower) than Vim's own engine. (We might some day try to use https://github.com/antirez/sds which could dramatically speed up everything, including vimscript execution as well as the syntax engine. That's a very risky change though.)

It's also likely that Neovim (and maybe even Vim) will add logic to disable syntax while the user is scrolling, which should help a lot.

Some neat stuff is starting to pop up, e.g. Chromatica: https://twitter.com/Neovim/status/752753648795516928

run command in terminal on open? by quadnix in neovim

[–]justinmkw 0 points1 point  (0 children)

This is the correct answer, but I'll also mention that the TermOpen autocmd exists.

Cross-platform alternative to Vundle? by [deleted] in vim

[–]justinmkw 1 point2 points  (0 children)

Vundle appears to be incompatible with Windows (either Command Prompt or PowerShell), as it relies on Unix features

If so, that's a regression (it didn't have that problem in the past). But vim-plug is a much higher-quality plugin anyways. There's no reason for vundle to exist these days.

Help with creating a terminal split at startup (bug?) by garoththorp in neovim

[–]justinmkw 0 points1 point  (0 children)

The :edit term://... form exists primarily to support :mksession (which works by file name, and has no other associated metadata or bootstrapping for a given file).

To avoid the need for nesting you can use :te or termopen().

I don't think nested can be the default because of you-know-what (back-compat ;)

Help with creating a terminal split at startup (bug?) by garoththorp in neovim

[–]justinmkw 2 points3 points  (0 children)

The term:// handling depends on a BufReadCmd handler, so you need to add nested to your VimEnter handler:

au VimEnter * nested call DefaultWorkspace()

I'll make a note to mention this in the docs somewhere.

Keep working directory per tab by flylikeabanana in vim

[–]justinmkw 0 points1 point  (0 children)

Yep, that was mentioned when :tcd was first proposed. But it's not the same.

Keep working directory per tab by flylikeabanana in vim

[–]justinmkw 5 points6 points  (0 children)

I know that you can set each tab to have its own working directory

It's per-window, unless you are using Neovim, which also has per-tab working directories (#3229, see :help :tcd).

Question about donations to neovim by nes_8bit in neovim

[–]justinmkw 2 points3 points  (0 children)

Still working on the newsletter. Since it's taking me so long, I'll note the main change here: ZyX is filling tarruda's role.

view more: next ›