Jump to content

jeffsui

Member
  • Posts

    93
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by jeffsui

  1. Github Repo: https://github.com/jeeftor/EmojiTaco


    I'm the author and its my work.

    Forum Thread: https://www.alfredforum.com/topic/9499-emoji-taco-downloads-emoji-from-unicodeorg/

    Dependencies: (embedded in the code - although I'd love it if there is a way in gallery eventually to have just a requirements.txt and let Alfred create a virtual environment)

    Picture (Maybe the 2nd is better)

    image.png.a5846054f6c035e4609c91845db1d7cc.png

     

    image.png.5faadb8e6eb3ca451adade2b5a2519c5.png

  2. I've just upgraded to OSX Mojave and a brand new MacBook (at work).  I have a workflow that enables and disables various proxy settings via some bash commands.  The old scrip that was called in the workflow is: 

     

    sudo networksetup -setwebproxystate  Wi-Fi on
    sudo networksetup -setsecurewebproxystate  Wi-Fi on
    sudo networksetup -setautoproxystate Wi-Fi On
    sudo networksetup -setautoproxyurl Wi-Fi {query}
    
    sudo networksetup -setsecurewebproxy Wi-Fi $proxy_server 80
    sudo networksetup -setwebproxy Wi-Fi $proxy_server 80

     

    Suddenly inside Mojave I'm now getting this error:

     

    Quote

    [2019-02-06 12:04:08][ERROR: action.script] sudo: no tty present and no askpass program specified

     

    I've switched my code over to this which now prompts me for a password every time (which is fine with Touch ID) 

    do shell script "sudo networksetup -setwebproxystate  Wi-Fi on
    sudo networksetup -setsecurewebproxystate  Wi-Fi on
    sudo networksetup -setautoproxystate Wi-Fi On
    sudo networksetup -setautoproxyurl Wi-Fi {query}
    sudo networksetup -setsecurewebproxy Wi-Fi $proxy_server 80
    sudo networksetup -setwebproxy Wi-Fi $proxy_server 80
    " with administrator privileges

    But where I'm confused is as to whether this is a new behavior in Mojave I enabled password-less sudo in the past.  If I remember on my old Mac when I ran this workflow the first time I got a password prompt from keychain that asked if I wanted to always allow.

     

    Any ideas the correct way to setup this up so it will continue to do so on Mojave land.  I'd rather not have to do finger stuff every time I make a change.

     

    Thanks.

     

     

  3. I've whipped up a little workflow which will allow you to send TTS (Text to Speech) phrases to various Sonos devices (assuming you have more than one).  I primarily use it to send messages to my kids room telling him to clean up.

     

    Directions are available at the GitHub Repo.

     

    The plugin works by using lame and say to generate an .mp3 file (called tts.mp3) which is stored somewhere on a sonos accessible path (such as //imac/share).  Once the file is generated the plugin utilizes SoCo (a python lib) to tell sonos to play the mp3 file.  

     

    You can get the latest release at : 

    https://github.com/jeeftor/AlfredSonosTTS/releases

     

    I've only tested it with my setup Play1,Play3,Amp and it works on all these devices.

  4. I'm trying to figure out the best way to determine whether the text in either title or subtitle is going to get truncated aka if its too long there will be some ...'s put in.  Is there a set character width for both of the fields or is it font based or something?

×
×
  • Create New...