News for hackers. Stuff that matters.
Re:Making Remote Work Work by rjzzleep on Thursday February 13, 2014 @11:11AM (#7232096)
since i spend a lot of time in the console i have a few very simple aliases, for the following and some other time zones i use frequently.

    cst='TZ=CST6CDT date'
    est='TZ=EST date'
    berlin='TZ=''Europe/Berlin'' date'
then i can just convert times and needed.

    berlin -d '4:00pm EST'
Re:Making Remote Work Work by sneak on Thursday February 13, 2014 @01:38PM (#7233183)
SO THAT'S HOW YOU SET ENVIRONMENT VARIABLES IN ALIASES! THANK YOU!

(I'd been making the slight-environment-change aliases into bash functions as a workaround. You just helped me so much.)

Re:Making Remote Work Work by mscman on Thursday February 13, 2014 @02:34PM (#7233677)
This works in a normal bash/zsh prompt as well if you want to set a variable only for that single command. It's why a lot of times you'll see build instructions like:

# CC=gcc make

After the command runs, CC will go back to whatever it was set to before (or unset if it wasn't set). Very handy for some operations.

Re:Making Remote Work Work by emillon on Friday February 14, 2014 @03:57AM (#7237594)
I think that you can also use env(1) for this.

    berlin='env TZ=Europe/Berlin date'
Re:Making Remote Work Work by mojuba on Thursday February 13, 2014 @01:02PM (#7232918)
Excellent idea. This, and I wonder when will I finally see a simple, practical web site that does just that: helps to schedule inter-timezone conf calls with minimal clicks. One such web site was once posted here on HN but it was unfinished at the time (didn't allow to add custom locations) and probably doesn't exist anymore.
Re:Making Remote Work Work by shrikant on Thursday February 13, 2014 @02:22PM (#7233574)
I've used http://www.worldtimebuddy.com/ for this in the past and it's worked really well.
Re:Making Remote Work Work by mojuba on Thursday February 13, 2014 @02:57PM (#7233839)
Kind of like http://timesched.pocoo.org suggested in another comment here, but this one is more cluttered. Anyway, nice tool, thanks!
Re:Making Remote Work Work by mbesto on Thursday February 13, 2014 @01:19PM (#7233030)
Re:Making Remote Work Work by mojuba on Thursday February 13, 2014 @01:44PM (#7233235)
Thanks, but:

http://www.thetimezoneconverter.com/ - allows only two locations. What about scheduling a conf call across NY, Dublin, Berlin and Moscow? What is the best time for all 4 locations?

http://everytimezone.com/ - awesome interface, but doesn't allow any customizations, e.g. pick just the locations I need. This was on HN, I remember I made some suggestions which the guy never implemented.

http://time.is/ - shows only current time, or otherwise compares times only in two locations. Useless, just like thousands of other similar web sites.

Re:Making Remote Work Work by ehPReth on Thursday February 13, 2014 @02:22PM (#7233582)
Try this one by Armin Ronacher: http://timesched.pocoo.org/ - it's open source as well
Re:Making Remote Work Work by mojuba on Thursday February 13, 2014 @02:55PM (#7233823)
Nice one, thanks!
Re:Making Remote Work Work by herge on Thursday February 13, 2014 @01:18PM (#7233020)
I use http://everytimezone.com/ all the time.
Re:Making Remote Work Work by mojuba on Thursday February 13, 2014 @01:47PM (#7233260)
Yes, nice, but incomplete (see my other reply in this thread)
Re:Making Remote Work Work by technomancy on Thursday February 13, 2014 @06:29PM (#7235481)
I have my chat client set to timestamp in UTC; helps a lot.