I love this new channel, very informative and fun :)
@annieworroll4373
Жыл бұрын
It took me a while but I finally got in the habit of doing this. Very useful.
@waterlysubstance
Жыл бұрын
Awesome videos, man. Wish you the best here, and thanks for the tips 😁👍
@nixtricks
Жыл бұрын
Thanks! It means a lot, really glad to be of help!
@basicbasedidot2547
Жыл бұрын
Great video very informative also you should do a vid on pipes
@AndersJackson
Жыл бұрын
Tab is used in Emacs for entering file name in C-x C-f or when entering Emacs commands with M-x I can't think how I would live without TAB expansions anymore.
@pewdiepiezzzzz124
Жыл бұрын
awesome
@thejonte
Жыл бұрын
I see you use Davinci Resolve for your editing! Nice. Do you have pro or do you just ffmpeg it?
@nixtricks
Жыл бұрын
It's the basic free tier (seems enough for now) and sometimes ffmpeg, but in most cases DaVinci is just happy with OBS encoding settings.
@thejonte
Жыл бұрын
@@nixtricks Cool! Thanks for the Insight! Love your stuff.
@shatteredvidrio
Жыл бұрын
Some commands you can't get completions with... like `flatpak run ` and others... how to add 'em?
@shallex5744
Жыл бұрын
i don't know much about it but it seems that all bash completions come from files in /usr/share/bash-completions on arch, i have some files in there, but i don't get bash completions whatsoever for program arguments, so perhaps it's something i need to turn on
@nixtricks
Жыл бұрын
I would first check that the bash completion script is not outdated somehow, but if you feel like tinkering or need it for custom stuff, you can write your own functions inside of scripts you can store under "/etc/bash_completion.d". The "compgen" and "complete" commands can help build autocomplete lists and register them properly.
@tomaszgasior772
Жыл бұрын
Probably shell completions are not supported by Flatpak. And that's fine since Flatpak is designed for desktop applications and not for command line ones.
@zxGHOSTr
Жыл бұрын
Which keyboard are you using in this video?
@nixtricks
Жыл бұрын
MX Keys from logitech.
@zxGHOSTr
Жыл бұрын
@@nixtricksthx
@UltimatePerfection
Жыл бұрын
Isn't this feature a little bit too basic though? And I mean "so basic, even Winblows has it" by it.
@smorrow
Жыл бұрын
Tab is such an obviously bad key to put completion on though. 1) You lose the ability to actually type tabs (you can type tab with ^V, but why not type it by just typing it...) 2) All completion types get overloaded onto one key. Plan 9 did it right by putting filename completion on ^F. That way if they ever have command, environment, domain-name, dictionary, [whatever] completion they can put it on ^C, ^E, etc.
@shallex5744
Жыл бұрын
i didn't know that anyone would ever want to type a tab on the command line
@smorrow
Жыл бұрын
@@shallex5744 With elastic tabstop support it would be very cool to have tabs. Also, I think it would be cool if the history mechanism, instead of up and down arrow cycling whole commands, just cycled the current column that you're in (and you columnate your command lines on the way in using tab).
@trueriver1950
Жыл бұрын
I agree with your first point I don't get your second point though. The system knows where you are on the command line, and whether it is expecting a command or a filename or a subcommand or whatever, so the overloading is never ambiguous. Or am I missing your point?
@bazoo513
Жыл бұрын
1:06 - Even in Windows cmd.exe.
@trueriver1950
Жыл бұрын
Even in ms-dos you could add tab completion (if I remember rightly it wasn't standard, but you could add a TSR to do it) I don't know if it started on UNIX and was copied by everyone else, or whether Unix copied the idea just like everyone else; but it certainly goes back a long way.
@bazoo513
Жыл бұрын
@@trueriver1950 Yaay, Terminate and Stay Resident! I haven't heard that phrase in decades! Are we old-timers or not 😀
@bazoo513
Жыл бұрын
@@trueriver1950 According to Wikipedia (what else), is started on Berkeley Timesharing System in '60s, then improved on Tenex and TOPS-20. Unix probably took it from the latter, and MS-DOS from either.
@trueriver1950
Жыл бұрын
@@bazoo513 fair enough. My experience starts really with DOS in various forms. (Rest of post off topic so feel free to skip) In mid to late sixties I was still at school. Mid sixties wrote my first computer programs in Fortran IV, on punch cards. School could not afford an electric card punch so we had to punch the cards by hand after memorising the Hollerith code. You had to be a kid to be willing to do that. Twice a week a teacher took them into a university to be run, and we got them the next morning. It could take weeks to get simple code running. We never attempted anything than the 60 or so lines on a line printer page. Late sixties, still at school, school was the first one in UK to have a live link to a computer: a 300 baud modem which took up 3U in a standard 19" rack. We had to stay till after 6pm to use it; not because of the competing charges but because the dial up cost the school more than the computer time during the day It wasn't till the Amstrad home PCs came along that I actually had a computer I could call my own; around 1983 if I recall. Hence my knowledge starts abruptly with MS-DOS, DR-DOS, and hacks like installing ANSI.SYS to be able to look backwards through command history.
Пікірлер: 27