Hacker Newsnew | past | comments | ask | show | jobs | submit | amcpu's commentslogin

Nuts!


I use a locally hosted YaCy instance with cached results to work around this scenario. Much of the content I am interested in is kept locally, so it’s good enough. When I have a bunch of “read later” tabs that pile up, I copy all their URLs into the crawler form with “Store to Web Cache” checked and it accomplishes what I described. Just another option to consider.


The dive utility helps tremendously for exploring the filesystem contents of a container image. Combine that with the output of `docker inspect` to look at the metadata and you should be able to have a good understanding of what it will do when running as a container.


Evaluating the whole contents of a filesystem is significantly more complex than evaluating one shell script.


Came here to scan the comments for someone else who would have posted that reference. So glad I found it! :)


Me too


You could also use the vim :%!python3 your_script.py (where your_script.py does the work to format the text) command that takes the text of the buffer as stdin to the script and replaces the buffer contents with stdout of the script. This can also be combined with visual mode linewise to only replace specific lines of the buffer (must work on entire lines selected).


Sounds like something out of https://blog.codinghorror.com ! :)


I’ve been having good success with _basic_ outlining functionality of Org Mode in VS Code using the “VS Code Org Mode” extension. No need for emacs for this use case. The built-in VS Code folding works really well and then combining with GitLab which has rendering support for Org Mode when committing/pushing commits. Plus, since everything I’m doing is already in Org Mode syntax, I can move to other editors later if desired. It’s a good solution for my needs, at least.


I honestly cannot remember ever typing sl instead of ls. Funny little “utility” in place there. It doesn’t appear to be part of a minimal Ubuntu installation, have you found it install “out of the box” with any Linux distros?


Doesn’t happen for “ls” for me, but I type “funciton” and “exmaple” all the time.


I basically never make any letter swap typos at all. I guess it's more common with faster typists that are using more fingers at once, and going fast enough that they aren't thinking one individual letters?


Maybe you forget about them.

I never noticed myself doing it either. But after learning of Emacs (and MacOS) "transpose" shortcut C-t (aka Control-T on macs), I find I use it about once every 1-2 weeks.

It's not even faster than deleting the word and re-typing it, no. It's just funny.


I did not know about transpose but I am now fully convinced that Emacs shortcuts can be art.

Really, I tried it out and giggled out loud. Now how do I go about sharing this joke with my friends? "It all started in 1976... let me tell you about bucky bits."


Lol I would not have guessed Mac would have a shortcut like that!


Yeah, it's great, and that's not the only one. Mac OS supports a whole bunch of emacs style text editing commands. I wish I could replicate in Linux.


I find that it largely depends on the keyboard that I'm using, but I can think of two scenarios when it happens to me.

If I'm typing at a steady pace ( no matter the speed), when a finger doesn't get the tactile feedback it expects, it may hesitate while the next finger strikes the next key on the same pace.

And for short commands like, `ls` or `cat`, I often hit the all the letters at nearly the same time which can swap letters.


Slow typist here, I make letter swap typos all the time. Cmd+T is my best friend.

Curious if other aphantastics are similarly slow/error prone? I cannot visualize a keyboard, and while I can usually type without looking, my form is poor and I do steal occasional glances.


I don't think aphantasia matters here.

I don't have a visual representation of the keyboard in my mind at all, but having touch typed (imperfectly) since high school, I can tell when I mistyped a key by feel too (eg. not looking at the output on the screen either, your muscle memory will let you know if any movement was awkard or unexpected).

FWIW, it's important to learn where the "corrective" (backspace, delete, cursor movement...) keys are on your keyboard while looking at the output: then you can easily push yourself to not look down on the keyboard while practicing.


Aphantastic here. I never learned to visualize a keyboard and went with blank keycaps to force myself to learn with weeks of painful brute force muscle memory. I learned Colemak which is much less finger travel and helped too as many words can be typed with home row.

I also do everything I possibly can on the command line because it is -one- interface to learn with a universal history to reference past commands vs randomly mucking about in GUI interfaces I can not picture in my head that are wildly different in every application.


Aphantastic here to say I have always had pretty great touch typing. In high school I would touch type on a HW keyboard phone - great to reply to texts while looking at my teacher for their presentation.

I do make mistakes but I don't feel particularly slow or error prone. As I said elsewhere I like to use the C-t command to fix letter swaps and I get them definitely less than once per normal day.


I never visualize the keyboard even though I could, it's all muscle memory.


Huh, maybe it has more to do with whether you type without looking or not?


Anecdotally I'm 130wpm+ and I make that typo a few times a week.


recent distros or of all time?


Any, I was just curious. :)


> Eat corn while listening to Korn music while using the Korn shell. … to compile the kernel.


All before the close of business: COB.


Finally HN has reddit beat on puns.


You seem to have an ear for puns.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: