this post was submitted on 19 Sep 2023
28 points (71.9% liked)
Technology
59669 readers
3663 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Cool that they have that. Why is there no cliggidy click option to quickly make one? I'd also just take an
ln
command.On Linux at least, the dev directory contains the actual devices. It's not where they are mounted and accessible. Everything is a file on UNIX, so this is where the physical device is, as opposed to its contents.
I know and use wt at work. It's pretty okay, but a major issue that I have with it is that it scales italics weird (at least with FiraCode NF). Also no custom or vim keys for the mark mode thing. For me, kitty is the most usable terminal, and there is no alternative for windows which does everything right (for me, or that I have found).
I won't step down on this one. Shells are made to be used interactively, and PowerShell feels like coding in C#. It's good that they have some aliases, but that's not enough.
Also, new software needs to be added to PATH manually, completion sucks compared to zsh with minimal plugins. Controlling a pwsh session just feels bad.
I'm probably still biased. It's good if you're okay with windows, you got less to worry about I suppose. I just really dislike it, and WI does dislikes me back.
There probably is some shell extension that could add this in context menu. In Windows you use mklink or New-Item commands. Links are not really popular in Windows environment, I would say an absolute majority do not even know about them or never think about them. Shortcuts are the ones that people generally use.
I can accept a compromise of slightly more verbose and standardized syntax for interactive use when compared with unix/linux and ability to easily automate pretty much everything you can in Windows / Microsoft ecosystem. I am not a professional coder, but I thoroughly enjoy scripting in PowerShell for work and private tasks.
True, that's just how Windows programs work. Executables probably will never be available from shell as they can be from Linux without manual tinkering. Start menu is essentially the alternative here. For those couple programs I need to be easily lauched from terminal, adding paths to PATH variable does not seem too much of an problem.