Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

HexChat fails to write channel (%c) to log's filename when using auto-connect/auto-join #438

Closed
Nisto opened this Issue · 7 comments

3 participants

@Nisto

I use this file name format for my log files: %s/%Y-%m-%d %c.log
But it seems like it joins the channel too fast when auto- connecting and joining, and as a result, it doesn't store a value for %c, so unless I join a channel manually (using e.g. "/j #channel"), I get something like "server/2013-03-04 .log".

@TingPing
Owner

have you tried without the space?

@Nisto

Just tried without the space, the channel name is still missing.

@Arnavion
Owner
  1. What is your OS and Hexchat version (including whether it's 32- or 64-bit)?
  2. Is this reproducible only with one network, or does it happen to all of them?
@Nisto
  1. Windows XP
  2. All networks

And actually, it turns out the problem is somewhere else. When I connect, I use the "global" server address for the network - so for example if I use irc.freequest.net to connect to FreeQuest, and I end up at bier.fr.eu.freequest.net, it would create a network log for irc.freequest.net, and a log for any channel that I have on auto-join for FreeQuest inside a "irc.freequest.net" folder, but all those logs will be empty, while the "real" logs will be inside a "bier.fr.eu.freequest.net" folder. Could you prevent this somehow?

@Arnavion
Owner
  1. Is it Windows XP 32- or 64-bit?
  2. Which version of Hexchat are you using?
  3. Is the Hexchat version 32- or 64-bit?
@Nisto

lol, don't know how I missed the other questions..
1. 32-bit
2. 2.9.4
3. 32-bit (x86)

@Arnavion
Owner

Starting with 2.9.5, we've dropped XP support. This issue does not seem to be present on any other platforms.

@Arnavion Arnavion closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.