- Jun 20, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
- Jun 19, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
- Jun 15, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
- Jun 11, 2014
-
-
Eric S. Raymond authored
-
- Jun 04, 2014
-
-
Eric S. Raymond authored
-
- Jun 01, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
- May 31, 2014
-
-
Eric S. Raymond authored
-
Unit 193 authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
W. Trevor King authored
This fixes some issues with 672240ab (Use syslog facility when irkerd is backgtrounded and no -l was given, 2014-05-31): * Shift the 'os' import to keep the stdlib imports alphabetized. * Move the syslog docs from a stand-alone paragraph into the -d/--log-level section. * Add some text to the -d/--log-level docs explaining the distinction between the -l/--log-file traffic logs and the -d/--log-level program-tracing logs. * StreamHandler logs to standard error (not standard output) by default [1]. Change "stndard output" to "standard error". * Add articles to background and foreground ("the background"). * Fix a "packground" -> "background" typo. * Explain our background-detection logic, and point out some of the assumptions made by the current implementation. I still think that it's better to have an explicit --syslog setting, and to leave it to packagers/users to descide explicitly if they prefer logging to syslog or stderr. But whatever the syslog-switching logic is, it should be clearly documented so folks don't have to read the source to understand it. [1]: https://docs.python.org/3/library/logging.handlers.html#logging.StreamHandler Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
- May 30, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
Eric S. Raymond authored
From an idea by tasn.
-
Antoine Beaupré authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Antoine Beaupré authored
i got tired of rereading the source code every time i wanted to use irk, isn't that silly? Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Beat Bolli authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Beat Bolli authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Beat Bolli authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Beat Bolli authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
Beat Bolli authored
Signed-off-by:
Eric S. Raymond <esr@thyrsus.com>
-
- Apr 18, 2014
-
-
Eric S. Raymond authored
-
- Mar 15, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
- Mar 12, 2014
-
-
W. Trevor King authored
Respect the 'socket' argument passed in by the caller. Fixes a typo introducted in a82724f9 (irkerd: Initial SSL/TLS implementation, 2014-03-06).
-
W. Trevor King authored
This fixes some problems with -i/--immediate parsing in ccd311c5 (irkerd: Transition from getopt to argparse, 2014-03-06). > + parser.add_argument( > + '-i', '--immediate', action='store_const', const=True, > + help='disconnect after sending each message') This does not match the old syntax where -i took two arguments (an IRC URL and a message). > - if immediate: > + if args.immediate: > irker.irc.add_event_handler("quit", lambda _c, _e: sys.exit(0)) > irker.handle('{"to":"%s","privmsg":"%s"}' % (immediate, arguments[0]), quit_after=True) > irker.irc.spin() immediate should be args.immediate, and arguments[0] needs to be added as a new (optional) positional argument. This patch fixes both issues.
-
Eric S. Raymond authored
-
- Mar 11, 2014
-
-
Eric S. Raymond authored
-
Eric S. Raymond authored
-
W. Trevor King authored
And use them (when present) as the USER username [1] and server PASS [2] respectively. The previous implementation gave no way to set PASS, which will vary on a per-target-server level. There's unlikely to be much need to set per-server usernames, except collision avoidance (e.g. network X already has an 'irker' user). I changed the existing IRCServerConnection.connect argument from 'ircname' to 'realname' to match the USER specs and our IRCServerConnection.user implementation. The 'realname' and 'username' arguments are currently unset, but you could add command line options to set irker-wide defaults, and use the kwargs chain to pass them down to the connect method. The fallback logic is: * Prefer the setting listed in the URL (although you'd need to add a parser to extract 'realname'). If that's empty or missing, fall back to * The irker-wide default passed down the kwargs chain. If that's empty or missing, fall back to * Local defaults ('irker' and 'irker relaying client'). I also tweaked the servername and port extraction in Target.__init__(), because they are already parsed out of the netloc (along with the username and password) by urlparse(). [1]: https://tools.ietf.org/html/rfc2812#section-3.1.3 [2]: https://tools.ietf.org/html/rfc2812#section-3.1.1
-