161–170 of 177 posts
Earlier quoted context omitted.
Speaking of heritage... 8+3 goes back at least to DECSystem-10 on PDP-10s.
Everything goes back to the PDP-10 we are all using the incestuous off-spring of DEC. Whether that is good or bad is left as an exercise to the reader.
I use different namespaces for different convenience scripts, and use the notation [character].[command] for all of them. I've used a character for each company I've worked for, and a different one for common scripts. This way is very easy to clean $HOME when I move.
do.item Add an item to the bottom of my todo list
do.soon List the items that I need to do soon
do.next List the next item to work on
do.mark Mark the current item done
I dislike this immensely. It costs nothing to type "~/bin" in front of the command each and every time. And it means I can put comma's wherever I want in some commands that use them, like SQL .. I do, however, like to comment my custom commands: $ mv ~/Desktop/*pdf ~/Documents/PDF # pdfsync $ for i in ~/Documents/Development/JUCE/JUCE_Projects/* ; do ; cowsay $i ; cd $i ; git pull ; git fetch --all ; git submodule up…
You can do what you want but it’s not nothing: it costs six keystrokes every time (seven, counting shift for tilde)
Earlier quoted context omitted.
What is "system path"? Every tool inherits the caller's path. I don't think this could be a problem unless a tool talked directly to systemd to execute itself.
Default PATH minus ~/bin.
Earlier quoted context omitted.
> One drawback is that this doesn't have the same tab completion ergonomics, which I have to admit is really nifty. They do in zsh
I meant specifically that you can quickly see all your custom scripts (and only them) by tab-completing comma itself. Of course aliases have regular tab completion in bash as well.
Of course - your own custom scripts usually wont have so fancy completion, and in any case you'd need to configure this and setting it up for both the long and short version is not that much hassle.
Earlier quoted context omitted.
There is no "default PATH", the default is inheriting the parent process's.
I’m here to communicate not be pedantic. I’m sure you could understand what I meant.
if a tool looks up a command name "x" given to it, it just takes $PATH and goes through it. the same $PATH as in your shell when you call "x" directly.
thinking more about it, you must thought something like putting "@daily mycommand ..." in crontab, then being annoyed by it not finding your command. then the problem is not that some tools expecting a "system path", but that some tools being defiant and overrides inherited path on their own accord. which is totally unneccessary: environment is called environment because it is prepared for you (the given program) to run in.
I use different namespaces for different convenience scripts, and use the notation [character].[command] for all of them. I've used a character for each company I've worked for, and a different one for common scripts. This way is very easy to clean $HOME when I move.
I like the idea of using periods for collections of commands. I have a todo list hacked together with shell scripts and I've been thinking about how I might want to stay away from collisions. I think I'll use do.thing style commands, so my commands will be: do.item Add an item to the bottom of my todo list do.soon List the items that I need to do soon do.next List the next item to work on do.mark Mark the current ite…
Exactly. It's super barebones but it works haha.