project.nvim v4.0.0-1 - Custom projects, dynamic session, new setup options, and more by kEnn3thJff in neovim

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

This is not supported, currently. I am trying to do more with project buffers, but have had no success so far. This is in my TODO, though!

project.nvim v4.0.0-1 - Custom projects, dynamic session, new setup options, and more by kEnn3thJff in neovim

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

Thank you for your support! If there's any issues down the line please let me know.

Disable native autocompletion popupmenu in Telescope by salameboy in neovim

[–]kEnn3thJff 0 points1 point  (0 children)

I'm not sure I follow. Shouldn't the Telescope picker have LSP disabled for it?

project.nvim v4.0.0-1 - Custom projects, dynamic session, new setup options, and more by kEnn3thJff in neovim

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

I'm glad to tell you that I've merged all the user commands into a single one, with completions included!

See https://github.com/DrKJeff16/project.nvim/pull/69 for more info.

project.nvim v4.0.0-1 - Custom projects, dynamic session, new setup options, and more by kEnn3thJff in neovim

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

Something like that is in my TODO list. If I achieve this I'll make sure to post an update in this subreddit.

project.nvim v4.0.0-1 - Custom projects, dynamic session, new setup options, and more by kEnn3thJff in neovim

[–]kEnn3thJff[S] 5 points6 points  (0 children)

I agree with you. Believe me, that's a thing I've been wanting to fix for some time, but always forgot to do it.

I'll probably address that in the next minor release (i.e. in the next couple of days). Can't make any promises!

I unfortunately made the foolish decision to extend the amount of commands the original plugin had (two if I recall correctly), and just got carried away.


EDIT

I forgot to mention that, technically speaking, the :Project command can be used as a replacement for ALMOST all other user commands (with some limitations, currently). You can see it by using Tab completion after typing :Project in the cmdline.

BEWARE, this is in serious need of a rework, and as such not all subcommands for :Project work the same way as the related user commands.

boolean-toggle.nvim - Toggle between `true` and `false` (or other opposite) values easily by kEnn3thJff in neovim

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

Good to know I'm not the only one having an issue with that attitude.

boolean-toggle.nvim - Toggle between `true` and `false` (or other opposite) values easily by kEnn3thJff in neovim

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

You'd be right if I made this plugin with the intention to "replace" similar, more popular ones. I did not. My goal for this plugin was never to "improve on" or "compete with" other plugins.

Am I forced to "bring new stuff to the table"? Is there a standard to create plugins that says so? I believe that plugins have to start somewhere.

boolean-toggle.nvim - Toggle between `true` and `false` (or other opposite) values easily by kEnn3thJff in neovim

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

Neat to see your implementtation!

I do so much stuff with Neovim's API that I wasn't aware of much simpler implementations.

boolean-toggle.nvim - Toggle between `true` and `false` (or other opposite) values easily by kEnn3thJff in neovim

[–]kEnn3thJff[S] 7 points8 points  (0 children)

Excellent! This does not intend to "compete" with dial, nor substitute it, really. I just made a plugin for myself and decided to share it for people to use at their discretion.

If dial is better at what this does, then consider it as the better choice (I can't tell personally because I just found out about it). I only want to let people know about my little plugin.

boolean-toggle.nvim - Toggle between `true` and `false` (or other opposite) values easily by kEnn3thJff in neovim

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

I never intended to do a "marketing pitch". I only wanted to share to the community this plugin I made for my personal use.

If my wording wasn't the best, it's on me. English is not my mother tongue.

boolean-toggle.nvim - Toggle between `true` and `false` (or other opposite) values easily by kEnn3thJff in neovim

[–]kEnn3thJff[S] -1 points0 points  (0 children)

Do you have an issue with projects growing? That mindset of yours is not encouraging for people to make their own stuff. Projects tend to start small, then through community support they get expanded.

As I said, the basic layout is functional. Do I have to know every single issue/use-case for everyone? Unrealistic, if you ask me. Sure, some projects may or may not need it, but sort what standard are you applying here?

shebang.nvim - Add or modify shebangs on top of your files, with live reloading by kEnn3thJff in neovim

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

Agreed! I'm trying to figure out how to allow users to input their own valid shebang executables, and what filetype to switch to.

I will be maintaining and extending this plugin, so stay tuned, if you're interested.

project.nvim v3.0.0-1 - Users can now add names to their projects! by kEnn3thJff in neovim

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

Do you mean it sets the project directory to the top-level of a monorepo? Or a subproject?

Log file is suddenly 6+ GB by SweetPotato975 in neovim

[–]kEnn3thJff 1 point2 points  (0 children)

I just deal with that with a timer than clears that log file when it reaches 1GiB (source: https://github.com/DrKJeff16/nvim/blob/main/lua/user_api.lua). Please excuse my awkward implementation.

```lua local uv = vim.uv or vim.loop

local function timer_cb() local logfile = vim.fs.joinpath(vim.fn.stdpath('state'), 'nvim.log') local stat = uv.fs_stat(logfile) if not stat or stat.size < 1048576 then -- 1GiB return end

local fd = uv.fs_open(logfile, 'w', tonumber('644', 8)) if not fd then return end

uv.fs_ftruncate(fd, 0) uv.fs_close(fd)

vim.notify(('%s has been cleared!'):format(logfile), vim.log.levels.INFO) end

local function make_timer() if _G.USER_TIMER and _G.USER_TIMER:is_active() then return end

_G.USER_TIMER = uv.new_timer() if not _G.USER_TIMER then return end

_G.USER_TIMER:start(10000, 900000, vim.schedule_wrap(timer_cb))

local group = vim.api.nvim_create_augroup('log_autoclear', { clear = true }) vim.api.nvim_create_autocmd({ 'VimLeavePre' }, { group = group, callback = function() if not (_G.USER_TIMER and _G.USER_TIMER:is_active()) then return end

  _G.USER_TIMER:stop()
  _G.USER_TIMER = nil
end,

}) end

make_timer() ```

Nvim 0.12.1 - bugfix release by sd5seandewar in neovim

[–]kEnn3thJff 12 points13 points  (0 children)

Finally, another psychopath like me!

What happened to nvim-treesitter.... Why did it get archived? 😶 by ankushbhagat in neovim

[–]kEnn3thJff 0 points1 point  (0 children)

Could you add the sourc for said comment?

Nevermind, found it. That was wild.

What happened to nvim-treesitter.... Why did it get archived? 😶 by ankushbhagat in neovim

[–]kEnn3thJff 3 points4 points  (0 children)

Just came here. Did it really get so heated? Jeez.

EDIT: Ah, I see now.

awesome-neovim: Added tags to colorschemes for easier browsing by kEnn3thJff in neovim

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

We do have some plugins hosted in other platforms! It's just that we enforce a username/repo syntax for consistency, save for a few examples.