| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Regular profanity.1 and profanity-command.1 for each command.
|
|
|
|
|
|
|
|
|
| |
`profanity mangen` will create for each command (`/account`, `/roster`)
an own manpage (`profanity-account.1`, `profanity-roster.1`)
See https://github.com/profanity-im/profanity/issues/1444
Needs some polishing formatting wise.
|
|
|
|
| |
We require c99/gnu99 anyways.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
We can use strchr() here.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1435
So far we didn't print the error if it contained `<error
type="cancel">`. It appears that the code always thought this is a
service-not-available (so one is either blocked or the account doesn't
exist) and printed `Recipient not found`.
But there can be other errors as well. Like in above mentioned issue
`not-allowed`.
Let's just print the text.
In case of the cancel type we still remove the jid from the chat
sessions. I'm not entirely sure whether this needs to be done in other
cases too.
|
|
|
|
|
|
|
|
|
| |
Using g_date_time_new_now_utc instead of g_date_time_new_now_local
Using g_date_time_format(timestamp, "%FT%TZ") instead of "%FT%T%:::z"
Edit:
DebXWoody created this patch because ejabberd returned an error with the
old date format.
|
|
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1354 point 3.
Since we dont use tcl and just libexpect I don't think we actually need
to link against it.
|
|\
| |
| | |
xmpp/bookmark: don't use uninitialised field
|
|/
|
|
|
|
|
|
|
|
| |
When a bookmark is created with '/bookmark add' command,
ext_gajim_minimize remains uninitialised in new bookmark object and
is read further in _send_bookmarks().
Initialise the field with 0.
Fixes #1432.
|
| |
|
|\
| |
| | |
Since the string from strerror should never be modified, use const.
|
|/ |
|
|\
| |
| | |
Fix use-after-free which is introduced in cons_alert()
|
|/
|
|
|
|
| |
Commit f12161f fixes memory leak, but introduces use-after-free issue.
Allocate new memory for win_name with g_strdup() since it is freed with
g_free() later.
|
|
|
|
|
| |
Until we have fixed their build issues.
(Py2/Py3 etc)
|
|\
| |
| | |
Cleanup/newlibs
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
So far only libstrophe is in 0.10.0 on TW.
Lets just add both since configure will choose libmesode anyways if both
are installed.
And we plan to deprecate libmesode later anyways.
|
| |
| |
| |
| |
| | |
This part of the code was waiting for xmpp_stanza_new_from_string() from
libstrophe 0.10.0.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This partly reverts d3a387a0ec6e5265f625de87318be2de610efb01.
For proanity 0.9.x we still wanted to support older glib versions so
that we can be packaged for various linux distros.
Now with 0.10 we want to move on.
|
| |
| |
| |
| |
| |
| |
| |
| | |
xmpp_stanza_get_child_by_name_and_ns
Replace our own stanza_get_child_by_name_and_ns() with the upstreamed
xmpp_stanza_get_child_by_name_and_ns() provided by the new
libstrophe/libmesode 0.10.0.
|
| | |
|
|/
|
|
| |
Close https://github.com/profanity-im/profanity/issues/1427
|
|\
| |
| | |
NetBSD support
|
| |
| |
| |
| |
| |
| |
| |
| | |
This allows profanity to work without segfaulting from NULL
pointer dereferences when used with NetBSD libcurses.
Basic functionality was tested, there may be more NULL pointer
issues hiding.
|
|/
|
|
|
|
| |
- Add NetBSD as a recognized platform without -ldl.
- Allow building with NetBSD libcurses instead of ncurses.
- Portability to NetBSD sh - use POSIX '=' instead of '=='.
|
|\
| |
| | |
Update gruvbox theme (background color)
|
|/ |
|
|\
| |
| | |
configure: support gtk3 too
|
| |
| |
| |
| |
| | |
Make Profanity compilable with gtk2 and gtk3.
Prefer the latter.
|
|\ \
| |/
|/| |
Fix memory leak in _handle_chat()
|
|/
|
|
|
| |
jid_create() for attribute "to" was called twice and the 1st object was
lost.
|
|\
| |
| | |
MAM: Only add each message once to database
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
archive_is is <stanza-id> or <result id=""> and should identify one
message stable and uniquely.
See XEP-0359: Unique and Stable Stanza IDs.
We need this for example for this situation:
* we go online with Profanity
* we fetch all messages since yesterday
* we add them to the db
* we go offline
* we go online with Profanity
* we fetch all messages since yesterday
* we only want to add the new ones
So far we don't ask MAM "give me all since last 'id'" but since a
certain date.
In case no archive_id will be set, it will be `(null)` and thus should
be inserted anyways because it won't find a value with (null) in that
row.
Because when adding we use `message->stanzaid ? message->stanzaid : "",`
so it will be empty in such a case.
Regards MAM: https://github.com/profanity-im/profanity/issues/660
Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Add stable stanza IDs to ProfMessage struct.
We parse this for 1:1 messages (MUC needs to be done too).
<stanza-id> for live messages
<result id="x"> for MAM messages
Regards MAM: https://github.com/profanity-im/profanity/issues/660
Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207
|