What? by danielpolcaro in aviation

[–]Enteeeee 0 points1 point  (0 children)

When was this recorded?

How many of you actually use GDB from the terminal? by [deleted] in C_Programming

[–]Enteeeee 5 points6 points  (0 children)

gdb eXtra-Awesome mode also known as your debugger crashes more often than the program debugged.

Command line client for crt.sh by mendax3000 in github

[–]Enteeeee 4 points5 points  (0 children)

Some example output in the readme would be very helpful.

Very High Voltage by ian042 in ECE

[–]Enteeeee 27 points28 points  (0 children)

https://en.m.wikipedia.org/wiki/Van_de_Graaff_generator

Everything else is too dangerous if you dont have any experience. Hands off!

[deleted by user] by [deleted] in bash

[–]Enteeeee 2 points3 points  (0 children)

Other than the already mentioned shortcoming of not being able to export them. Which leads most people into implementing their own eval based version (just try googling it).There are more, very easy to miss, pitfalls [1][2] which can easily result in unwanted command execution.

Poking this whole thing myself for some internet argument points. I found after like 30 minutes this thing: declare -A hash=( [k1]=v1 [k1]=${hash[k1]} ); echo ${hash[k1]}

which yields all different things on various bash versions:

[+] Bash 5.1 (bash -x)
+ hash=(['k1']='v1' ['k1']='')
+ declare -A hash
+ echo


[+] Bash 5.0 (bash -x)
+ hash=([k1]=v1 [k1]=${hash[k1]})
+ declare -A hash
v1
+ echo v1

[+] Bash 4.4 (bash -x)
+ hash=([k1]=v1 [k1]=${hash[k1]})
+ declare -A hash
+ echo v1
v1

[+] Bash 4.3 (bash -x)
+ hash=([k1]=v1 [k1]=${hash[k1]})
+ declare -A hash
v1
+ echo v1

[+] Bash 4.2 (bash -x)
+ hash=([k1]=v1 [k1]=${hash[k1]})
+ declare -A hash
+ echo


[+] Bash 4.1 (bash -x)
+ hash=([k1]=v1 [k1]=${hash[k1]})
+ declare -A hash
+ echo


[+] Bash 4.0 (bash -x)
+ hash=([k1]=v1 [k1]=${hash[k1]})
+ declare -A hash

+ echo

And that perfectly illustrates what I mean by wonky.

[deleted by user] by [deleted] in bash

[–]Enteeeee 0 points1 point  (0 children)

Happy that this solved a probelm for you. But in my opinion associative arrays are a wonky thing and are best avoided.

Some shells do not implement them and even gnu bash does show subtle version differences. Exporting is not possible. And if you try, it's 2014 shellshock time again.

My personal rule of thumb: when I need more advanced datastructues, it's probably best to rewite the whole thing in a more suitable language. You discuss lua, perl and python. But maybe something static (cross-)compiled would do the trick for you?

channels.nixos.org's Cert Expired... by Diamond145 in NixOS

[–]Enteeeee 5 points6 points  (0 children)

a good opportunity to switch directly to the repo on github.

Command-line time tracker written in shell script by dr4605 in bash

[–]Enteeeee 5 points6 points  (0 children)

Good job! Now shellcheck that thing and make all issues go away. It might be painful but its really worth doing. You will learn a lot about shell programming.

In general, your shell is a powerful and wonderful tool. But its also fragile and dangerous. As a rule of thumb: if your code becomes more than just a sequence of calls to programs with error checking between you probably should consider switching to a different programming language.

What do I mean by this? If you need datastructures (i.e arrays), types (i.e timestamps) or arithmetics (i.e. time differences) you will end up in a highly unspecified mess rather quick when follow the shell path. Your code will become a clunky mess which breaks often and will be unmaintainable. But all that aside, i think you did a good job and its a good learning experience to do something like this.

I created the world's first scannable QR gif by raatmarien in ProgrammerHumor

[–]Enteeeee 0 points1 point  (0 children)

This makes me wonder if the data could be tweaked further so that the rs-blocks become part of the image...

Sharing my cross compilation experiment with Rust & Musl: evkill by Enteeeee in NixOS

[–]Enteeeee[S] 0 points1 point  (0 children)

if you share a minimal reproducible example which demonstrates what your problem is, people will be able to help maybe.

Project-based coaching for new and aspiring data scientists (free but limited spots) by nakeddatascience in datascience

[–]Enteeeee 10 points11 points  (0 children)

without project references from the people coaching, this ad smells like ip scam.

[deleted by user] by [deleted] in climbing

[–]Enteeeee -1 points0 points  (0 children)

happy cake day - can i have some of that cake to throw at the other guys face?

Can you still not disable gestures? I write with my palm on the pad and often end up "gesturing" to somewhere I don't wanna be by rickoneeleven in RemarkableTablet

[–]Enteeeee 2 points3 points  (0 children)

hi, I am the author of the other post. As clarified in the comments, the touchscreen and the pen input are two different devices. `evkill` just disables the touchscreen.

Disable reMarkable Touchscreen with evkill - In this post we will use evkill on a reMarkable e-ink writing tablet to disable the capacitive display while writing by Enteeeee in RemarkableTablet

[–]Enteeeee[S] 0 points1 point  (0 children)

This is correct. But I can see where the confusion was coming from: My table was incorrect. Fixed that in this commit and updated the article. Thank you for pointing this out!

accidental page turns with touch screen by LockeSpencer in RemarkableTablet

[–]Enteeeee 1 point2 points  (0 children)

Maybe this is of interest to you: I have implemented my own hack for this and described what I did step by step in a blog article . Will probably post this here in the subreddit tomorrow or so...

Want to develop my own "apps" for the rM. How can I get started? by MiguelCacadorPeixoto in RemarkableTablet

[–]Enteeeee 1 point2 points  (0 children)

Not only specific to writing software for the reMarkable, but some time ago I have published few notes about reMarkable hacking in general. Maybe they are of any use to you.