Jump to content

drwatson

Member
  • Content Count

    44
  • Joined

  • Last visited

Everything posted by drwatson

  1. derp. Awesome. thank you so much a lot of new cool stuff. It was a bit hard finding the alfred since it was baked into the sourcecode zip this time FYI
  2. Hi Jarek, Thanks for the update. I noticed that the workflow no longer respects the order of the timezone list file, but orders them in order of time no matter what I do. Is this intentional ?
  3. https://www.timeanddate.com/time/gmt-utc-time.html Just pick a place in GMT time zone, like Reykjavík in Iceland ( https://www.timeanddate.com/worldclock/iceland/reykjavik ) https://en.wikipedia.org/wiki/UTC±00:00#As_standard_time_(all_year_round)
  4. [~]$ npm install --global alfred-polyglot > alfred-polyglot@1.4.0 postinstall /usr/local/opt/nvm/current/lib/node_modules/alfred-polyglot > alfy-init + alfred-polyglot@1.4.0 added 238 packages from 86 contributors in 5.207s [drwatson@zoro](06:36:50)(5.646s) [~]$ trans !set default-language vietnamese fish: Unknown command: trans package.json doesn't even have a "bin" section so how could trans get installed ? The doc doesn't really explain how the workflow gets installed either. How does this thing work ?
  5. this seems like an unnecessary question. If I had to guess, it's because Jerek inherited the code from someone else. He's done a great job. I'd leave it at that.
  6. It looks like other workflows store data in the info.plist file. What if the data is stored there instead? THen you can rid of the timezone move command altogether? Also, if you still want to keep it for backwards compatability, you could use the info.plist to store a reference to the location of the file instead.
  7. I changed to latest version but ended up rolling back to 2.0 because neither seemed to work. I don't think preferences folder has ever worked tbh which is why I was using the move command to begin with. Thanks for prioritizing ! -d
  8. There have been two possible factors that determine the location of timezone.txt: The preference folder as determined in Advanced | Set preferences folder The storage location as defined within the timezone script itself (timezone move command). Right now, it doesn't appear to honor either
  9. Jarek: I noticed that the workflow doesn't save the timezone.txt file to the correct location anymore. Any chance you could look into that ?
  10. Looks like 2.12 is the latest: https://github.com/jaroslawhartman/TimeZones-Alfred/releases/tag/v2.12
  11. I don't get what you're trying to do or what the problem is. Are you trying to get it to highlight the right one ? My version ( 2.0 ) will only show the matching results. Maybe you could upgrade ?
  12. my first thought is that it's way easier to edit the actual file than removing and adding them back. You can find out where the file is using timezone move. And you should make sure that the city that you added is present in that file. If it's not, then that's the problem
  13. Jarek, thanks for the updates. The about page still mentions it being 1.8 even though the changelog has 1.9 in it. Also, I think it's good to reference the website and maybe github location too.
  14. convert 1 usd to sek ✔ convert $1 sek ✔ convert $1 to sek ✖ Why doesn't the last one work? bug?
  15. I don't know the answer but I would take this chance to get comfortable with 24. Am/pm is just an annoyance when you get used to it. There's a reason many countries use 24 including the US military
  16. I ended up modifying the script myself. In timezone_list.sh < city_time=$(date -u -j -f %s $city_epochtime +"%T") #Create readable time expression --- > city_time=$(date -u -j -f %s $city_epochtime +"%l:%M %p") #Create readable time expression 157c157 Note the %l:%M %p was changed to simply %H:%M
  17. Any way to configure this so that I can see times in 24-hour clock?
×
×
  • Create New...