There's nothing specifically bash about it, but here's what the components mean:
"kill" = kill running process
"-9" = kill as forcefully as possible
"$(...)" = command substitution: run the stuff inside the brackets and replace this term with the results (it will be the processes to kill in this case).
"lsof" = list open files (other things like ports and devices count as files on Unix systems)
"-i" = search for internet address
":19421" = local machine, port 19421
I think they're missing a "-t" on lsof, to make it output process IDs only ("terse mode") instead of a human-readable table:
> Consequently, an ocean tide on ancient Venus could have had significant effects on the rotational history of the planet
The implication seems to be that we could answer whether Venus once had water, based on the orbital history of the Earth (over very long time frames), I guess?
I may be wrong but I don't think so. It is not suggested in the article. You'd need to know precisely how fast Venus was spinning when it had oceans. NewAtlas [0] interprets this as ancient ocean possibly being the culprit of Venus' extremely slow rotation period (~243 d.)
I use emacs `-nw` within tmux, on iterm2/3 on mac. There are several terrible problems with this setup which I've never bothered to lose a weekend to trying to sort out (don't misunderstand me: I have lost weekends to some of these problems, and I'm running out of spare weekends).
mac pbcopy/paste into emacs does strange and horrible things. Mouse and scroll-wheel integration roughly doesn't work at all. The list is long.
I also use terminal tools a lot (data engineering), so the terminal itself (and hence tmux) is an important part of my toolset. Meaning, I can't abandon the terminal. Nor do I want to -- as others have said, I have RSI issues with touchpads and mouse-clicking. Spectacle on Mac (or any actual tiling window manager on linux desktops) helps with that, but if I never had to touch a mouse/trackball again in my life, that would be awesome.
As others have said, I mostly want to use an integrated editor and get on with my job, rather than go down a half-century old rabbit hole of reading SICP just to tweak some editor defaults. Again, don't misunderstand me: learning LISP changed my life, man. But that's not the same as "can I enable rainbow delimiters for protobuf" (As an aside, Little Schemer is a much gentler intro to LISP, and also awesome.)
And since I know we're a community of people who get distracted by the next shiny problem to solve: please don't focus on trying to fix the list of issues I'm describing. That's not the point (and I have no spare weekends).
>Mouse and scroll-wheel integration roughly doesn't work at all.
emacs, when started with the -nw flag, has nothing to do with mouse gestures. The terminal emulator (iterm in your case) sits between you and emacs and does not pass mouse gestures to emacs.
Actually, to be painfully precise, there is a convention, which iterm and emacs might or might not use, by which iterm could conceivably pass the location of single left clicks to the emacs process, but, e.g., mouse drag events and scroll-wheel events never get passed.
So for example when the users drags the mouse, then presses Command-C, `emacs -nw` has no way of knowing the user did that, and if anything got into the system clipboard, that is iterm's doing, not emacs's.
Might I suggest `open Emacs.app` rather than `emacs -nw`?
Except for a GNU or Emacs logo that can be suppressed by setting the variable inhibit-startup-screen to non-nil and except for a tool bar that can be suppressed by evalling `(tool-bar-mode -1)`, the result is indistinguishable from a terminal window to most Mac users, but has mouse and scroll-wheel integration.
To be precise, after `(server-start)` is evalled inside the Emacs.app process, whenever the command line `emacsclient <file name>` runs anywhere, inside or outside the Emacs.app process, the Emacs.app "visits" (opens) <file name>.
Honestly, any of them. They're all good. The one I have is three or four years old, and it still works as well as it did when it was new, except for the battery (but it stays plugged in so that doesn't matter). I could easily keep using it for 3–4 more years if it keeps getting map updates.
Every few months I plug it into my computer and leave it to update for a few hours (it's a one-click process), but I think some of the newer ones have Wi-Fi so they can auto-update.
It really depends on what features you want. I've found the voice commands to be quite handy. It has a hard time understanding some addresses, but for stuff like "go home", "turn down the brightness", "navigate to the nearest Tim Hortons", it's great. I wish mine had a built-in dashcam like the newer ones, but they're not cheap. Mine has Bluetooth as well, so it can get more frequent traffic updates from my phone (instead of through the FM receiver), as well as take speakerphone calls.
It's pretty much a single function device, which is perfect. I never have to mess with it, it's always there, and it leaves my phone free for audiobooks or for me to use if I'm in the passenger seat.
Don't know where OP is sailing from, but in my country, it's customary for students students to do a summer internship somewhere in the middle of their undergrad years. In most domains AFAIK internships are without compensation, but programming internships tend to be pretty well paid.
Do it in the summer or between terms. Or delay your graduation. If you think your degree program won't get you a job (or it will be tremendously harder) because you are older & you don't have recent work experience, then try taking 3 months out to get paid 80k as an intern, then coming back and finish your program.
I really feel that for devs coming from unusual backgrounds, you just need a positive recent work entry on your resume. That's all you need to break through.
The parent's confusion stems from the fact that the OP is a nearly-40-year-old man who did programming earlier in his life, quit for 16 years, and is now trying to get back into it. "Do an internship during college" isn't really actionable advice for this guy.
Sorry, I missed that important point, bad reading comprehension. I thought he said he was getting a degree and was a junior in college but I read it again and he didn't mention college. He's looking at "junior engineer" or beginning programmer jobs.
College internships aren't available, he's not a student. Still, he or she needs one recent dev job on his resume, that will unlock further job opportunities. I think going to recruiting events in person and talking to devs and recruiters in person is one way to make that personal connection that could put you over the hump. Go to an event related to your area of biggest interest, try to make a personal connection.
