Neywiny 4 days ago | root | parent | prev | next [–]
My initial thought is you're getting escape sequences or other signals to trigger the bell/chime. I've never had it crash a terminal but I've never really used a macbook. A common one I'll see in gnome terminal is the terminal printing out some info about itself (I guess there's a way to get some info back from the other side of a link) or changing the title bar. An easy test would be to have something dump that bell character to the terminal as fast as possible and see if that does it, and also try /dev/zero to check that doesn't. reply
0points 3 days ago | root | parent | prev | next [–]
That's the ascii bell symbol being rendered on your terminal. See parent's comment, how he piped output from /dev/random into the next command and not to stdout. reply
signa11 4 days ago | root | parent | prev | next [–]
just a guess “visual bell” might fix it perhaps ? reply
0points 3 days ago | root | parent | prev | next [–]
(Sorry if too off-topic) I just saw this and thought this was pretty cool! Running your command in nushell, and eventually aborting it gives the following output ^CError: nu::shell::terminated_by_signal
× External command was terminated by a signal
╭─[entry #28:1:32]
1 │ cat /dev/random | hexdump -C | grep 'ca fe'
· ──┬─
· ╰── terminated by SIGINT (2)
╰────yencabulator 9 hours ago | root | parent | next [–]
Ehh. Nushell error handling is poorly built and buggy as hell. I wanted to use it, I really believed in the sales pitch, but it's just utterly unreliable and I have zero faith left in them ever actually fixing it. - error handling is neglected in the basic design: <https://github.com/nushell/nushell/issues/10633>, <https://github.com/nushell/nushell/issues/10856>, <https://github.com/nushell/nushell/issues/8615>, <https://github.com/nushell/nushell/issues/6617> - control-C interrupts its internals with obviously-wrong error: <https://github.com/nushell/nushell/issues/8828>, is midhandled in other ways <https://github.com/nushell/nushell/issues/8206> - something is horribly wrong with the basic design of command-line arguments: <https://github.com/nushell/nushell/issues/9939>, <https://github.com/nushell/nushell/issues/9766> - they're getting the fundamentals of globs on command lines wrong: if you pass string literals to an external command, they're still processed for globs. this means `ls ""` (internal) and `^ls ""` (external) behave differently: <https://github.com/nushell/nushell/issues/9558> reply
shayonj 4 days ago | parent | prev | next [–]
I have always wondered if anyone used it in a "real life scenario". This was hilarious, thanks for sharing :D reply
imadethis 4 days ago | root | parent | next [–]
When I was in college, the local news was interviewing a comp sec professor of mine in the computer lab. The cameraman was taking B-roll footage (blinking lights from racks, cables going everywhere, that sort of thing). He asked if he could film a few of our screens to show what we were diligently working on, which is how we got hacker typer onto the nightly news. reply
siamese_puff 4 days ago | parent | prev | next [–]
God damn that is funny reply
*
1 point by Ihatefriend 0 minutes ago | prev | next | edit | delete [–]
ban#robloxplayer called Kazyeah pls pls (he is annoying me) I am not a hacker so I wanna learn how to ban people at roblox reply
pjerem 5 days ago | prev | next [–]
LPT : If you are using this website to hack the FBI or whatever, don't forget to triple press SHIFT and to triple press ALT :) reply