Updates from ThomasPowell Toggle Comment Threads | Keyboard Shortcuts

  • ThomasPowell 7:35 am on September 23, 2022 Permalink | Reply
    Tags: , meetings   

    20 Meeting Personalities 

    This list was put together from experiences with experiences with conference calls in 2011. It’s interesting to see, depending on my role on a team or in an organization, how many of the “personalities” below I’ve adopted. It’s also interesting to see how the “all remote” meetings post-pandemic have made some of “personalities” or commentary obsolete.

    • Off-mute chewer – Chews on (lunch?) audibly into the microphone.
    • Absent-minded mute button user – Starts responding with the mute button on for about a minute or more before realizing that no one is hearing the response.
    • Mute button blamer – Wasn’t paying attention. 
      Had to have name called several times.
      Blames mute button for not having a clue what’s going on.
      See also: How the Mute Button on Your Phone Actually Works
    • Clock Watcher – Spends more time checking watch that actually participating in meeting.
    • Filibusterer – Single handedly talks the meeting into oblivion. (Not to be confused with the derailer or rambler.)
    • Derailer – Somehow manages to bring up tangential topics that get everyone completely off topic for the next 15 minutes.
    • Rambler – Responds to any question with a barely intelligible introspection on the topic.
      Responds to follow-up questions for clarification grow at an exponential rate.
    • Hedger – Treats every remote possibility as likely and stays non-committal unless you accept the exceptions noted.
    • Side Conversation Starter – Either completely oblivious or too rude to care that another meeting is going on.
    • Overhead speaker – Not an actual attendee or person, but an object which causes an echo in speakerphones and disrupts the meeting until it becomes silent again.
    • Tattle-tale – At the first of not getting his or her way, threatens to go tell a more powerful person to whom the tattler is connected.
    • Foot-propper – The meeting is a lounge to this person:  Feet are propped up on the table and behaves generally too relaxed to actually be engaged in the meeting.
    • Multitasker – Furiously typing on the keyboard, but obviously not to take notes on the meeting. (Don’t bother asking this person questions unless you want to rehash the entire meeting.)
    • Referee – “Sees the merits of both sides” of an intense debate.
      Tries to make everybody play nice, regardless of their agendas.
    • Idea killer – Always has a negative scenario for any proposal.
      Never has an idea himself.
    • Yes man – Would say no pants Friday at the office was a good idea, provided the right person proposed it.
    • Interrupter – Jumps in mid-details and often freaks out about half the story or asks questions whose answers were already on their way.
    • Belittler – Often pulls rank or “experience” to shut other people off.
    • Saboteur – Is either annoyed at the assignment or annoyed at not getting the project lead, but plays nice during the meeting, silently plotting the slow death of the project. (Can also accomplish goals as an inciter.)
    • Inciter – May jump communication chains to create the illusion of one person hiding information from another.
  • ThomasPowell 1:56 pm on September 17, 2022 Permalink | Reply
    Tags: , imessage   

    Annoy your friends with iMessage and AppleScript 

    Ever want to send a text message but you don’t have the energy to send it one word at a time? If you have macOS signed into iMessage, you can use AppleScript to automate sending one word at a time! (Warning: Doing this more than a few times will probably get you blocked by the people you know!)

    (The below script is available at send_message.applescript)

    #!/usr/bin/env osascript
    #  CREDIT TO https://chrispennington.blog/blog/send-imessage-with-applescript/ for how to send iMessages via AppleScript
    on run parameters
      # the number here is the number of seconds
      set theDelay to 3
      # Change this to the phone number of the iMessage contact to use
      set phoneNumber to "+1 (555) 555-1212"
      tell application "Messages"
        set targetBuddy to phoneNumber
        set targetService to id of 1st account whose service type = iMessage
        repeat with arg from 1 to length of parameters
          set textMessage to ( item arg of parameters )
          set theBuddy to participant targetBuddy of account id targetService
          send textMessage to theBuddy
          delay theDelay
        end repeat
      end tell
      log "Message sent"
    end run

    The repeat with arg from 1 to length of parameters and end repeat is essentially AppleScript’s for loop, with arg being the loop variable and 1 to length of parameters being the closed range on 1 to the end of the parameters list. Changing the value of theDelay can separate the messages by different number of seconds (currently 3 seconds)

    You need to chmod +x the script and update the phone number and then you can run it like:

    ./send_message.applescript This is a message to send

    Results of running AppleScript

This is a [Read 1:49PM] message to send with one blue bubble on each line
    Results of sending iMessages via AppleScript to myself

    You can group words with quotes as well

    ./send_message.applescript "This is a" "message to send"

    AppleScript with quoted arguments.

"This is a" "message to send"

    Remember: Use / abuse of this script may get you blocked. This script is purely for educational purposes.

  • ThomasPowell 6:29 pm on September 9, 2022 Permalink | Reply
    Tags: , vim-plug,   

    Windows vim-plug error 

    When trying to port my macOS .vimrc to Windows and attempting to set up vim-plug, I ran into the following error

    Windows vim-plug error

The system cannot find the path specified.
Error detected while processing function <SNR>2_install[1]..<SNR>2_update_impl[62]..<SNR>2_git_version_requirement[2]..<SNR>2_system[30]..function <SNR>2_install[1]..<SNR>2_update_impl[62]..<SNR>2_git_version_requirement[2]..<SNR>2_system:
line   24:
E282: Cannot read from "C:/Users/twill/AppData/Local/Temp/VF3575F.tmp"
Press ENTER or type command to continue

    In searching, I found this issue on vim-plug’s GitHub repo: Error when I try to install plugins on Windows. The comment on setting shellslash made me look in my own .vimrc:

    set shell=/bin/bash

    Commenting that out with the following resolved the issue. (No admin

    " set shell=/bin/bash

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc
%d bloggers like this: