-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profanity in compose-mode get disconnected #1888
Comments
Thats to be expected. |
I want to add some details. It can be fixed by calling It can be renamed to something like: |
Well, it does not fix the issue, we have to read the edited file once the editor is closed. It probably would make sense to a bit rework forking part (we can fork: 2nd part: Also we should ideally keep all this time UPD: the actual problem is that profanity keeps redrawing (and probably listening to the input), so we somehow need to stop redrawing, but to continue listening network. I don't see really good way to get it done easily... |
debug-profanity.log
profrc-profanity.txt
Description of the issue
When using the compose editor during few minutes, Profanity display an error message. It says the connection has been lost.
It happens with any program used as editor (tested on nano + emacs-nox). It happens in 1-1 chat and in chatrooms. It is not depending on message-length.
Version
How to reproduce
Launch Profanity, then start a discussion in 1-1 chat
launch editor (M-c or /editor) then wait 4min. Do not wait 5sec
type your message in editor
save/exit the editor : "Lost connection - Reconnecting" appears in the chat window.
The facts
The reconnection depends on settings in profrc file. In my profrc, Profanity will reconnect immediatly, but that is not the default configuration. For some users, there might be a delay or no reconnection at all.
The "Lost connection" message is not really true, because the XMPP account is never shown as "offline" in rosters of my contacts (after 4min).
You are able to send the message right-after compose. No message is lost.
(The XMPP account used to produce the logs is a test account).
The text was updated successfully, but these errors were encountered: