brndnmtthws / conky

Light-weight system monitor for X, Wayland (sort of), and other things, too
https://conky.cc
GNU General Public License v3.0
7.27k stars 620 forks source link

IRC shows up as ${irc} #670

Closed RossComputerGuy closed 1 year ago

RossComputerGuy commented 6 years ago

I'm trying to make conky connect to the Arch Linux IRC and I have this snippet in my /etc/conky/conky.conf file. But it shows up as ${irc}, what am I doing wrong and how do I fix it?

${color grey}Arch Linux IRC:
 $color${irc chat.freenode.net:6667 #archlinux}
dbriba commented 6 years ago

${irc.....} is not a command conky. try with ${curl............} curl : url (interval_in_minutes) Download data from URI using Curl at the specified interval. The interval may be a positive floating point value (0 is allowed), otherwise defaults to 15 minutes. Most useful when used in conjunction with Lua and the Lua API. This object is threaded, and once a thread is created it can't be explicitly destroyed. One thread will run for each URI specified. You can use any protocol that Curl supports.

RossComputerGuy commented 6 years ago

There is a command called irc: image

dbriba commented 6 years ago

Excuse me, I did not see this command in my setting. Have you the 6667 port open in your firewall ?

RossComputerGuy commented 6 years ago

Port 6667 is open, I compiled with IRC support now and now the IRC command doesn't show up as ${IRC} but it doesn't display anything at all.

dbriba commented 6 years ago

May be the name of the channel is not #archlinux but other name.

RossComputerGuy commented 6 years ago

No, it is. https://wiki.archlinux.org/index.php/IRC_channel

dbriba commented 6 years ago

In your link I see that:

In order to reduce spam #archlinux and #archlinux-offtopic have the channel mode set to +r and +q $~a. This means you have to be identified via NickServ to be able to join these channels and send messages, respectively. If you are not registered and identified, you will be forwarded to #archlinux-unregistered.

May be you must be identified to see the channel

RossComputerGuy commented 6 years ago

Well, how do I do that?

dbriba commented 6 years ago

Well, how do I do that?

I don't know, the irc 's conky command have no arguments for that. Maybe using a script, but I do not have enough knowledge to write it

lasers commented 6 years ago

I don't have access to conky right now to play with ${irc}. You can try joining a random channel (e.g. ###conky) along with your IRC client there to see if it's working okay. I'm not sure about registration thing, but you may have better luck with ii and some other conky variable like {cat} or {exec tail}. http://manpages.ubuntu.com/manpages/latest/en/man1/ii.1.html The better solution probably might be to just run irssi or weechat inside screen or tmux so you would be able to do more than just reading messages.

dbriba commented 6 years ago

The channel is set to +r See here : https://freenode.net/kb/answer/channelmodes

r : Prevents users who are not identified to services from joining the channel.

RossComputerGuy commented 6 years ago

I know +r is set but I just need a way to log in.--Sent from Yandex.Mail for mobile19.10.2018, 22:26, "dbriba" notifications@github.com:The channel is set to +r See here : https://freenode.net/kb/answer/channelmodes

r : Prevents users who are not identified to services from joining the channel.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

dbriba commented 6 years ago

I see that in your link :

k (password)
To enter the channel, you must specify the password on your /join command. Keep in mind that modes locked with ChanServ's MLOCK command can be seen by anyone recreating the channel; this includes keys. Also keep in mind that users being on the channel when +k is set will see the key as well.

try this : ${irc chat.freenode.net:6667 #archlinux +k your_password}

RossComputerGuy commented 6 years ago

It didn’t work--Sent from Yandex.Mail for mobile19.10.2018, 22:40, "dbriba" notifications@github.com:I see that in your link :

k (password) To enter the channel, you must specify the password on your /join command. Keep in mind that modes locked with ChanServ's MLOCK command can be seen by anyone recreating the channel; this includes keys. Also keep in mind that users being on the channel when +k is set will see the key as well.

try this : ${irc chat.freenode.net:6667 #archlinux +k your_password}

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

dbriba commented 6 years ago

Maybe your_password must are between parenthesis ()

lasers commented 6 years ago

If you looked at IRCSERVERPASS variable in src/irc.cc code, you will see that it's not being used nor verified anywhere so it's probably not possible to identify / join registered channels. Just a heads up.

No idea what will happen to this issue. You might have better luck (fifo) piping out irssi/weechat/others to conky instead.

Llewellynvdm commented 5 years ago

Has anyone been able to get this to work? I would really like to use this.

There is a crazy work around via Telegram-IRSSI bridge, and then via telegram-messenger-cli stream to Conky. Close to madness... but it works. Just seems like there should be an easier way.

RossComputerGuy commented 5 years ago

@Llewellynvdm I've been wondering about the same thing since I opened this issue.

brndnmtthws commented 5 years ago

The irc support is not enabled unless you build with BUILD_IRC=ON. It depends on a library called libircclient, and I'm not sure of the status of it at the moment.

RossComputerGuy commented 5 years ago

I had built it with irc enabled.04.01.2019, 12:19, "Brenden Matthews" notifications@github.com:The irc support is not enabled unless you build with BUILD_IRC=ON. It depends on a library called libircclient, and I'm not sure of the status of it at the moment.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

brndnmtthws commented 5 years ago

Let me try testing it to see if it works. If not, I'll probably remove the code unless someone wants to shepherd it.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment, or this issue will be closed in 30 days.

github-actions[bot] commented 1 year ago

This issue was closed because it has been stalled for 30 days with no activity.