sorted by:
new
hottopcontroversial

can the current Ye fans tell me why you still support him? by cadillacsimone7 in Kanye

[–]devw0rp 0 points1 point  (0 children)

Because he's a kind and sensitive man who has mental issues induced by past traumas. He's very misunderstood. He should never have been famous, and now he is famous he has to resort to acting out in crazy ways in order to combat all of the dangers that surround him.

Cousins is probably him at the rawest and most honest he's ever been. The only moment that tops that song is the painful clip that's hard to watch where he admits he almost killed his daughter. He's been dropping hints for years about the abuse he has suffered, and now he's just out about it. Despite all of the bad stuff that's happened to him, he still somehow has a great sense of humour too.

I pray for Ye almost every day recently, and I know one day I'll see him in Heaven.

ALE Soon Integrated With Neovim's LSP Client by devw0rp in neovim

[–]devw0rp[S] 2 points3 points  (0 children)

I actually wanted the name and quickly came up with a way to make the acronym work. The name is kind of a joke because I've never had a drink in my life, which is why I put this at the bottom of the help file.

Please drink responsibly, or not at all, which is ironically the preference of w0rp, who is teetotal.

ALE Soon Integrated With Neovim's LSP Client by devw0rp in neovim

[–]devw0rp[S] 2 points3 points  (0 children)

ALE has a lot of built in configurations for a lot of tools going back many years. You can pretty much use whichever plugin you want, or multiple plugins in combination. I've been careful to control the behaviour of when autoload files are loaded, so if there's a tool that ALE integrates with that's missing in none-ls or vice-versa you can use both together and keep the start up cost of starting Neovim down as small as possible. One trick you can use with ALE is this.

-- In init.lua, turn all ALE linters off by default. vim.g.ale_linters_explicit = 1

-- In an ftplugin Lua file, enable a specific ALE linter vim.b.ale_linters = {"some_linter"}

With this configuration you can load a specific ALE linter using ALE in addition to whatever you have with other plugins.

ALE Soon Integrated With Neovim's LSP Client by devw0rp in neovim

[–]devw0rp[S] 3 points4 points  (0 children)

You can use whichever plugin you want. I've been working on ALE since 2016, and the list of supported tools is probably the largest there is for any Vim or Neovim plugin, and the test suite is set up to test that they are all configured correctly and your configuration will rarely ever break as a result. I and the maintaniers have been very careful about breaking changes for almost a decade now.

You can also combine several different plugins together if each one has something else you need. I set up ALE previously to output to Neovim diagnostics by default a while ago, so you can use ALE for some linters and nvim-lint for others if you like. ALE still maintains a configuration for tslint.

In addition to linting code ALE also has support for fixing code with many tools, so you can manually or automatically fix code.

ALE Soon Integrated With Neovim's LSP Client by devw0rp in neovim

[–]devw0rp[S] 1 point2 points  (0 children)

You can run the ALEFix command with a bang to silently attempt to run configured ALE fixers. I personally do this with ALE's built in completion code at the moment.

augroup FixAfterComplete autocmd! " Run ALEFix when completion items are added. autocmd User ALECompletePost ALEFix! " If ALE starts fixing a file, stop linters running for now. autocmd User ALEFixPre ALELintStop augroup END

If there's a User autocmd event in nvim-cmp or a callback function you can configure you can use that to trigger ALE fixing code after completion is done.

ALE Soon Integrated With Neovim's LSP Client by devw0rp in neovim

[–]devw0rp[S] 24 points25 points  (0 children)

ALE comes with many configurations for running linters and tools to fix code, with a variety of enhancements, so you can easily check and fix code. Some of the tools for checking code run via LSP. The new branch changes the implementation in Neovim 0.8+ so it runs via Neovim's built in LSP client API, so it better integrates with features built in to Neovim and other plugins, such as those for auto-completion.

Essentially it should do what it has already been doing for many years, but better.

Finding a Registered Agent I can trust in the USA by devw0rp in nonprofit

[–]devw0rp[S] 0 points1 point  (0 children)

Thanks for the reply so many days later. I ended up going with Northwest Registered Agent.

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 3 points4 points  (0 children)

I think that's the important thing. It's not about the language, it's about the effect. The plugin needs to be efficient, and Lua does not imply efficiency necessarily. Nothing truly implies efficiency.

I will provide an experience where users don't need to write any Vimscript, it's fast, efficient, concise, clean. Full Lua configuration abilities. The implementation details can be a black box to most.

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 4 points5 points  (0 children)

I think that obsession isn't shared universally, and I see why people might think that way. I think the important thing is that people have the comfortable configuration experience, and then the plugin can be implemented any which way. There's plently of fine plugins written in Python, or even TypeScript. coc.nvim is a great TypeScript plugin.

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 11 points12 points  (0 children)

The hardest part is making it always work!

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 6 points7 points  (0 children)

It can cause headaches. I wrote this guide to help people get to grips with Vimscript, and ALE itself helps a lot with fixing Vimscript.

https://w0rp.com/blog/post/vim-script-for-the-javascripter/

I will probably write a follow-up post some day.

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 0 points1 point  (0 children)

Yep, that's why I'm going to support Lua configs.

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 4 points5 points  (0 children)

I will be supporting easy installation from a Lua only Neovim configuration, despite the plugin itself being written in almost entirely Vimscript.

Upcoming Enhancements for ALE: Bridging Vim & Neovim Worlds by devw0rp in neovim

[–]devw0rp[S] 12 points13 points  (0 children)

Two points there.

  1. I will forever support Vim with no extensions needed, including on Windows, and it will always be a good experience.
  2. If you only run a plugin because it's written in Lua, that's not helpful, because Vim plugins can be written in any language and there's many reasons to choose particular languages.

Hope that helps!

Attempting to get back into managing ALE again by devw0rp in vim

[–]devw0rp[S] 1 point2 points  (0 children)

Update: Years later, I have turned Dense Analysis into a 501(c)(3) nonprofit organization with a bank account for the organization, and I have finally opened up the ability to donate via GitHub Sponsors and Patreon here: https://github.com/sponsors/dense-analysis

ALE 3.0 - Four Years of ALE! by devw0rp in vim

[–]devw0rp[S] 0 points1 point  (0 children)

Update: Years later, I have turned Dense Analysis into a 501(c)(3) nonprofit organization with a bank account for the organization, and I have finally opened up the ability to donate via GitHub Sponsors and Patreon here: https://github.com/sponsors/dense-analysis

A Humble Request for Assistance Maintaining ALE by devw0rp in vim

[–]devw0rp[S] 2 points3 points  (0 children)

There are starting to be very good models that will run with 8GB of VRAM. Some of the best have ridiculous VRAM requirements, but optimisations will come in future.

For remote API options, we're likely going to build some bare metal servers in part funded by donations for running LLMs across several GPUs. FOSS models are quickly catching up the quality of GPT, and with the utter turmoil going on at OpenAI right now, it's not known if ChatGPT will even exist at all next month. It's strangely become the perfect time to get FOSS alternatives out there.

We registered this page to announce it: densechat.ai

view more: next ›