 | Emacs Matrix Client Dev | 17 Members |
| Development Alerts for matrix-client.el | 5 Servers |
| Emacs Matrix Client Dev | 17 Members |
| Development Alerts for matrix-client.el | 5 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 Oct 2018 | ||
 Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed 12 commits to ordered-buffer: https://github.com/jgkamat/matrix-client-el/commit/81bb5c55daa5b3cecdc0108927dfda88223de906 alphapapa: WIP: ordered-buffer code for inserting into room buffers alphapapa: Add: Store timeline event IDs in hash table for deduplication alphapapa: Fix/Tidy: Fix small bug and move code around alphapapa: Tidy: Comments and docstrings alphapapa: Tidy: Requirement alphapapa: Tidy: Remove obsoleted code alphapapa: Update: (--update-date-headers) For ordered-buffer changes alphapapa: Add: timestamp-header-delta variable alphapapa: Change/Fix: Process timeline events in order This may not be the best way to do this. It is simple, and should be fast enough, but there might be a cleaner way to handle this. alphapapa: Change: Improve insertion of headers for old messages Probably need to refactor a bit, or add some functionality to ordered-buffer to cleanly handle inserting from both ends. But this isn't bad. The only issue now is that, when inserting old messages, a new timestamp header is always inserted, even if the timestamp difference is within the delta setting, which is not necessarily a bad thing, because it makes it easier to see where the newly fetched messages are. It gets a little complicated because, when inserting old messages, if we insert from the top (which makes sense), we need to insert the messages in a different order so the prefix-fn looks at the right event to determine whether to insert a new header. alphapapa: Add: Update date headers at midnight alphapapa: Fix: Don't return empty strings for room displaynames | 01:40:12 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #55: Ordered buffer [open] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 01:40:13 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #27: Early WIP: "next-gen" client [open] - https://github.com/jgkamat/matrix-client-el/pull/27 | 02:02:51 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed to client-ng: Fix: Remove newlines between HTML tags in mx-reply messages - https://github.com/jgkamat/matrix-client-el/commit/52d90d0508ab13d96b4a99ee4b4ba6fcba342a8a | 02:03:06 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed 12 commits to ordered-buffer: https://github.com/jgkamat/matrix-client-el/commit/cdbf9e1941fdbc628424774e341b200f16163e08 alphapapa: WIP: ordered-buffer code for inserting into room buffers alphapapa: Add: Store timeline event IDs in hash table for deduplication alphapapa: Fix/Tidy: Fix small bug and move code around alphapapa: Tidy: Comments and docstrings alphapapa: Tidy: Requirement alphapapa: Tidy: Remove obsoleted code alphapapa: Update: (--update-date-headers) For ordered-buffer changes alphapapa: Add: timestamp-header-delta variable alphapapa: Change/Fix: Process timeline events in order This may not be the best way to do this. It is simple, and should be fast enough, but there might be a cleaner way to handle this. alphapapa: Change: Improve insertion of headers for old messages Probably need to refactor a bit, or add some functionality to ordered-buffer to cleanly handle inserting from both ends. But this isn't bad. The only issue now is that, when inserting old messages, a new timestamp header is always inserted, even if the timestamp difference is within the delta setting, which is not necessarily a bad thing, because it makes it easier to see where the newly fetched messages are. It gets a little complicated because, when inserting old messages, if we insert from the top (which makes sense), we need to insert the messages in a different order so the prefix-fn looks at the right event to determine whether to insert a new header. alphapapa: Add: Update date headers at midnight alphapapa: Fix: Don't return empty strings for room displaynames | 02:03:16 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #55: Ordered buffer [open] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 02:03:17 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed to ordered-buffer: Add: Fancy quoting - https://github.com/jgkamat/matrix-client-el/commit/3159197ac578b47146c171ed4d7e179e5b5a1387 | 02:36:11 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #55: Ordered buffer [open] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 02:36:12 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #55: Ordered buffer [open] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 02:42:08 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed to ordered-buffer: Add: Fancy quoting - https://github.com/jgkamat/matrix-client-el/commit/28839f0333d59ba8b7e52bd908823d3a17f86426 | 02:42:08 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed to ordered-buffer: Change: Destructure mx-reply messages with esxml Since some clients include newlines between and before and after the HTML tags, we need a more flexible solution, and esxml is that, thankfully. - https://github.com/jgkamat/matrix-client-el/commit/77f7b2b775a5cf1c5b6abf8a7015d15ca036aee8 | 17:07:54 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #55: Ordered buffer [open] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 17:07:55 |
