mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Server stats:

5.1K
active users

#zsh

7 posts7 participants1 post today

Can we please have one standard way to define shell completions, that is compatible with all shells?

I'm moving from zsh to nushell, and it's relatively new, and you have to configure completions by writing a lot of code, including a lot of files, it's a nightmare.

It's easier for older shells like zsh or fish only because other people already done it, and some packages include per-shell completions.

There is @carapace_sh which attempts to do the right thing, but having completions in the other place than actual app is not very good idea.

usage.jdx.dev/ is trying to do the same but differently, and it has a way for an app to provide a schema for completions. This is step in the right direction, but not many tools support this.

Has anyone tried to put this somehow on the shell level? E.q. app includes a file like `myapp.completions` , and shell have a module which reads the file and generates a list of completions based on user input.

The right way to do this, is probably by defining a standard cross-platform/cross-shell schema. And it can be read by the shell, or by the tool like carapace or usage...

usage.jdx.devUsageSchema for CLIs
#Linux#zsh#bash

I was using #zsh for the last many years, and I have configured EVERYTHING the way I like.

- Auto-completions
- Per-directory history
- #McFly for Ctrl-R quick search
- Aliases

Now I'm moving to #nushell and I want to configure everything in the same way. But, per-directory history is either broken or non-existent: github.com/nushell/nushell/dis

People do not use per-directory history? This is AWESOME, every time you switch directory you have your entire relevant history at your fingertips. I recommend everyone to try it.

zsh has per-directory-history plugin (i was using oh-my-zsh)
#atuin has even better search, you can filter by workspace/directory/session/...

Atuin has solved missing/broken per-directory history partially, but god I want this to be default in all shells.

Linus Torvalds has proper motivated reasons for really disliking file systems without a case sensitivity.

Read this with me from the kernel lkml, regarding bcachefs.

Re: [GIT PULL] bcachefs fixes for 6.15-rc4 - Linus Torvalds
lore.kernel.org/lkml/CAHk-=wja

🖋️ #bash #sh #zsh #ksh #csh #tcsh #fish #git #Linux #lkml #POSIX #FOSS #100daysofCode #640DaysOfCode #coding #1024DaysOfCode #github #programming #Torvalds #filesystem

Replied in thread

I still need some more feel at home config help. As you can see here I love having vertical gradients on my displays, but in KDE and Vallpaper I have not found how I can set gradients on the side of my wallpaper which are deliberately not 16:9 since I love to look at (vertical) gradients. Where do I need to look to achieve that? Is there a KDE action that I need to define for all my 20 KDE desktops?

.🖋️ #xFace #KDE #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #gPartEd #Gnome #Linux #POSIX #fresh #programming #hugo #gvfs #backgrounds #wallpaper #Vallpaper #gufw

Replied in thread

Im starting to achieve platform distro OS translucency regarding more and more projects. Now I can smoothly work in my hugo projects from any distro I want in Linux. All I need to do is keep the copies I work on in sync.
Since I dont run zfs jet on a centralized HDD / SSD I simply use mc -a to do the job manually.
Normally it should be trivial, but the hugo projects want rm -Rf dir otherwise old files with similar size can be changed, thus screwing up continuity

Since my KDE MX install is moothing out in cfg features I need, which is a combo of XFce components and KDE, I can smoothly switch to the KDE distro and work further while I tune it.

I chose to keep XFce seperate from KDE distro wise due to size constraints I;ve put on my boot partition

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #gPartEd #xFace #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper #gufw

Replied in thread

@rl_dane

I have KDE on a semi permanent installation on a 2.5" Drive. If you have been following my toots you know at which level I am with it again after a couple of decades

It's nothing in ease of use, compared to my XFce Desktop ENV: where I have all shortcuts I want in muscle memory, however KDE has become much more powerful in the couple of decades I've not looked at it.

Replied in thread

The next step was to config KDE connect in this KDE. Luckily I know that I need gufw to migrate my profile, from the xFce MX linux to this KDE MX linux.
It was a matter of installing gufw, which is not default in KDE distro, since it has its own nice interface. For me sticking with what I know is the easiest since I want to drive KDE on desktop again after so many decades, even though XFce is still going to be used most, due to shortcut muscle memory

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper

Replied in thread

I also encountered another problem; I can immediately tell you that it's not a KDE specific problem but it popped up in konsole.

The subject is fonts and the section is point size. The monitors I use are not of a small resolution. In fact an ideal IPS LED panel layout for me would be an 8K panel two 4K panels flanking it and two 1080p ultra ultra wide panels at a left and right of those.

With such a setup I can monitor different machines at the glance and control them with ease.

Even on my 1080p Ultra Ultra wide panel the default Point sizes for fonts are too small. On a scratch KDE based MX Linux installation, the following problem was repeated twice in Konsole.

The first time I changed font point sizes, closed konsole. When I reopened konsole the fixed with font, was replaced with one that appended spaces behind every couple of letters.

This rendered konsole unusable for work.

Changing the fonts Point sizes to the defaults again did not fix the problem.
Sinds that installation was Vanilla and didn't have enough space for home and root on one partition to actually Play with KDE, I wiped it and started again.

This time I deliberately did not change the point sizes even though it was hard to read. I then copied over some configuration directories from my other installation to this One, none of them related to anything KDE wise or any fonts directory. When I rebooted that installation The problem occurred for the second Time.

As with the wallpaper issue, I immediately converted that energy of irritation to something positive. I troubleshooted the font problem for a short while and when I couldn't isolate it I did a simple thing. I created a couple of other accounts on the same KDE installation to see if I could repeat the error.

That reproduction step is vital before a bug report is created. The other accounts were also residing on my other xFace MX Linux installations, which means I could simply copy them over to the other home partition where KDE was looking at.

In the other accounts I could not repeat the error.

That means a bug report is worthless because repeatability is crucial. Since the usage of a terminal in the K Desktop Environment is important, I changed my strategy and simply installed the xFace Four terminal in KDE. In the end that was a nice move since I know all the keyboard shortcuts of the terminal by hand they are in muscle memory and they have been there for years.

As a bonus I also installed other good shells in MX KDE the hashtags tell you which.

Right now I have a KDE installation in which I can actually work based upon the MX Linux KDE variant

I shall link a couple of photographs in a few minutes

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish  #distro #KDE  #Gnome #Linux #POSIX  #fresh #programming  #backgrounds #wallpaper #Vallpaper

Continued thread

My next step was something unexpected.

In XFce4 my desktops all have different backgrounds per IPS Led Panel. Its a matter if context menu key (on my keyboard I have one) select background and move the program to the next display beside it and repeat, then move it to the next desktop, display besides AD Infinitum

KDE says HELL NO to that ease.
I did some reasearch and saw that it was easy peasy in KDE 4.5.x then got replaced with activities in KDE Plasma 5.x
The simple command is now either kwin scripts or a lot of keystrokes and time.

Instead of getting pissed I went further and found that what the programmers replaced with activities (which are POWERFULL and versatile) and also usuable for wallpapers per VTop (Virtual desktop) was eased back (in 2022) with VallPaper

Source is here

cadence.moe/blog/2022-12-03-im

.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper

cadence.moeImplementing different wallpapers on KDE virtual desktops - cadence's weblog (personal blog)