[X] My Assistant

I need to stop delaying the cleaning of my pc (going on 7 months).

This post has been edited by hoigoigoi: May 29 2019, 03:08

I need to stop delaying the cleaning of my pc (going on 7 months).

You'll be fine

1stPlayer claimed the brand name "Steampunk" is a metaphor of sort, representing the "spirit in pursuit of extreme" (according to their interpretation). Everyone else however completely disagree, arguing the manufacturer should have employed Steampunk-inspired aesthetics in its PSU. 1stPlayer then shot back, with a rhetorical question: "Does the Black Widow (brand of PSUs) have (an actual) widow in it?" Damn, it was hilarious.

This post has been edited by Super-hujan86: Jun 4 2019, 03:51

Who?

Last thing I thought:
I've written better scripts for calibrating touch screens than the people making the xf86-input-wacom driver seem to be capable of making. Wish they'd get their acts together.
This script is written and tested in ksh93 (KornShell '93), but should work in bash and maybe others.

CODE

#! /usr/bin/ksh
# calib
#xsetwacom set 'Wacom Serial Penabled 2FG Touchscreen Pen stylus' \
#          Area 0 137 26130 16293
# min_X min_Y max_X max_Y

# less parsing to do later if we just snag the device name now (if available)
case "$#" in
  1)
    devicename="$1"
;;
  5)
    devicename="$1"
;;
  *)
    devicename=""
;;
esac
# This script remaps our arguments for consistency between xsetwacom and the
# calibrator tool xinput_calibrator. It uses xsetwacom format. It acts as
# a translator to avoid user confusion (meaning: to avoid my own confusion).

# the docalib function gets piped into a loop that reads the output of
# xinput_calibrator line-by-line to scrape the information we need.
docalib(){
  case "$#" in
    0)
      xinput_calibrator
;;
    1)
      xinput_calibrator --device "$1"
;;
    4)
      # xinput_calibrator takes precalib in form of: min_x max_x min_y max_y.
      # Unfortunately, xsetwacom uses the form of:   min_x min_y max_x max_y.
      # so we swap the middle two parameters from the order passed.
      # (When we are done, the script returns in xsetwacom format)
      xinput_calibrator --precalib "$1" "$3" "$2" "$4"
;;
    5)
      xinput_calibrator --device "$1" --precalib "$2" "$4" "$3" "$5"
;;
    *)
      >&2 echo "Wrong number of arguments given. Should be one of:"
      >&2 echo "    0 - use defaults for everything."
      >&2 echo "    1 - Specify a device name."
      >&2 echo "    4 - Enter previous calibration settings."
      >&2 echo "    5 - Specify a device name followed by previous calibration settings."
      >&2 echo "Calibration settings should be passed in the order of:"
      >&2 echo "    TopLeftX TopLeftY BottomRightX BottomRightY"
      >&2 echo
      >&2 echo "Please try again."
      exit
;;
  esac
}

# 0    137    26130    16293
# min_X    min_Y    max_X    max_Y
MinX="ERROR"
MinY="ERROR"
MaxX="ERROR"
MaxY="ERROR"
docalib "$@" | \
  while read line; do
    echo "$line" | grep -q '^Calibrating standard Xorg driver'
    if [ "$?" -eq 0 ]; then
      if [ -z "$devicename" ]; then
        devicename="$(echo "$line" | cut -d\  -f5- | sed 's/"//g')"
      fi
    fi
    echo "$line" | grep -q '^Option'
    if [ "$?" -eq 0 ]; then
      
      varname="$(echo "$line" | awk '{print $2}' | sed 's/"//g')"
#     echo "VARNAME: ""$varname"
      varval="$(echo "$line" |  awk '{print $3}' | sed 's/"//g')"

#      ksh/bash/zsh specific (not posix), but more powerful/versatile than the
#      'case' method that follows. I tried to make this work using just eval,
#      but couldn't, for some reason I cannot explain.

#      typeset "$varname""=""$varval"
      eval "$varname"="$varval"
    fi
  done

if [ "$MinX" != "ERROR" ]; then
  echo "Area (linuxwacom) [xf86-input-wacom]:    value"
  echo "x1   (MinX)       [TopX]            :    ""$MinX" # top left X
  echo "y1   (MinY)       [TopY]            :    ""$MinY" # top left Y
  echo "x2   (MaxX)       [BottomX]         :    ""$MaxX" # bottom right X
  echo "y2   (MaxY)       [BottomY]         :    ""$MaxY" # bottom right Y
  echo
  echo "To apply this calibration, run:"
  echo "xsetwacom set '""$devicename""' Area ""$MinX"" ""$MinY"" ""$MaxX"" ""$MaxY"
fi

Also, why the hell don't more people use kornshell? and Why the fuck does FreeBSD still use tcsh for its root shell in 2019?

Also, you can make that calibration apply automatically by piping that script to 'tail -n 1' and doing an eval.

Who?

Not sure.
(grumbles something about kids these days with their blinking LEDs and their 'youtubers' who play video games for money)
Oh yeah, Bill Buckner died like a week ago. That's somebody I know the name of.
If you or your family are from the Boston area/are long-time red sox fans you or they have probably heard of him. He is commonly blamed for the Red Sox losing the world series in 1986. At that point they hadn't won a world series in 68 years.
I only somewhat care because of my family, but I grew up hearing about his role in the the world series game as gospel.
Apparently, he was a really awesome guy to meet in real life, though. Before the dementia, anyway.
…And this is the most I've talked about baseball since 2012. Sorry.

