Timeline
May 20, 2013:
- 1:29 PM code-review edited by
- Note that github emails don't show up as being to:barnowl-dev@mit.edu (diff)
- 1:24 PM Contributing edited by
- Mention github pull requests (diff)
- 1:23 PM code-review edited by
- Note that github pull requests are just as good as email to … (diff)
- 12:55 PM Changeset [3bd3ee8] by
- Merge 60ae73623d2d5d0de7ff98c39b77da51ec7b30a9 into 731e921fabe20fb70a9578e3237ec87804111276
- 12:21 PM Changeset [60ae736]release-1.10 by
- Fix a leak. Also add the CALLER_OWN annotation to the owl_zephyr_dotfile method.
- 12:07 PM Changeset [25a5e3b] by
- Merge 731e921fabe20fb70a9578e3237ec87804111276 into 53151d4da160cdeb2e541e3353934732bd6d9dc5
- 12:05 PM Changeset [731e921]release-1.10 by
- Make check for non-existant channel more correct Currently, this doesn't change anything; all channels start with '#'. However, when pull #107 (Improve irc-msg support for multiple connections) lands we want to accept, e.g., '0' as a valid user name. So we should actually be checking if the value is defined, rather than if it's not falsy. Perhaps we should also exclude empty strings, spaces, etc., as valid user names/channels.
May 19, 2013:
- 7:45 PM Changeset [2e9b9ad] by
- Merge 53151d4da160cdeb2e541e3353934732bd6d9dc5 into c2866ecce166474ab92c7f75d53d7de0d6d884a0
- 7:35 PM Changeset [53151d4]release-1.10 by
- Use "our" instead of "my" for zephyrStartup hook All our other hooks seem to be defined using "our", and I don't seem to be able to use the zephyrStartup hook without this change. http://perldoc.perl.org/functions/our.html does claim the scoping should be the same (though it also seems to suggest that only "our" gives a package variable instead of something only in the current lexical scope...).
May 13, 2013:
- 8:12 PM Changeset [67009f92] by
- Merge c2866ecce166474ab92c7f75d53d7de0d6d884a0 into 0625919d1e483ec9ba11021e1281e05f9d2b877a
- 8:11 PM Changeset [c2866ec]release-1.10 by
- Split irc messages into chunks From Zephyr: barnowl / irc-cutoff / kchen 2013-05-09 16:38 (Everyone Left Wheel Thru) This might be an IRC limitation. RFC 1459 says: "IRC messages are always lines of characters terminated with a CR-LF (Carriage Return - Line Feed) pair, and these messages shall not exceed 512 characters in length, counting all characters including the trailing CR-LF. Thus, there are 510 characters maximum allowed for the command and its parameters. There is no provision for continuation message lines. See section 7 for more details about current implementations." (I didn't read the rest of the RFC to know how many other bytes are involved in sending a message.) I chose 450 to be the default cut-off semi-arbitrarily; freenode seems to allow up to about 463 characters (to channel #agda, with username jgross).
May 6, 2013:
- 10:17 PM Ticket #249 (Investigate support for bidi (Arabic/Hebrew)) created by
- I don’t really know what’s supposed to happen here, but I think merely …
Apr 24, 2013:
- 4:29 PM Ticket #248 (Make `:sub -mumble` less confused) created by
- […] Zephyr treats subscription triples starting with - as punts.
- 4:27 PM Ticket #247 (Make zpunt (optionally) write to .zephyr.subs) created by
- Zephyr has a punt mechanism, which uses the - prefix. :zpunt …
Note: See TracTimeline
for information about the timeline view.
