Skip to the content ForoHackers
Log inJoin

kplm9

Joined 29 March 2024

Posts in the forum

  1. Replied in he congelado Git mirando su historia. La CPU está a cero y yo de rodillas

    If the pager is less, press q. Yes, really just q, no ceremony.

  2. Replied in Python 3.13: acabo de corregir la línea del medio sin volver a escribir las dos que estaban bien

    I piped the same function plus a print into the interpreter and also got 96. No lovely editable block appeared. My jealousy would like to know where you got yours.

  3. Replied in diff returned one. My backup email would like everybody to evacuate the shed

    Empty directory, two little files. Identical text: status 0. Different text: 1. Point GNU diff at a name I made up: 2 here. Are you sure the "anything wrong" branch isn't doing three jobs?

  4. Replied in puse umask 077 y el cuaderno viejo sigue tan sociable como el lunes

    It's a mask on creation. For a plain new file requested as 0666, the mask removes permissions from the requested mode. It doesn't walk round revisiting your old files. Monday's got you there, lol.

  5. Replied in Bash has discovered a photograph called *.jpg. I would quite like to see it.

    My partner says this is how the garage forum thing started and I am not allowed to do it again.

  6. Replied in Bash has discovered a photograph called *.jpg. I would quite like to see it.

    Sorted in this Bash script with shopt -s nullglob before the loop. Empty directory, no lines. Kept the quotes around "$f" ; one of the real pictures is called nice hinge.jpg and it's a very nice hing…

  7. Started Bash has discovered a photograph called *.jpg. I would quite like to see it.

    Tiny personal script, nothing clever: for f in .jpg; do printf 'photo: %s\n' "$f"; done . In a directory with two pictures it prints both names. In an empty directory I get a solemn line reading phot…

  8. Replied in Make says my tests are up to date. My tests are an empty directory.

    Tiny wrinkle against past me: I also tried a real file named test instead of the directory. Same message. It wasn't a clever directory feature after all.

  9. Replied in Make says my tests are up to date. My tests are an empty directory.

    RAN twice. Directory still there. No imaginary green certificate. Thank you.

  10. Replied in Make says my tests are up to date. My tests are an empty directory.

    Yep. Empty directory. I renamed it and got RAN. Changed the name back and I've been officially excused from testing again.

  11. Started Make says my tests are up to date. My tests are an empty directory.

    I wrote a Makefile with a test: target that prints RAN. It worked on the workbench computer. On my laptop today: make: 'test' is up to date. I never ran it on this machine. I haven't even broken anyt…