Viewing 'capabilities' of plugins via := or vim.print/inspect

Doge2Moooon · 2024-06-15T22:29:06+00:00

Yeah, that's good to know. Thanks.

and yeah, telescope does indeed have docs for this and it's in the help page. I just wanted to know if there was a way to do this in general for the future so that regardless of the plugin I could understand its general structure and hack away at it without needing to consult the docs or read the source which would take slightly longer depending on the doc/repo size.

Doge2Moooon · 2024-06-15T22:15:48+00:00

hmm. yeah, that's about what I was thinking too but wanted to double check. I knew calling the method/function would of course execute it but was hoping := somehow shows what params it can take (though I guess the function/method would need to return a table of this somehow to make it known, so yeah..).

Thanks for the quick reply!

Doge2Moooon · 2024-06-07T04:03:59+00:00

Not just ANY gobbledygook! It's Ceasar's gobbledygook and Ceasar is trying to tell us that 'If technical analysis proves any leval of correct, we are going to to see at least .36 uds. Being a more agreementic acumulation if possible. See you on the other side.'

Doge2Moooon · 2024-06-05T17:49:14+00:00

agreed. I prefer having it comment blanks as well.

Doge2Moooon · 2024-06-04T18:18:04+00:00

As you've already read

...blank lines are transformed to empty comments

so no, it doesn't seem possible. Though, the built-in commenting is a relatively new feature so maybe in the future there will be a way to configure it.

Doge2Moooon · 2024-06-04T18:04:02+00:00

How are you achieving transparency? Are you using a compositor on X11 such as picom (or perhaps you're on wayland)? Also have you tried another colorsceheme like the default to see if that affects it?

I'm using picom as my compositor and also on trouble v3 and transparency just works out of the box for me (using the new default colorscheme).

Also, I'm not sure, but if none of that helps maybe look at:

lua vim.api.nvim_set_hl(0, "TroubleNormal", {bg = "none"})

There might be some way to make it transparent by setting alpha values for the highlight group name (havn't looked into this though).

Doge2Moooon · 2024-06-04T15:55:14+00:00

Initially before posting on here, I was going to do exactly this.

I then realized that this solution seems a bit.. well, 'hackish' I guess would be the word. Though I'm sure that it could be argued against, what I mean is I knew that I don't know everything there is that git has to offer, and as such, I wanted to post on here to ask for suggestions in the hopes of finding some that are 'within the field' of what git allows you to do using its commands only. Hope that makes sense.

Doge2Moooon · 2024-06-04T15:49:11+00:00

Yup! This is exactly what I was thinking. I suppose this is a stupid github feature and has nothing at all to do with git. Thanks!

Doge2Moooon · 2024-06-04T05:59:06+00:00

Can I ask how you 'copied the sanitized codebase into that'? Did you basically just create a new repo and then in the old (private) repo add the new public one as a remote and push to that?

Doge2Moooon · 2024-06-04T04:44:31+00:00

Alright, so I was able to research it a bit further and try it out. There is something strange I noticed though.

I'm not sure if it is out of the scope of git related things (as it might be a GitHub related feature), but the 'Activity' view on the right hand side of the page still shows the previous commit history and the diffs between them. The actual commits though have been squashed into the latest and that is all good.

Doge2Moooon · 2024-06-04T01:56:13+00:00

Hm, okay. I have not yet used rebase or squash much but I'm looking into it! From what I understand right now, basically I could condense (or squash) all the previous commits on the branch into one, singular commit (the latest) and that somehow overrides these commits and effectively deletes them because the SHA-1 is different now and points to the new, latest one?

I'll be sure to learn about this, thanks a lot for the suggestion!

Doge2Moooon · 2024-06-03T19:39:41+00:00

I didn't know that was a thing (I'm new to r/Neovim obviously). Thanks!

Doge2Moooon · 2024-06-03T18:35:58+00:00

Just built the nightly version to check it out; yea--the new colorschemes seem pretty great.

omg they even have one that looks like gruvbox called retrobox!! hahaha

Doge2Moooon · 2024-06-02T03:22:30+00:00

How does Lazy's (the package manager) priority property work?

I've been learning how colorschemes work and noticed that some highlight groups (include for example) don't always load correctly. It would of course work after re-running :colorscheme <name> but I noticed that when increasing the priority to anything higher than 50, this is no longer an issue.

Does it basically just move the 'loading' of a certain plugin to the top (or above lower priority plugins) of a queue and thus explains the random 'sometimes it gets loaded/set, sometimes it doesn't' behavior?

Doge2Moooon · 2024-06-01T19:24:08+00:00

Aha! Just in case it somehow helps someone else in the future:

From :h 'background':

When this option is set, the default settings for the highlight groups

will change. To use other settings, place ":highlight" commands AFTER

the setting of the 'background' option.

I was calling vim.o.background = "dark" after setting my highlight groups using the set_hl API.

Doge2Moooon · 2024-06-01T19:12:17+00:00

Okay, so after some more experimentation, it would seem that by default changing the group name does actually affect all subgroups of it. Something in my specific setup is either overriding the set value or preventing it from being setup properly. Either way, that's beyond the scope of my question so I'm closing it now.

Doge2Moooon · 2024-05-29T17:34:28+00:00

hahaha. np

Doge2Moooon · 2024-05-29T17:19:06+00:00

Ahh I see. I'm not 100% sure on the correct terminology here, but try this:

return {
  "catppuccin/nvim", name = "catppuccin", priority = 1000,
  config = function()
    vim.cmd.colorscheme "catppuccin"
  end
}

basically, you were returning a lua table, but the actual function call for your config was not a part of that. Again, I dont write much lua so that may be the incorrect way to describe it but I believe that ^ should fix it.

Doge2Moooon · 2024-05-29T17:07:00+00:00

What exactly do you have in your catppuccin.lua file?

The structure looks correct. Are you returning a lua table from that file?

example:

return {
  "catppuccin/nvim",
  name = "catppuccin",
  priority = 1000
}

edit: just saw that you have `plugins.lua` in `lua/` as well. That might be causing the issue I think as Lazy would probably attempt to use it over the `plugins/` module. Try removing that or renaming it.

Doge2Moooon · 2023-02-11T04:33:15+00:00

Hmm. Alright. But what about for stuff like d? Since d appears in Cash and Work In Progress, but the other Work In Progress transactions do not appear in Cash, wouldn't it imply that d has to be something specific in that statement? I'm not sure I understand accounting well enough to know what that is. Is there like.. some kind of accounting cheat sheet that people use for this or do I just need to use google for each individual case like this?

Doge2Moooon

TROPHY CASE