| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
Related to https://github.com/profanity-im/profanity/issues/1019
|
|/ / / |
|
| | |
| | |
| | |
| | | |
Fix memory leak.
|
|\ \ \
| | | |
| | | | |
Add option to set all window related time formats
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Implements feature requested at: https://github.com/profanity-im/profanity/issues/632
So instead of:
/time console set <format>
/time chat set <format>
/time muc set <format>
/time mucconfig set <format>
/time private set <format>
/time xml set <format>
As a short cut the user can do:
/time all set <format>
Excluding statusbar and lastactivity settings since they are not for main windows, but used slightly differently.
|
| | |
| | |
| | |
| | | |
Mouse support has been disabled long ago.
|
| | | |
|
| | |
| | |
| | |
| | | |
Like discussed with James.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Feature/704 ui behaviour reconnect
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
After pasis review of my code he thinks it's better to safe the
timestamp per MUC so we can account for some problems that could occur
with timing.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For #704 we don't show the room history upon reconnect.
Now we also don't show the room subject in the channel
upon re-established connection.
|
| | | |
| | | |
| | | |
| | | | |
Let's test for mucwin earlier.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If re-establish a connection don't print the room history again.
In case there there happened nothing at all since we got the room
history on the last connection.
And in case there were no new messages during the time we have been
disconnected.
Instead of printing the room history again we now print 'Re-established
Connection'.
This adds a bit of overhead since we save the timestamp upon every MUC
message.
See: https://github.com/profanity-im/profanity/issues/704
|
|\ \ \ \
| | | | |
| | | | | |
Rejoin all MUCs on reconnect
|
|/ / / /
| | | |
| | | |
| | | | |
Should fix https://github.com/profanity-im/profanity/issues/1120
|
|\ \ \ \
| | | | |
| | | | | |
Iterate logfiles until 100 are reached
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fix https://github.com/profanity-im/profanity/issues/519
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
paulfariello/feature/remove_session_when_untrusting_omemo_device
Remove OMEMO session when untrusting a fingerprint
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We have to store known_devices in a long term fashion otherwise we might
not be able to delete session if it is remove from device list server
side.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Print omemo start related msgs into correct window
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some code was duplicated/similar.
The parts about using a chatwin while being started from another window
(recipient provided) and being a chatwin were the same.
Like this it should be easier to read and less code.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Print them in the window of the contact. Not just the current window.
Fix https://github.com/profanity-im/profanity/issues/1093
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Only complete certain omemo commands if connected
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some of the omemo commands depend on the roster being present.
Several of those functions call `assert()` if that's not the case.
Modify omemo autocompletion in such a way that only things that don't
need the roster will be completed. Only works on first level.
When typing `/omemo` it will still complete to `/omemo start` but not
offer suggestions for that, but print a message that you need to be
connected.
Fix https://github.com/profanity-im/profanity/issues/1117
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Improve plugin load/install failure message
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In case Python or C plugins are disabled install/load failed silently.
Notify the user that we can't load them because profanity was built
without support for plugins.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Use travis matrix to test more systems (#1100)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
+ Arch and Debian are run in Docker containers, as openSUSE Tumbleweed.
+ OSX/macOS doesn't use any containers.
* Homebrew is used to fetch all the dependencies.
* The dependencies are declared in the Brewfile.travis file.
+ The travis-build.sh script has been modified to check for the current
OS and the different configure flags has been moved into an array
that'll be looped through instead.
The xscreensaver (for libXScrnSaver) flags has been removed for macOS
as it only makes sense for systems running X11, which macOS doesn't
(usually) do.
+ Some minor shellcheck fixes, too.
Fixes: #1100
|
| | | | | | |
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Check autoconnect set settings
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Check that user doesnt do `/autoconnect set `.
Which would result in: `Account '(null)' does not exist`.
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Fixes https://github.com/profanity-im/profanity/issues/1112
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add omemo.char to themes
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Thanks to @kaffekanne for noticing this!
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Users where under the impression that you can't colour the time displayed
in the statusbar.
Let's add it to the template, and also change all themes to use the same
colour for the time as for the statusbar text.
|
|\ \ \ \
| | | | |
| | | | | |
Fix SIGABRT on lost connection
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We destory the roster in ev_disconnect_cleanup().
Adding a function to test if the roster has been destroyed and testing
for it in the statusbar.
So now when the connection is lost 'Lost connection' is printed in all
open windows.
We can then reconnect with `/connect accountname`.
Should fix https://github.com/profanity-im/profanity/issues/1083
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
status_bar_new() and status_bar_active() are almost identical.
Let's use one helper function to not duplicate code.
I thought about renaming both functions into one and adding another
parameter but didn't come up with a good name for the function that
clearly describes what it does. So staying with current names + helper
functions.
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Save the name for displaying the windows in the statusbar inside the tab
object.
So far we calculated them repeatedly and this created issues when we
lost the connection.
Regards https://github.com/profanity-im/profanity/issues/1083
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Don't clear saved account data in session_disconnect()
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If connection loss occurs, it calls session_disconnect() eventually.
This function clears saved account data which is required for
reconnection. Therefore, when reconnect timer expires, we get errors:
02/06/2019 04:53:42: stderr: ERR: (profanity:17115): GLib-CRITICAL **:
04:53:42.305: g_key_file_has_group: assertion
'group_name != NULL' failed
02/06/2019 04:53:43: prof: ERR: Unable to reconnect, account no longer
exists: (null)
To solve it, don't clear the saved data in session_disconnect(). It will
be cleared properly on connection loss if reconnect timer is not
configured. But won't be cleared with /disconnect command.
So, after /disconnect the data will live in memory until the next
/connect.
Also, remove some copy-paste in connection loss path.
|
|\ \ \ \
| |/ / /
|/| | | |
Cancel autoping timer on disconnect or connection loss
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If Profanity is disconnected in any way before ping response is
received, the autoping timer will expire after the next connection
is established. As result, user will be disconnected immediately.
Cancel autoping timer in ev_disconnect_cleanup(), so it is done
for all kind of disconnections.
|
|\ \ \
| | | |
| | | | |
xmpp/connection: fix #1103
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When connection is lost, profanity tries to disconnect what leads
to an infinite loop. The loop occurs, because connection_disconnet()
runs xmpp_run_once() separately and waits for XMPP_CONN_DISCONNECT
event. But it doesn't happen, because the connection object is
disconnected.
As solution, don't disconnect after XMPP_CONN_DISCONNECT is received.
Also, don't free libstrophe objects while the event loops executes,
because the event loop continues using objects after callbacks quit.
|