-
-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic mailsync script readded/improved. Should actually work on *most* cron setups. #607
Comments
@LukeSmithxyz
eval `grep -h -- \
"^\(export \)\?\(MBSYNCRC (...) is failing because the grep -h -- "^$(printf '\t')* *\(export \)\?\(MBSYNCRC (...) |
Okay. In aa4fb99 I now have it check for systemd and run the DBUS line. I also changed the regex to match whitespace at the beginning of the variable export lines. |
This line doesn't work for me. Have to substitute "$USER" with "root" or manually export $DISPLAY. |
Your Xorg is running as root? What distro/WM are you using? |
Yes. I'm using Arch + dwm. I followed this link and set |
Okay. Since I assume that only one graphical user will be logged in at once, I suppose I could just remove the user specification and avoid this issue. |
@LukeSmithxyz looks had some flaw in the notification script... displays="$(pgrep -a Xorg | grep -wo "[0-9]*:[0-9]\+")" e.g:
|
if difficult to parse |
The from line is working fine for me. Could you show me the erroneous results? I've push a commit that will fix your first issue. |
i did not get that first |
|
@LukeSmithxyz perhaps i mis-read your comment, but looks |
@Maugrift thx (#640) and fyi, now dup |
In f589cd4 I have added back the
mailsync
script with two main improvements:You can set mailsync as a cronjob now and it should actually work and display "New Mail" notifications without anything too funky. There have also been added options like
mw -t 40
to set up an automatic sync as a cronjob every 40 minutes. This means that it actually should work and give notifications on many, I hope, most Linux machines (and I think it should still work with Mac).Several things I am still doubtful about, so your help would be nice. I don't use soystemd obviously and things often work differently. I seem to remember systemd requiring a line like
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus
to function with the cronjob, but this line breaks the functionality on runit. Systemd-users, please tell me what your experience is.The line is currently commented out.It will now run only on systemd machines.The text was updated successfully, but these errors were encountered: