Menu
▾
▴
emacs-jabber-general — Discussion about jabber.el
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(24) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(66) |
Feb
(15) |
Mar
(15) |
Apr
(23) |
May
(16) |
Jun
(29) |
Jul
|
Aug
(5) |
Sep
(40) |
Oct
(10) |
Nov
(2) |
Dec
(25) |
| 2006 |
Jan
(43) |
Feb
(7) |
Mar
(11) |
Apr
(15) |
May
(7) |
Jun
(13) |
Jul
(13) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
(9) |
Dec
(12) |
| 2007 |
Jan
(5) |
Feb
(9) |
Mar
(27) |
Apr
(20) |
May
(20) |
Jun
(4) |
Jul
(54) |
Aug
(67) |
Sep
(27) |
Oct
(9) |
Nov
(18) |
Dec
(11) |
| 2008 |
Jan
(32) |
Feb
(29) |
Mar
(15) |
Apr
(6) |
May
(11) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(17) |
Oct
(19) |
Nov
(8) |
Dec
(13) |
| 2009 |
Jan
(8) |
Feb
(3) |
Mar
(11) |
Apr
(18) |
May
(4) |
Jun
(2) |
Jul
(7) |
Aug
(12) |
Sep
(20) |
Oct
(1) |
Nov
(2) |
Dec
(9) |
| 2010 |
Jan
(1) |
Feb
(7) |
Mar
(1) |
Apr
|
May
(13) |
Jun
|
Jul
(5) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(6) |
| 2011 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(19) |
Sep
(1) |
Oct
(10) |
Nov
(2) |
Dec
(6) |
| 2012 |
Jan
(1) |
Feb
(3) |
Mar
(23) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
(7) |
Oct
(3) |
Nov
(5) |
Dec
|
| 2013 |
Jan
(4) |
Feb
(6) |
Mar
(1) |
Apr
(20) |
May
(9) |
Jun
(1) |
Jul
(8) |
Aug
(14) |
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(1) |
| 2014 |
Jan
(1) |
Feb
(16) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(11) |
Jul
(7) |
Aug
(13) |
Sep
(4) |
Oct
|
Nov
(2) |
Dec
(2) |
| 2015 |
Jan
(2) |
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
(1) |
Jul
(9) |
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(5) |
Dec
(1) |
| 2016 |
Jan
(6) |
Feb
(1) |
Mar
(5) |
Apr
|
May
(7) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(4) |
| 2017 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(10) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
|
From: Adam S. <as...@ko...> - 2019-04-14 02:05:12
|
If a jabber:x:oob message is received with a URL that looks like an
image, the image is fetched and displayed.
Also, the URL is only shown if displaying the image fails. I'm not
quite sure about moving jabber-char-print-url to jabber-body-printers,
but I don't think it makes sense to show it if displaying the image
succeeds.
But, if there is a URL, that can't be displayed, maybe the body should
be shown? Hm.
In the examples I've seen, the message looks like:
<message from="vi...@ko.../pidgin" to="as...@ko..." type="chat" id="purple4fb6fb94">
<archived by="koldfront.dk" xmlns="urn:xmpp:mam:tmp" id="1555194815542627"/>
<stanza-id by="koldfront.dk" xmlns="urn:xmpp:sid:0" id="1555194815542627"/>
<body>https://koldfront.dk/xmpp/virgil/8ze1C6CGD1hvWQhbl4cYNzDYrAb19wjbFX7IkXZ3/x-face.png</body>
<x xmlns="jabber:x:oob">
<url>https://koldfront.dk/xmpp/virgil/8ze1C6CGD1hvWQhbl4cYNzDYrAb19wjbFX7IkXZ3/x-face.png</url>
</x>
</message>
so the body is redundant when the jabber:x:oob url is handled.
---
jabber-chat.el | 45 +++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 43 insertions(+), 2 deletions(-)
diff --git a/jabber-chat.el b/jabber-chat.el
index e2fd607..3cfaf00 100644
--- a/jabber-chat.el
+++ b/jabber-chat.el
@@ -177,7 +177,6 @@ These fields are available:
(defvar jabber-chat-printers '(jabber-chat-print-subject
jabber-chat-print-body
- jabber-chat-print-url
jabber-chat-goto-address)
"List of functions that may be able to print part of a message.
Each function receives these arguments:
@@ -187,7 +186,9 @@ WHO :local or :foreign, for sent or received stanza, respectively
MODE :insert or :printp. For :insert, insert text at point.
For :printp, return non-nil if function would insert text.")
-(defvar jabber-body-printers '(jabber-chat-normal-body)
+(defvar jabber-body-printers '(jabber-chat-print-image
+ jabber-chat-print-url
+ jabber-chat-normal-body)
"List of functions that may be able to print a body for a message.
Each function receives these arguments:
@@ -630,6 +631,46 @@ If DONT-PRINT-NICK-P is true, don't include nickname."
(format "%s <%s>" desc url))))))
foundp))
+(defun jabber-chat-download-image (url)
+ "Download image from URL and return as image"
+ (when (string-match "^https?://.*\\.\\(png\\|jpg\\|jpeg\\|gif\\)$" url)
+ (let ((image-buffer (url-retrieve-synchronously url)))
+ (when image-buffer
+ (with-current-buffer image-buffer
+ (goto-char (point-min))
+ (re-search-forward "^$" nil 'move)
+ (forward-char)
+ (delete-region (point-min) (point))
+ (let ((image (create-image (buffer-string) nil t :max-width 800 :max-height 400)))
+ ; I can't figure out how to use max-width and max-height,
+ ; as width and height are set, and overrides them:
+ (let ((width (image-property image :width))
+ (height (image-property image :height)))
+ (setf (image-property image :width) nil)
+ (setf (image-property image width) nil)
+ (setf (image-property image :height) nil)
+ (setf (image-property image height) nil))
+ image))))))
+
+(defun jabber-chat-print-image (xml-data who mode)
+ "Print images provided in jabber:x:oob namespace."
+ (let ((foundp nil))
+ (dolist (x (jabber-xml-node-children xml-data))
+ (when (and (listp x) (eq (jabber-xml-node-name x) 'x)
+ (string= (jabber-xml-get-attribute x 'xmlns) "jabber:x:oob"))
+ (setq foundp t)
+
+ (when (eql mode :insert)
+ (let ((url (car (jabber-xml-node-children
+ (car (jabber-xml-get-children x 'url)))))
+ (desc (car (jabber-xml-node-children
+ (car (jabber-xml-get-children x 'desc))))))
+ (let ((image (jabber-chat-download-image url)))
+ (when image
+ (insert-image image url)
+ (insert "\n")))))))
+ foundp))
+
(defun jabber-chat-goto-address (xml-data who mode)
"Call `goto-address' on the newly written text."
(when (eq mode :insert)
--
2.20.1
--
"Everything needs to change. Adam Sjøgren
And it has to start today." as...@ko...
|
|
From: Adam S. <as...@ko...> - 2019-04-14 02:02:08
|
Adam Sjøgren writes:
> And I don't think it implements the image view part?
I have implemented this part. It can probably be done in a nicer way,
but this is what I got working: [patch in next email].
Best regards,
Adam
--
"Everything needs to change. Adam Sjøgren
And it has to start today." as...@ko...
|
|
From: Martin J. <ja...@ja...> - 2019-04-13 19:00:15
|
Hi, On Sat, Apr 13, 2019 at 12:03 PM Mandar Mitra <man...@gm...> wrote: > > I've been using emacs-jabber very happily for 1:1 chats on Google > Hangouts, but recently, jabber-roster has started displaying strings > of the form > > * 22r...@pu... Online > * 0ek...@pu... Away > MessagingA53984b2d - Away (), priority 0 > messaging-lcsw_hangouts_43734ED5 - Away (), priority 0 > * 0ze...@pu... Away > > in addition to regular names. > I have been experiencing the same issue in the past few weeks. I assume it has something to do with Google deleting Google Plus related stuff. On Sat, Apr 13, 2019 at 5:26 PM Mandar Mitra <man...@gm...> wrote: > > Following up on my own email: I dug around a bit more, and can think > of a workaround, but am not sure how to implement it. > > The documentation says the %n specifier in jabber-roster-line-format > corresponds to "Nickname of contact, or JID if no > nickname". Apparently, the problematic lines provide JIDs only, but > no nicknames. > > I can use jabber-vcard-get to get the vcard for a contact that's > showing up as a JID only. Thanks for the tip, this vcard then always actually displayed the contact's proper name and so I finally knew who they were. I then manually edited the contact (with jabber-roster-edit-action-at-point, or just pressing "e") and changed the name to the proper one. I usually had to do it twice for the change to take effect but I was able to fix the five or six contacts that were un-decipherable strings before I read your email. So thanks a lot, I hope you'll also be able to fix the problem too. Martin > I should be able to use bits of > jabber-vcard-display to extract the "Full name", which is what I'd > like to see displayed in the roster. > > But I don't know how to put all the pieces together. Can someone > please help? > > Thanks, > Mandar. > |
|
From: Mandar M. <man...@gm...> - 2019-04-13 15:26:26
|
Following up on my own email: I dug around a bit more, and can think of a workaround, but am not sure how to implement it. The documentation says the %n specifier in jabber-roster-line-format corresponds to "Nickname of contact, or JID if no nickname". Apparently, the problematic lines provide JIDs only, but no nicknames. I can use jabber-vcard-get to get the vcard for a contact that's showing up as a JID only. I should be able to use bits of jabber-vcard-display to extract the "Full name", which is what I'd like to see displayed in the roster. But I don't know how to put all the pieces together. Can someone please help? Thanks, Mandar. |
|
From: Mandar M. <man...@gm...> - 2019-04-13 10:03:27
|
I've been using emacs-jabber very happily for 1:1 chats on Google Hangouts, but recently, jabber-roster has started displaying strings of the form
* 22r...@pu... Online
* 0ek...@pu... Away
MessagingA53984b2d - Away (), priority 0
messaging-lcsw_hangouts_43734ED5 - Away (), priority 0
* 0ze...@pu... Away
in addition to regular names.
I just upgraded to the latest MELPA package, but that did not fix the problem. Could any one please suggest what the cause might be?
Thanks,
Mandar.
|
|
From: Adam S. <as...@ko...> - 2019-03-30 09:08:15
|
Hi, Both Conversations and Gajim (with the Url Image preview-plugin) support sending images, by way of XEP-0363, displaying the image inlne in the chat. Has anyone implemented support for that in jabber.el? I found https://github.com/yuchangyuan/jabber-http-file-upload but it doesn't work for me, it just keeps prompting for files. And I don't think it implements the image view part? Best regards, Adam -- "Everything needs to change. Adam Sjøgren And it has to start today." as...@ko... |
|
From: Zeus P. <ze...@ib...> - 2018-07-20 14:49:29
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
greetings,
please advise where to look at ...
after connect to my (two) accounts, emacs starts to eat 20-50%
of one core on my netbook ...
fsm-debug is filled up with such rows:
- ---[ quotation start ]-------------------------------------------
Fri Jul 20 15:23:10 2018: Sent :stanza to jabber-connection in state :session-established
Fri Jul 20 15:23:10 2018: Sent :roster-update to jabber-connection in state :session-established
Fri Jul 20 15:23:10 2018: Sent :filter to jabber-connection in state :session-established
Fri Jul 20 15:23:10 2018: Sent :stanza to jabber-connection in state :session-established
Fri Jul 20 15:23:10 2018: Sent :roster-update to jabber-connection in state :session-established
Fri Jul 20 15:23:10 2018: Sent :filter to jabber-connection in state :session-established
- ---[ quotation end ]-------------------------------------------
OS: FreeBSD 11.1-RELEASE-p9 #0 amd64
emacs: emacs-25.3
jabber.el: 0.8.92
what could cause that?
- --
Zeus V. Panchenko jid:ze...@im...
IT Dpt., I.B.S. LLC GMT+2 (EET)
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQYIXL6FUmD7SUfqoOveOk+D/ejKgUCW1HypgAKCRCveOk+D/ej
KlCmAJ0bAmzZvpBbm7AusjQrfKV7oQ+/WQCcD3zjKHuwJm1jdm2uQRdzUDj6cCE=
=kZ8V
-----END PGP SIGNATURE-----
|
|
From: Adam S. <as...@ko...> - 2018-07-03 09:00:12
|
Thibault writes:
> The attached updated patch decouples the `jabber-history-enabled' and
> `jabber-history-mam' variables.
Sweet.
> Let me know if you encounter issues.
I will, thanks for the quick reply!
Best regards,
Adam
--
"It's part of our policy not to be taken seriously" Adam Sjøgren
as...@ko...
|
|
From: Thibault M. <thi...@gm...> - 2018-07-03 03:06:49
|
Hi, The attached updated patch decouples the `jabber-history-enabled' and `jabber-history-mam' variables. When they are both non-nil, the messages will be logged to files and the server (assuming MAM is enabled) but retrieved from the server. To use MAM only set `jabber-history-enabled' to nil and `jabber-history-mam' to a non-nil value. Let me know if you encounter issues. thibault Adam Sjøgren via Emacs-jabber-general writes: > There are some caveats with multiple messages being added as one, and > with timestamps, which I didn't notice in the beginning. > > However, the worst thing is that my chatlogs in > ~/.emacs.d/jabber-history/* has stopped being appended to! > > I would _really_ like both MAM-support and the chatlogs being written > to. > > Is that possible? > > I have, among other things, this: > > (setq jabber-history-enabled t > jabber-history-mam t > jabber-history-muc-enabled t > > > Best regards, > > Adam |
|
From: Adam S. <as...@ko...> - 2018-07-02 19:03:59
|
There are some caveats with multiple messages being added as one, and
with timestamps, which I didn't notice in the beginning.
However, the worst thing is that my chatlogs in
~/.emacs.d/jabber-history/* has stopped being appended to!
I would _really_ like both MAM-support and the chatlogs being written
to.
Is that possible?
I have, among other things, this:
(setq jabber-history-enabled t
jabber-history-mam t
jabber-history-muc-enabled t
Best regards,
Adam
--
"To call for hands of above Adam Sjøgren
To lean on as...@ko...
Wouldn't be good enough
For me-åååå"
|
|
From: Thibault M. <thi...@gm...> - 2017-09-21 03:00:51
|
Hi, Thanks for letting me know that it works with ejabberd, that's good news. Hopefully this can eventually get merged. thibault Adam Sjøgren writes: > Hi, > > > Thibault writes: > >> I only tested with my prosody server, so I expect more work will be >> needed to get this to work reliably. > > First: sorry for taking so long to repond to your kind reply. > > I have tested your MAM support patch again, and it works beautifully for > me now! > > The "only" thing I have changed since the last time, is that I upgraded > my server when Debian released stretch this summer, and thus got a new > version of ejabberd. > > I would recommend this patch be merged :-) > > > Best regards, > > Adam |
|
From: <as...@ko...> - 2017-09-18 20:10:50
|
Hi,
Thibault writes:
> I only tested with my prosody server, so I expect more work will be
> needed to get this to work reliably.
First: sorry for taking so long to repond to your kind reply.
I have tested your MAM support patch again, and it works beautifully for
me now!
The "only" thing I have changed since the last time, is that I upgraded
my server when Debian released stretch this summer, and thus got a new
version of ejabberd.
I would recommend this patch be merged :-)
Best regards,
Adam
--
"It's the Disneyland-law Adam Sjøgren
So far out it makes anarchy a bore" as...@ko...
|
|
From: <as...@ko...> - 2017-07-19 14:51:35
|
Hi, Is anyone working on OMEMO-support for jabber.el? I have been using OTR with jabber.el for quite a while, and it works well, but OMEMO sounds even better: »Finally I can send encrypted messages to someone who is currently offline, uses multiple clients and simultaneously receive a copy of that message on all of my devices.« ⌘ https://conversations.im/omemo/ Best regards, Adam -- "most of the Flash that Web users encounter each day Adam Sjøgren is bad Flash with no purpose beyond annoying people." as...@ko... |
|
From: Fernando B. <Fer...@F1...> - 2017-06-06 21:01:56
|
Hi everyone, I am looking for a command line or Emacs-based client that can handle the WebRTC protocol. Only audio and text would be absolutely necessary, video would not, as the target audience are blind users. I understand the focus on this list is on XMPP, but I am writing to find out if there would be interest in expanding the EmacsJabber code to include compatibility with WebRTC. Alternatively, any suggestions of other projects or developers which might be interested in the WebRTC protocol in the non-GUI context would be very welcome. Our ultimate objective is to have a client that would be used by blind persons through Emacs and Emacspeak, on very low cost and low power devices, i.e. single board computers. Thanks for any guidance, Fernando |
|
From: Thibault M. <thi...@gm...> - 2017-02-12 19:26:48
|
Hi, thanks for trying this out. I only tested with my prosody server, so I expect more work will be needed to get this to work reliably. Thanks for offering to help debug this. First a quick word on the module. It spawns an XMPP request when (1) opening a new chat buffer (in order to get the recently archived messages) and when (2) calling `jabber-chat-display-more-backlog'. The XMPP request is asynchronous and the main function `jabber-mam-query' spins until the incoming message handler releases the lock. Hanging at (while (not jabber-mam-lock) (sit-for 1)) means that the lock does not get released by the message handler function. The first thing to do to debug this is to capture the XMPP request and the corresponding response message. The attached patch should print both in the *Messages* buffer. If you could apply this patch, and try again, we should be able to see the request and response. That would be the first step. The *Messages* buffer should contain something like this: * The prepared MAM request ,---- | MAM request: [<query xmlns='urn:xmpp:mam:0'><x xmlns='jabber:x:data' type='submit'><field var='FORM_TYPE' type='hidden'><value>urn:xmpp:mam:0</value></field><field var='id'><value>thi...@ex...</value></field><field var='with'><value>us...@ex...</value></field><field var='start'><value>2017-02-08T20:44:53Z</value></field></x><set xmlns='http://jabber.org/protocol/rsm'><max>10</max><before/></set></query>] `---- I often try to check the query by using the XMPP console in pidgin to see the server response. To do so, I wrap the content of the query within <iq> tags: <iq type='set' id='test'> <query xmlns= .... REMAINDER OF THE REQUEST TEXT ...</query> </iq> * The initial response to the request ,---- | MAM request succeeded `---- This simply means that the request succeeded, but this instantaneous server response does not return any message. If you get a failure message here, the request was not accepted (e.g. because the server does not support MAM or the namespace is wrong). But if you had a failure, then the lock should be immediately released, so it shouldn't hang. * Incoming messages Then the `jabber-handle-incoming-mam-message' function should process (and print for debugging) the incoming messages. Here is an example of message: ,---- | MAM incoming: (message ((to . thi...@ex.../20e82cb5-2d01-4a92-90ef-ffed886aee36)) (result ((id . 8b18e151-3199-4327-8a75-96e3bfd22c72) (xmlns . urn:xmpp:mam:0)) (forwarded ((xmlns . urn:xmpp:forward:0)) (delay ((stamp . 2017-01-27T05:04:06Z) (xmlns . urn:xmpp:delay))) (message ((type . chat) (to . thi...@ex...) (from . us...@ex.../015a473e-ed3a-4063-9d94-d42238631761) (id . purplea9f9333e) (xmlns . jabber:client)) (active ((xmlns . http://jabber.org/protocol/chatstates))) (body nil Message content open))))) | `---- * A final message The server should use result set management (https://xmpp.org/extensions/xep-0313.html#query-paging) to page through results. After N messages, it should return a message containing the last returned index so the caller can send a subsequent request and get the remaining messages. I suspect the issue is around here. The final message I get may look like this. ,---- | MAM incoming: (message ((to . thi...@ex.../20e82cb5-2d01-4a92-90ef-ffed886aee36)) (fin ((complete . true) (xmlns . urn:xmpp:mam:0)) (set ((xmlns . http://jabber.org/protocol/rsm)) (first nil 64e7f38c-5c47-484b-8cae-897f0691009e) (count nil 75) (last nil 03d1feb1-bfc1-4e00-bc24-f88aef05d1e1)))) `---- My code tries to read this final message and determine whether to send a following request or to stop and release the lock. Among other things, it uses the (complete . true) part of the response to make that decision. I suspect the code makes wrong assumptions about the structure of this message. If you could report with the *Messages* output, that would greatly help. I will also try to setup an ejabberd server, to see if I can reproduce the issues on my end. Thanks for your help, thibault |
|
From: <as...@ko...> - 2017-02-11 15:58:11
|
I wrote:
> I just tried it - connecting to an ejabberd server with MAM enabled, and
> looking at the backlog/history of messages in the Conversations Android
> app (which also supports MAM). Worked fine!
Uhm, I was too quick there. My test just showed that my ejabberd and
the Android app handles MAM...
After setting jabber-history-mam to t and starting jabber.el, if I press
RET on an entry in the roster, jabber.el seems to hang "forever".
If I toggle-debug-on-quit before, and press C-g three times, I get this
stack trace:
Debugger entered--Lisp error: (quit)
(while (not jabber-mam-lock) (sit-for 1))
(let ((mam-query (jabber-mam-make-query jid-me jid-with start-time end-time number-left jabber-mam-last-id))) (setq jabber-mam-lock nil) (jabber-send-iq jc nil "set" mam-query (function jabber-report-success) "MAM request" (function jabber-report-success) "MAM request") (while (not jabber-mam-lock) (sit-for 1)) (if (integerp number) (progn (setq number-left (- number (length jabber-mam-results))) (setq jabber-mam-done (or jabber-mam-done (<= number-left 0))))))
(while (not jabber-mam-done) (let ((mam-query (jabber-mam-make-query jid-me jid-with start-time end-time number-left jabber-mam-last-id))) (setq jabber-mam-lock nil) (jabber-send-iq jc nil "set" mam-query (function jabber-report-success) "MAM request" (function jabber-report-success) "MAM request") (while (not jabber-mam-lock) (sit-for 1)) (if (integerp number) (progn (setq number-left (- number (length jabber-mam-results))) (setq jabber-mam-done (or jabber-mam-done (<= number-left 0)))))))
(let ((number-left (if (integerp number) number nil))) (while (not jabber-mam-done) (let ((mam-query (jabber-mam-make-query jid-me jid-with start-time end-time number-left jabber-mam-last-id))) (setq jabber-mam-lock nil) (jabber-send-iq jc nil "set" mam-query (function jabber-report-success) "MAM request" (function jabber-report-success) "MAM request") (while (not jabber-mam-lock) (sit-for 1)) (if (integerp number) (progn (setq number-left (- number (length jabber-mam-results))) (setq jabber-mam-done (or jabber-mam-done (<= number-left 0))))))))
jabber-mam-query((:fsm jabber-connection :state :session-established :state-data (:send-function jabber-network-send :original-jid "as...@ko..." :username "asjo" :server "koldfront.dk" :resource "tullinup" :password [....]
Any ideas for what I should do to debug further?
Best regards,
Adam
--
"Do I really want to set this in Denmark?" Adam Sjøgren
as...@ko...
|
|
From: <as...@ko...> - 2017-02-11 15:42:25
|
Thibault writes: > I have fixed a couple of bugs: > - enforce limit on number of results > - prevent duplicate when incoming message is received (and was also > returned by MAM). > > I have also submitted a pull request on github > (https://github.com/legoscia/emacs-jabber/pull/21) to see if I can get > some interest there. > > I would appreciate feedback, hoping this can eventually get merged. I just tried it - connecting to an ejabberd server with MAM enabled, and looking at the backlog/history of messages in the Conversations Android app (which also supports MAM). Worked fine! Only problem is OTR, but that isn't something I was expecting MAM to handle :-) Thanks for contributing this enhancement to jabber.el, I hope it can be merged. Best regards, Adam -- "Do I really want to set this in Denmark?" Adam Sjøgren as...@ko... |
|
From: Thibault M. <thi...@gm...> - 2017-01-27 05:23:45
|
Damien Cassou writes: > I have the impression this project is dead. Nobody answers on the > mailing list. Thanks, I am giving it another try. I have fixed a couple of bugs: - enforce limit on number of results - prevent duplicate when incoming message is received (and was also returned by MAM). I have also submitted a pull request on github (https://github.com/legoscia/emacs-jabber/pull/21) to see if I can get some interest there. I would appreciate feedback, hoping this can eventually get merged. Thanks, thibault |
|
From: Damien C. <da...@ca...> - 2017-01-16 11:39:01
|
Adam Sjøgren <as...@ko...> writes: > Damien writes: >> I have the impression this project is dead. Nobody answers on the >> mailing list. > > Didn't Magnus Henoch just commit something a week ago? > > · https://sourceforge.net/p/emacs-jabber/mailman/message/35589469/ you are right. Though, the previous commit was from a year ago according to https://sourceforge.net/p/emacs-jabber/mailman/emacs-jabber-commit and the general mailing list have been very quiet too: https://sourceforge.net/p/emacs-jabber/mailman/emacs-jabber-general (even more if you remove my own messages). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill |
|
From: <as...@ko...> - 2017-01-16 10:18:01
|
Damien writes: > Thibault Marin <thi...@gm...> writes: >> I am not sure this is the right place for this, but I have implemented >> some support for server-side archive management (XEP-0313 Message >> Archive Management) in emacs-jabber. > I have the impression this project is dead. Nobody answers on the > mailing list. Didn't Magnus Henoch just commit something a week ago? · https://sourceforge.net/p/emacs-jabber/mailman/message/35589469/ I think it sounds great with MAM-support in jabber.el, I have just enabled MAM in my ejabberd to get Conversations (the app) to say "MAM available" :-) Best regards, Adam -- "Do I really want to set this in Denmark?" Adam Sjøgren as...@ko... |
|
From: Damien C. <da...@ca...> - 2017-01-16 08:45:50
|
Hi Thibault, Thibault Marin <thi...@gm...> writes: > I am not sure this is the right place for this, but I have implemented > some support for server-side archive management (XEP-0313 Message > Archive Management) in emacs-jabber. I have the impression this project is dead. Nobody answers on the mailing list. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill |
|
From: Thibault M. <thi...@gm...> - 2017-01-14 08:46:23
|
Hi all, I am not sure this is the right place for this, but I have implemented some support for server-side archive management (XEP-0313 Message Archive Management) in emacs-jabber. The attached patch (to apply on top of the master branch) contains the current version. Most of the code is in the new jabber-mam.el module, with additional modifications to the jabber-chat and jabber-history. The code branches off the file history extraction to create and send the MAM query instead of reading the archive from a file. MAM results are processed by a function added to `jabber-message-chain'. The code supports result paging according to XEP-0059 (Result Set Management). Does this look like something that could be merged? Any suggestion or review would be welcome. Thanks in advance. thibault P.S.: Is there any syncing with the github emacs-jabber repository (https://github.com/legoscia/emacs-jabber?). I am thinking it may be easier to get people to test this on github (I could submit a pull request there if preferred). |
|
From: Damien C. <da...@ca...> - 2016-12-15 10:31:00
|
Adam Sjøgren <as...@ko...> writes: > Do you have a link to that part of the documentation? http://emacs-jabber.sourceforge.net/manual-0.8.0/File-transfer.html#File-transfer -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill |
|
From: <as...@ko...> - 2016-12-15 10:04:44
|
Damien writes:
> here is an extract of jabber.el documentation:
>
> jabber.el has limited support for file transfer. The most important
> limit is that files sent and received are kept in buffers, so Emacs
> must be able to allocate enough memory for the entire file, and the
> file size must be smaller than the maximum buffer size.(1)
>
> jabber.el is able to exchange files with most Jabber clients (and
> also some MSN transports), but notably not with the official Google
> Talk client. The Google Talk client uses a different file transfer
> protocol which, at the time of this release, has not been published.
Nice!
I looked in the menu in Emacs, and I searched the net, but not
thoroughly enough.
Do you have a link to that part of the documentation?
Thanks!
Adam
--
"Do I really want to set this in Denmark?" Adam Sjøgren
as...@ko...
|
|
From: Damien C. <da...@ca...> - 2016-12-15 09:56:35
|
Hi Adam, Adam Sjøgren <as...@ko...> writes: > I think some XMPP-clients can transfer files. Is that something > jabber.el can/want to handle? here is an extract of jabber.el documentation: jabber.el has limited support for file transfer. The most important limit is that files sent and received are kept in buffers, so Emacs must be able to allocate enough memory for the entire file, and the file size must be smaller than the maximum buffer size.(1) jabber.el is able to exchange files with most Jabber clients (and also some MSN transports), but notably not with the official Google Talk client. The Google Talk client uses a different file transfer protocol which, at the time of this release, has not been published. -- Damien Cassou Företagsplatsen AB Phone/Fax: +46 (0)8 774 63 00 Mobile: +33 (0)6 80 50 18 91 Address: Skeppsbron 26, 4tr, SE-111 30 Stockholm Web: www.foretagsplatsen.se |
48 messages has been excluded from this view by a project administrator.