This post has been edited by dragontamer8740: Jun 4 2019, 09:45

MSI really loves PS/2. Even in 2019, their motherboards have one.

I was avoiding motherboards that seemed to increase in price only for useless LED and Wifi features, but there ended up being a catch: no USB-C compatibility (making the compatibility of my computer case with it useless (IMG:[invalid] style_emoticons/default/sad.gif) ).

Also, why the hell don't more people use kornshell? and Why the fuck does FreeBSD still use tcsh for its root shell in 2019?

If one considers tcsh a C shell then zsh can be thought as a korn shell. ksh's good, and zsh would be a good remake of it had it fallen prey of "make every single feature anyone on github can think of".

MSI really loves PS/2. Even in 2019, their motherboards have one.

They are legacy and won't be going away, it's also lower latency then USB.

If one considers tcsh a C shell then zsh can be thought as a korn shell. ksh's good, and zsh would be a good remake of it had it fallen prey of "make every single feature anyone on github can think of".

Isn't zsh still markedly less performant than ksh93, though?
I mean, ksh93 uses a custom I/O library (sfio) because stdio apparently wasn't good enough.

Also, 100% agreed on the zsh bloat. That's the primary reason I don't use it. That being said, I do use emacs…

And typeset -Z (for automatic zero padding) is one of my favorite things about ksh93 in practice. That and how fast it is compared with bash, and its "discipline functions" (basically getters and setters).

But yet, AT&T laid David Korn and Glenn Fowler off. At least ksh93's still free software. Just wish FreeBSD would throw tcsh into the fires of hell where it belongs, instead of making it the root shell.

This post has been edited by dragontamer8740: Jun 5 2019, 09:22

MSI really loves PS/2. Even in 2019, their motherboards have one.

And that's a damn good thing, too. One of the few things that are still good in consumer technology.
You'd better not be dissing AT keyboard protocol. It's perfectly suited for its task.
Pardon the clutter, I'm mid-move


sorry for double post.

This post has been edited by dragontamer8740: Jun 5 2019, 09:50

And that's a damn good thing, too. One of the few things that are still good in consumer technology.
You'd better not be dissing AT keyboard protocol. It's perfectly suited for its task.

Oh, snap. That is actual IBM 90s keyboard. I don't know if PS/2 keyboards are still being manufactured nowadays. Last time I ever used a PS/2 keyboard was around 2007, because the Asus motherboard has the port for it and it's a lot cheaper than the USB version.

The Asus TUF FX505DY (renamed to FX505A in Malaysia for whatever reason) employs a Ryzen 5 3550h CPU which according to its specs its memory controller supports max. memory speeds up to 2400MHz. However Asus decideed to throw in a 2666Mhz memory module in the laptop. Delving into the Bios found no option to overclock the memory module, so I guess the reason for Asus' decision is just to up the laptop's price a little.

Modern BIOS can be configured with a mouse, funny.

They are legacy and won't be going away.

A rare case where "legacy" doesn't equate to "dead".

Linux is so much fragmented it'll probably never be popular for people.

Linux is so much fragmented it'll probably never be popular for people.

Good.

Hopefully simply booting off a live CD and overwriting /etc/sudoers with a working sudoers file will work rather than (GUI prompt to mount a disk still works though so that's something I guess, however I wanted to see if I could update /etc/sudoers to get a rid of that).

Linux is so much fragmented it'll probably never be popular for people.

Technically speaking though Linux is extremely popular as it is just the kernel, what you are talking about are the 6,000,000 OS's for it, each has it's own minor issue.

i.e Most of the used android builds are very likely stuck on 3.4.x because none free binary blobs and I would rather not "upgrade" when my phone currently works fine (after a bit of additional "patch" applying on top of having to reformat the phone in order to apply custom ROM updates because storage when attempting access via recovery is apparently using different credentials however booting up normally works fine and OTA updates are unable to be applied but the support page for it is dead which is extremely helpful).

Also nearly every distro is likely to have at least a few packages that are extremely old and have not seen an update in years.

This post has been edited by u_21099: Jun 10 2019, 13:36

Good.

The things that come with popularity unfortunately already exist, though
Stuff like systemd that's supposed to "simplify" a distro but just makes things worse, for instance.
And GNOME 3

Oh, snap. That is actual IBM 90s keyboard. I don't know if PS/2 keyboards are still being manufactured nowadays.

They are. IBM's old mechanical models are still being made, even, just under a different name. Apparently the cases are made of ABS instead of PVC now, too. In your choice of with- or without-windows-keys. There are also other color options; this is the white version.
[www.pckeyboard.com] https://www.pckeyboard.com/page/product/UNI0416

Last time I ever used a PS/2 keyboard was around 2007, because the Asus motherboard has the port for it and it's a lot cheaper than the USB version.

I got my IBM boards (I have 3) for:
1: free while volunteering at a fundraiser where people dump their shit and a school sells it. In very good shape. Made in 1993.
2: free from a friend who has a hobby writing programs for old computers/consoles. Dirty AF, but I cleaned and fixed it. Made in 1993.
3: $18 for a working terminal which came with a keyboard. Made in 1987.

I bought that gray shell from the company I linked above (Unicomp) since they're liquidating old stock and apparently had a bunch of industrial gray colored cases lying around brand new, from back when they were IBM branded and made with PVC. I paid around $35 for it and an LED overlay sticker since they're sold without them.

This post has been edited by dragontamer8740: Jun 10 2019, 16:14