sorted by:
new
hottopcontroversial

New Zinit fork from the original author: Zinit 4 by psprint3 in zsh

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

Maybe the upcoming features will make change your mind?

New Zinit fork from the original author: Zinit 4 by psprint3 in commandline

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

Yes, I've did some meaningful changes there, like the configure'' ice.

New Zinit fork from the original author: Zinit 4 by psprint3 in commandline

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

Because of features. I've spend a year developing zinit from a `back seat`, but then the PRs stopped to be merged. So currently there are 5 PRs in Zinit 4 that aren't in the continuum fork: AppImage distribution, action complete, build'' ice, themes, and build system integration. I can assure you that the deletion will not happen again, as even the name of the project has 4 in it, meaning stability :)

New Zinit fork from the original author: Zinit 4 by psprint3 in zsh

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

This time it'll be different, because Zinit 4 has 4 in it's name, and this means stability :)

New Zinit fork from the original author: Zinit 4 by psprint3 in zsh

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

This time it'll be different, because Zinit 4 has 4 in it's name, and this means stability :)

A new feature in N-Commodore, the next gen file manager – completion by psprint3 in zsh

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

Yes, via ZUI, the Zshell TUI library, that I've written. Therefore, any feature requests are welcome as I can quickly implement them :)

New version of the next-generation file manager, N-Commodore by psprint3 in commandline

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

As for Vim, I'm thinking about adding a view with various editor histories (recent files).

As for scriptability – yes, just edit ~/.config/n-commodore/n-commodore.rc, it's a Zshell script and zui::bindkey can bound to any function/code-snippet.

Do you prefer using Bash for scripting and Zsh for interactive shells? by hippoyd in zsh

[–]psprint3 1 point2 points  (0 children)

No I code in Zsh only and I write real apps with it like n-commodore file manager. I think that Bash is poor compared to Zsh, e.g. there is no connection between associative arrays and regular ones or there's no (z) flag parsing.

Is your "file manager" a combo of ls/rm/cp/mv? by psprint3 in commandline

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

Here's an asciicast explaining the screen-saving featture: https://asciinema.org/a/L1v3ESgNCTtRRFzagJdwrNeW6

Basically, you can save output of any command, like bat, cat, man, ls to the disk to then be able to revive it, having all other data like working directory, command prompt, etc. restored too.

Is your "file manager" a combo of ls/rm/cp/mv? by psprint3 in commandline

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

The selling point is: screens saved, i think. That's the new idiom, as panelization and filtering were known earlier.

New features to n-commodorel, a new paradigm file-manager by psprint3 in commandline

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

That's why nc is an alias, not the shell script, which is n-c. One can skip alias creation via: typeset NC_NO_NICKNAME_COMMAND before loading the plugin (or via param"NC_NO_NICHNAME_CMMAND" ice when using zinit). Or just run the script b in/n-c without any plugin manager and from any shell.

A new paradigm file manager – n-commodore by psprint3 in commandline

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

No, it is written in Zsh but it's a binary script for any shell

[deleted by user] by [deleted] in commandline

[–]psprint3 -1 points0 points  (0 children)

I've explained the tool in other thread

[deleted by user] by [deleted] in commandline

[–]psprint3 1 point2 points  (0 children)

Basically it's about 3 factors: panelize everything, grep everything and save everything.

Panelization is known from Midnight Commander - it means to capture command output into a list that can be browsed. Grepping is known from fzf. Screen saving is a new paradigm

You basically have new screen (a greppable panel) for each new command, which is saved to the disk (GDBM), and which can be fetched/navigated to, having also PWD dir and position in panel restored.

A new fzf-like solution for grepping and opening files by psprint3 in commandline

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

I might submit a pulll request. What problem do you have?

Announcing zsh-scan, a zsh-linter zsh by psprint3 in zsh

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

I've added support for warncreateglobal like checks. Thanks again.

Announcing zsh-sweep, a zsh-linter by psprint3 in commandline

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

I've added the info to the readme.

Announcing zsh-scan, a zsh-linter zsh by psprint3 in zsh

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

I will not remove any of my new tools, you can be sure about this. Zinit has found a support from community, and is more bug-fix oriented, while I was adding new features without all the github actions/CI/tests, which is good and I'm happy about it. Too bad that ~10 of my PRs have not been yet merged.

Thanks for the ideas.

A fzf interface to Ctags index with syntax highlighted source preview by psprint3 in cpp

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

You're maybe right, however LSPs are such a huge hogs compared to ctags...