| 17 Oct 2018 | ||
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] jgkamat deleted jay/emacs-26-optional | 14:22:39 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed to legacy-client: Fix: (matrix-client.el) Require s - https://github.com/jgkamat/matrix-client-el/commit/5751eefc121eda0b69b3875db7b0913d520f5269 | 14:23:21 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] jgkamat pushed to ordered-buffer: Attempt to fix malformed replys See https://github.com/vector-im/riot-ios/issues/2080 Not fully tested yet, so feel free to revert. - https://github.com/jgkamat/matrix-client-el/commit/0e3bef5859a8850f85f492b4bf914be8937a0bcd | 14:26:41 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] jgkamat synchronize pull request #55: Ordered buffer [open] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 14:26:42 |
| 20 Oct 2018 | ||
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] stardiviner opened issue #57: Stop bind matrix-client request on normal request functions [open] - https://github.com/jgkamat/matrix-client-el/issues/57 | 05:56:29 |
| 21 Oct 2018 | ||
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] stardiviner opened issue #58: Can matrix-client support Org link like supported link type `irc:` in Org? [open] - https://github.com/jgkamat/matrix-client-el/issues/58 | 06:05:11 |
| 22 Oct 2018 | ||
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] stardiviner closed issue #57: Stop bind matrix-client request on normal request functions [closed] - https://github.com/jgkamat/matrix-client-el/issues/57 | 00:37:59 |
| 23 Oct 2018 | ||
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] stardiviner edited issue #57: Stop bind matrix-client request on normal request functions [closed] - https://github.com/jgkamat/matrix-client-el/issues/57 | 02:47:03 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa closed pull request #55: Ordered buffer [closed] to alphapapa - https://github.com/jgkamat/matrix-client-el/pull/55 | 02:47:59 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] web-flow pushed 16 commits to client-ng: https://github.com/jgkamat/matrix-client-el/commit/35c8bc904cf7ba256903c27ceb542643edf81a9c alphapapa: WIP: ordered-buffer code for inserting into room buffers alphapapa: Add: Store timeline event IDs in hash table for deduplication alphapapa: Fix/Tidy: Fix small bug and move code around alphapapa: Tidy: Comments and docstrings alphapapa: Tidy: Requirement alphapapa: Tidy: Remove obsoleted code alphapapa: Update: (--update-date-headers) For ordered-buffer changes alphapapa: Add: timestamp-header-delta variable alphapapa: Change/Fix: Process timeline events in order This may not be the best way to do this. It is simple, and should be fast enough, but there might be a cleaner way to handle this. alphapapa: Change: Improve insertion of headers for old messages Probably need to refactor a bit, or add some functionality to ordered-buffer to cleanly handle inserting from both ends. But this isn't bad. The only issue now is that, when inserting old messages, a new timestamp header is always inserted, even if the timestamp difference is within the delta setting, which is not necessarily a bad thing, because it makes it easier to see where the newly fetched messages are. It gets a little complicated because, when inserting old messages, if we insert from the top (which makes sense), we need to insert the messages in a different order so the prefix-fn looks at the right event to determine whether to insert a new header. alphapapa: Add: Update date headers at midnight alphapapa: Fix: Don't return empty strings for room displaynames alphapapa: Add: Fancy quoting alphapapa: Change: Destructure mx-reply messages with esxml Since some clients include newlines between and before and after the HTML tags, we need a more flexible solution, and esxml is that, thankfully. jgkamat: Attempt to fix malformed replys See https://github.com/vector-im/riot-ios/issues/2080 Not fully tested yet, so feel free to revert. alphapapa: Merge pull request #55 from jgkamat/ordered-buffer Ordered buffer | 02:48:00 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa closed pull request #24: Early WIP: API r0.3.0 [closed] - https://github.com/jgkamat/matrix-client-el/pull/24 | 02:48:59 |
| 26 Oct 2018 | ||
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa pushed to master: Fix: matrix--next-property-change and message insertion - https://github.com/jgkamat/matrix-client-el/commit/b795e6d77ec705481adb04e2cf1d55868348bac2 | 04:25:20 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] web-flow pushed 79 commits to master: https://github.com/jgkamat/matrix-client-el/commit/35c8bc904cf7ba256903c27ceb542643edf81a9c alphapapa: Fix: Don't send notifications on initial sync alphapapa: Fix: Attempt workaround of potential timer/timeouts issue alphapapa: Fix: Don't move point when inserting messages alphapapa: Tidy: Remove unneeded logging alphapapa: Fix: Ignore errors from dead buffers on disconnect Happens occasionally. alphapapa: Fix: (matrix-warn) Add string to args after calling matrix-log alphapapa: Fix: Call matrix-warn instead of display-warning directly Except *in* matrix-warn, of course. alphapapa: Add: Kill buffers on disconnect alphapapa: Add/Fix: Persist transaction ID and initialize to random number NOTE: According to <https://matrix.org/docs/spec/client_server/r0.3.0.html#id183>, the transaction ID should be scoped to the access token, so we should preserve it with the token. However, if the client crashes and fails to save the TID, and then reuses it in the future...what happens? The server seems to accept messages with already-used TIDs. Maybe it has some kind of heuristic... I found these: <https://github.com/matrix-org/synapse/issues/1481> and <https://github.com/matrix-org/synapse/pull/1624>. alphapapa: Fix: Header insertion position for new day's messages A minor bug introduced by the change to matrix--next-property-change, which I didn't catch until now. alphapapa: Comment: Add note alphapapa: Add/Change: Derived mode and -connect command This simplifies a few things and puts room buffers in matrix-client-ng-mode rather than fundamental-mode, making it easier to sort them, etc (it's also how the non-ng branch works). alphapapa: Fix: Add matrix- prefix to url-with-retrieve-async This caused inexplicable problems because it diverged from another copy of the function in my config. alphapapa: Fix: (matrix-url-with-retrieve-async) Error when connection completely fails It seems that the callback can be called with `nil' when the connection fails before getting any headers, like: url-http-end-of-document-sentinel(#<process matrix.org<5>> "connection broken by remote peer\n"), in which case `url-http-end-of-headers' is nil, so we need to call the error fn. Would like to structure this more cleanly. alphapapa: Add: (--human-format-date) "Yesterday" alphapapa: Fix: Set initial-sync-p in -connect alphapapa: Add: Process state messages on connect This restores the room buffer naming behavior of the legacy branch. alphapapa: Change: Update format$ macro from elexandria alphapapa: Change/Fix: Rename matrix-warn to matrix-error and fix warning alphapapa: Comment: Add a MAYBE alphapapa: Notes: Add bug alphapapa: Add: Customizable server hostname For users whose homeserver hostname is not the same as the server part of their user ID. See <https://github.com/jgkamat/matrix-client-el/pull/27#issuecomment-408091419>. alphapapa: Fix: (matrix-url-with-retrieve-async) Add URL to error callback alphapapa: Add: Display sending messages immediately, with button to resend WIP WIP WIP: Progress Now, when sending a message, it is immediately displayed in the buffer, with normal faces and metadata, along with a "[pending]" button. When the server responds with the event ID, it's added to the message, and the button is removed. Then when the event is received back from the server in the next /sync, the event is deleted from the buffer and replaced with the event from the server, which has the server's origin timestamp. Still need to test resending messages that don't get sent, but now that the matrix.org homeserver is a bit more reliable, with the improvements they've recently made, this doesn't happen as often... alphapapa: Reorganize faces and room code into separate files alphapapa: Port: Typing notifications alphapapa: Port: Room topic Well, isn't this simple! alphapapa: Port: Room avatars alphapapa: Port: Convenience commands in room buffers For RET, TAB, reply/quote, etc. alphapapa: Fix: "Left" messages alphapapa: Fix: Insertion position In preparation for loading earlier messages... alphapapa: Port: Fetch older messages alphapapa: Fix: Move room-related macros into room file alphapapa: Fix: matrix-session :server instance-initform alphapapa: Fix: UTF-8 encode JSON data Fixes #50. See also <https://github.com/magit/ghub/issues/12>, <https://github.com/dakrone/es-mode/issues/62>, and <https://github.com/magit/ghub/issues/35>. I can't explain why this is necessary. We encode the message to UTF-8 already, and there shouldn't be anything multi-byte about the JSON syntax. And if there were, shouldn't that have been the case already, not just when sending multi-byte content encoded in the JSON? e.g. see especially <https://github.com/magit/ghub/issues/35#issuecomment-348832926>. Jonas's comment on commit <https://github.com/magit/ghub/commit/45cd8c8341f2065aad6ed72200c10842f8087498> almost seems to explain it, but I still don't understand why it would happen here, because we were already encoding the messages to UTF-8 before giving them to url.el. Anyway, this seems to fix it. And this is another thing that I think should be fixed in the url-with-retrieve-async macro. We should just encode EVERYTHING to UTF-8 and tell the server that we're using it. If that were already the case in url.el, none of these bugs would have happened, and it would have saved so many man-hours in all these projects. alphapapa: Notes: Add todo alphapapa: Revert "Fix: UTF-8 encode JSON data" This reverts commit d3b0233ffb555a8d01bdafcfbe24d6c96b1dab1d. The change in the first hunk was a mistake: the data variable, which becomes url-request-data, should remain an alist, not a string. The other changes are necessary, but the Synapse server seems to be rejecting UTF-8-encoded JSON, so the /login POST request is rejected with "HTTP 400 Bad Request" (and no further explanation). Reverting this should at least make the client-ng branch usable with plain-ASCII messages and /login working again. alphapapa: Fix: UTF-8-encode POST data This attempts a simpler (and apparently more correct) fix for the fix attempted in 8d10d9828474afb8cb7e30398c27c805d83ac693 and reverted in 8d10d9828474afb8cb7e30398c27c805d83ac693. Sending non-ASCII room messages appears to work, and logging in (POST to /login) appears to work. Fixes #50 (for real, this time, I hope). alphapapa: Add: (-image-url-prefixes) i.redditmedia.com alphapapa: Fix: Trim messages before quoting alphapapa: Fix: Update date headers when message arrives on new day alphapapa: Fix: Special commands must start with / Without this fix, it's actually impossible to send a message starting with the word "who". Oops. alphapapa: Fix: /who: Don't insert "[pending]" alphapapa: Add: /html command Sends HTML messages. alphapapa: Tidy: Remove unused code alphapapa: Add: Message body faces This allows better customization of message faces. The main message-body face inherits from default, and the own-message-body face inherits from it. P.S. helm-grep + wgrep is a great combination. alphapapa: Add: Simple room command macro This makes it easy to implement simple commands, like a /listening command that sends an emote like "Listening to: ...". alphapapa: Change: Send room command methods the command argument Rather than sending the whole input and requiring each command to remove "/command " from the input. alphapapa: Change: Improve room command macro and use it for commands Later we can add /command completion with e.g. pcomplete. alphapapa: Fix: (matrix-client-ng-send-input) Split command on spaces alphapapa: Change: (matrix-client-ng-def-room-command) Automatically propertize alphapapa: Change: (matrix-client-ng-defevent) Improve debug declaration Now the body is correctly instrumented, so event handlers can be stepped through with edebug. I'm not sure if the other parts can be instrumented, but it took long enough to figure this out, so I'll try that another time. alphapapa: Add: Render messages quoted with mx-reply specially alphapapa: Add: /upload command for images Can easily be extended to other filetypes later. Squashed commit of the following: commit 96dc95cdc8102f4f28dccfea522bd7b365b493fe Author: Adam Porter <adam@alphapapa.net> Date: Wed Oct 10 10:11:07 2018 -0500 Change: Don't advise url-http-create-request Use cl-letf to override it where needed. commit d7591f9c1496e23bc2072d113b401d8c20caba59 Author: Adam Porter <adam@alphapapa.net> Date: Sun Sep 2 00:13:35 2018 -0500 Tidy: upload callback commit 0de8f93309d10764e5a1bbc2662253435267e140 Author: Adam Porter <adam@alphapapa.net> Date: Sat Sep 1 23:57:27 2018 -0500 Comment: Add comment about fixing the fix commit b02190f5b748d4c59b6d38ca95c7e6c799db6434 Author: Adam Porter <adam@alphapapa.net> Date: Sun Aug 26 23:52:45 2018 -0500 Add: /upload command commit 48da8059c61b8f63e2f9ad7b0498d1449b6de988 Author: Adam Porter <adam@alphapapa.net> Date: Sun Aug 26 23:52:20 2018 -0500 Add/Change: Download HTTP paths, then upload Also convert function to method commit e1f5eb5754253895cf413ad3e52e3cf23e62846d Author: Adam Porter <adam@alphapapa.net> Date: Sun Aug 26 23:50:36 2018 -0500 Fix: Get image type from file header if no extension commit a1b4c3faa38c426a7804b33b444cd2bb7e461c62 Author: Adam Porter <adam@alphapapa.net> Date: Thu Aug 23 00:33:09 2018 -0500 WIP: Image upload Plus everyone's favorite, cowsay! alphapapa: Change: Use request instead of url.el It's impossible to upload files with url.el unless url-http-create-request is overridden with a fixed version, and that must be done with function advice (which applies to everything in Emacs), because doing it with cl-letf doesn't work (who knows why--it works fine for other things). Obviously we don't want to override that function globally, even though it works fine now, because when url.el changes in the future, that might break something. And it's not a good idea, anyway. So let's switch back to request.el. Frankly, I don't even remember why I switched to my url-with-retrieve-async function. There is this pesky bug at https://github.com/tkf/emacs-request/issues/92, but that only applies to synchronous requests, which we aren't using. alphapapa: Revert: "Change: Use request instead of url.el" This reverts commit 21c8af26d899f29885060b3ef52f644a86531a41. request.el has a bug which causes our sync requests to get duplicated. The last message I received in a room arrived 21 times because of 21 simultaneous sync requests. I don't know what is causing it, and request.el is very difficult to debug. So we will have to go back to using url.el for everything we can use it for. For a few things that don't work with url.el, like uploading files, we'll have to use request.el. What a mess. And how disappointing that there is no HTTP library for Emacs that doesn't have these kinds of virtually-impossible-to-debug bugs. See https://github.com/jgkamat/matrix-client-el/pull/27#issuecomment-428689369 alphapapa: Add/Fix: Use request.el for uploading See https://github.com/jgkamat/matrix-client-el/pull/27#issuecomment-428689369. alphapapa: Fix: Disable shr filling except for blockquotes Was broken in 3e80e3eb5553973a5e2975cc85841ca9c2262712. alphapapa: Change: (matrix-client-ng-update) Use matrix-client-ng-timeline Also allows us to easily replay events into a buffer. alphapapa: Change: Improve buffer naming, especially on initial sync In large rooms (e.g. #emacs with > 600 users), initial sync is now faster because 1) the room name is only computed twice (when the room buffer is created, and when the initial sync is completed) rather than for every user "join" event (and the initial computation is very fast, because there are one or no users known to be in the room when the buffer is first created), and 2) we short-circuit the computations when possible, avoiding looking up displaynames for users unnecessarily. alphapapa: Add/Change: Use <backtab> to go to earlier events alphapapa: Fix: Use correct show-images variable alphapapa: Fix: Remove newlines between HTML tags in mx-reply messages alphapapa: WIP: ordered-buffer code for inserting into room buffers alphapapa: Add: Store timeline event IDs in hash table for deduplication alphapapa: Fix/Tidy: Fix small bug and move code around alphapapa: Tidy: Comments and docstrings alphapapa: Tidy: Requirement alphapapa: Tidy: Remove obsoleted code alphapapa: Update: (--update-date-headers) For ordered-buffer changes alphapapa: Add: timestamp-header-delta variable alphapapa: Change/Fix: Process timeline events in order This may not be the best way to do this. It is simple, and should be fast enough, but there might be a cleaner way to handle this. alphapapa: Change: Improve insertion of headers for old messages Probably need to refactor a bit, or add some functionality to ordered-buffer to cleanly handle inserting from both ends. But this isn't bad. The only issue now is that, when inserting old messages, a new timestamp header is always inserted, even if the timestamp difference is within the delta setting, which is not necessarily a bad thing, because it makes it easier to see where the newly fetched messages are. It gets a little complicated because, when inserting old messages, if we insert from the top (which makes sense), we need to insert the messages in a different order so the prefix-fn looks at the right event to determine whether to insert a new header. alphapapa: Add: Update date headers at midnight alphapapa: Fix: Don't return empty strings for room displaynames alphapapa: Add: Fancy quoting alphapapa: Change: Destructure mx-reply messages with esxml Since some clients include newlines between and before and after the HTML tags, we need a more flexible solution, and esxml is that, thankfully. jgkamat: Attempt to fix malformed replys See https://github.com/vector-im/riot-ios/issues/2080 Not fully tested yet, so feel free to revert. alphapapa: Merge pull request #55 from jgkamat/ordered-buffer Ordered buffer | 04:29:55 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa synchronize pull request #27: Early WIP: "next-gen" client [open] - https://github.com/jgkamat/matrix-client-el/pull/27 | 04:30:49 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa closed issue #56: Receiving message causes Emacs to hang [closed] - https://github.com/jgkamat/matrix-client-el/issues/56 | 07:30:05 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa closed issue #25: Access tokens and passwords may be revealed by curl [closed] to alphapapa - https://github.com/jgkamat/matrix-client-el/issues/25 | 07:32:54 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa closed issue #22: Cache token [closed] to alphapapa - https://github.com/jgkamat/matrix-client-el/issues/22 | 07:33:37 |
| Github [@jgkamat:matrix.org] | [jgkamat/matrix-client-el] alphapapa closed issue #21: EIEIO constructor improvements [closed] - https://github.com/jgkamat/matrix-client-el/issues/21 | 07:34:43 |