about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* xep-0308: create setting to toggle lmcMichael Vetter2020-02-107-11/+27
| | | | and print settings if only `/correction` is run.
* xep-0308: set correction char in configMichael Vetter2020-02-105-1/+58
|
* xep-0308: add `correction` autocompletionMichael Vetter2020-02-104-0/+48
|
* xep-0308: Initial support for incoming LMCMichael Vetter2020-02-105-7/+75
|
* avatar: use unique id for stanza idMichael Vetter2020-02-073-7/+10
| | | | "retrieve1" should have been only for testing.
* Clear buffer upon /clearMichael Vetter2020-02-071-0/+2
| | | | | | | | I think both the window and the buffer should also be cleared in case `/clear` is issue and persist_history is off. Otherwise it could happen that win_redraw() redraws the whole content of the buffer again.
* Set PREF_COLOR_NICK to false by defaultMichael Vetter2020-02-061-1/+1
|
* Add default pref for PREF_COLOR_NICKPaul Fariello2020-02-051-0/+2
| | | | Fix a segfault if corresponding preference is not saved in config file.
* rosterwin: end correct colorsMichael Vetter2020-02-031-1/+1
| | | | | Actually presence_colour should be stopped there. Thanks to rumin-miller for finding this.
* Add `/omemo char` autocompletionMichael Vetter2020-02-031-0/+1
| | | | Seems this got forgotten.
* Add context to autocomplete_with_func and use it for omemo trust commandPaul Fariello2020-01-3123-129/+159
| | | | Fix #1068
* fix: Initialize variable in stanza_get_oldest_delay()Michael Vetter2020-01-301-1/+1
|
* Fix error in stanza_get_oldest_delay()Michael Vetter2020-01-301-3/+3
| | | | Introduced in bf2e09feee1697c570fcfb9e1e44a8ec991bd196.
* muc: save oldest timestampMichael Vetter2020-01-303-3/+38
| | | | | | | | | | | | | | | | | | So far we saved the timestamp which also had the `from`. But we need this only to find out whether it's MUC history. For displaying we should use the oldest delay timestamp. Also in https://github.com/profanity-im/profanity/commit/61f66966ddfe8ebd8bae26dd7ff92d777004edda#diff-4926fd4577a336bd3eb240f8104a5c5bL837 a error was introduced. Before we saved the timestamp in all cases. And only if timestamp AND from was given we went into MUC history case. Normal timestamp saving was not done anymore only if it also had a from attribute. Regards https://github.com/profanity-im/profanity/issues/1254
* stanza: Refactor stanza_get_delay_from()Michael Vetter2020-01-301-26/+49
| | | | Have two helper functions one for XEP-0203 and one for XEP-0091.
* Change theme handlingMichael Vetter2020-01-296-17/+51
| | | | | | | | | | | | | | | | So far when loading a theme it also overwrote the preferences the user set. Lengthy discussion can be found at https://github.com/profanity-im/profanity/issues/1077 Now we use `/theme load themename` to load the [colours] part of a themem only. `/theme full-load themename` will load the complete theme including preferences set in there. Regards https://github.com/profanity-im/profanity/issues/1077
* Add comments to preferences.cMichael Vetter2020-01-291-2/+2
|
* Refactor theme.cMichael Vetter2020-01-291-27/+44
| | | | | | Make _theme_list_dir() static. Sort _load_preferences() loadings accoding to type. Add comments.
* Revert "Save first delay tag as timestamp"Michael Vetter2020-01-281-9/+0
| | | | | | | | This reverts commit ef00b10c90aef8b75415fae558789d21bb975d75. According to reply by user in https://github.com/profanity-im/profanity/issues/1254#issuecomment-578389784 it didn't help.
* Save first delay tag as timestampMichael Vetter2020-01-241-0/+9
| | | | | | | | | | | | So far we got the first delay with a from that comes from the server. This way we know it's MUC history. Now we take the first time stamp we actually find. Which is likely the one being added first. And should contain the correct time to display. It would be nicer to actually compare the dates though. Regards https://github.com/profanity-im/profanity/issues/1254
* XEP-0092: Add configuration option to choose whether to send OS nameMichael Vetter2020-01-246-1/+36
| | | | | `/os on|off` now let's one choose whether to include the OS name once `/software` (XEP-0092) is ran on us.
* Fix typo in commentMichael Vetter2020-01-231-1/+1
|
* xep-0092: add config option to set whether OS is revealedMichael Vetter2020-01-233-14/+27
| | | | | | Default is on. `revail.os=false` in the `connection` section of the config can disable it. A command to configure this will follow.
* xep-0092: send OS tooMichael Vetter2020-01-231-0/+23
| | | | | So far we only sent client name and version. Let's also send the OS name.
* Add option to notify about version requestMichael Vetter2020-01-233-0/+12
| | | | | | | | | | Cannot be configured for now. Can be set via `adv.notify.discoversion` in the `notification` section. Will notify about version requests via XEP-0092 and XEP-0232. Client version can still be seen via caps (capabilities). See `stanza_attach_caps()`.
* Add myself to copyrightMichael Vetter2020-01-232-0/+2
|
* Refactor rosterwin_roster()Michael Vetter2020-01-231-18/+17
| | | | Use helper function for duplicate code.
* Fix titlebar and rosterbar descriptionMichael Vetter2020-01-231-3/+2
|
* Add option to display MUC name or JID in titlebarMichael Vetter2020-01-239-9/+77
| | | | Add `/titlebar use [name|jid]`.
* Display MUC name in titlebarMichael Vetter2020-01-231-1/+8
|
* Fix spacing in titlebar.cMichael Vetter2020-01-231-2/+0
|
* Print `roster rooms use` in info pageMichael Vetter2020-01-231-0/+4
|
* Respect `/roster room use` setting also when sorted for serviceMichael Vetter2020-01-231-8/+14
|
* NULL room_name in win_create_muc()Michael Vetter2020-01-231-0/+1
|
* Add `/roster room use` autocompletionMichael Vetter2020-01-231-0/+12
|
* Add `/roster room use` commandMichael Vetter2020-01-236-2/+48
| | | | | | | `/roster room use name` to use the name of the MUC in the roster list. `/roster room use jid` to use the jid of the MUC in the roster list. Display it only in case `/roster room by none` is set so far.
* Save MUC room name in ProfMucWinMichael Vetter2020-01-233-0/+6
| | | | We will need this if we want to display the Name instead of the JID.
* xep-0084: use hash table for avatar lookupMichael Vetter2020-01-221-8/+11
|
* XEP-0392: get background color from themeMichael Vetter2020-01-223-1/+17
| | | | | | | So far we just used -1 (default color). Now we actually check whether `bkgnd` is set in the theme file and use this if available. Fix https://github.com/profanity-im/profanity/issues/1255
* rosterwin: remove duplicate ifMichael Vetter2020-01-221-3/+0
|
* Add support for 12 bytes IVPaul Fariello2020-01-203-4/+4
| | | | | | | 16 bytes IV should be used. Some clients can't use it so we should also support decrypting 12 bytes IV. Fix #1253
* Fix maybe uninitialized and don't guard g_freePaul Fariello2020-01-201-17/+14
|
* Ignore invalid base64 in OMEMO stanzasPaul Fariello2020-01-201-10/+44
| | | | Fixes #1239
* Use OMEMO for offline MUC members (#1242)Paul Fariello2020-01-208-37/+128
|
* Refactor /roster show/hide (#1251)Daniel Lublin2020-01-121-133/+44
| | | Refactor /roster show/hide
* Merge pull request #1248 from svensp/masterMichael Vetter2020-01-051-1/+3
|\ | | | | OMEMO message keys allow prekey="1" alongside prekey="true"
| * omemo: Check for `1` alongside `true` in an omemo encrypted message stanzaSven Speckmaier2020-01-031-1/+3
| | | | | | | | | | | | | | | | prekey is defined as `<xs:attribute name="prekey" type="xs:boolean"/>` which allows both `true` and `1` as truthy values. Not checking for `1` breaks omemo encryption when interacting with clients which set prekey="1", example: psi+ 1.4.983 Regards https://github.com/profanity-im/profanity/issues/1247
* | Update my Copyright to 2020Michael Vetter2020-01-0324-26/+26
|/
* Add comments to avatar.cMichael Vetter2019-12-231-8/+11
| | | | And use better function names.
* Dont kill *.char preferences if theme doesnt contain itMichael Vetter2019-12-201-14/+0
| | | | | | | | | | | | | | | | | | | | | So far `/occupants char *`, `/roster contact char *`, `/roster room char #`, `/roster header char -`, `/occupants header char -` was saved and loaded from the preferences. But was overwritten when the theme was loaded. If the theme didn't set these values the value was just cleared. Despite that it might have been set in the users preferences. Funny enough the themes don't operate generally like this. For example `otr.char` is not cleared. This is again due to our borked theme/prefs concept (https://github.com/profanity-im/profanity/issues/1077). For now let's just use the one set from the preferences if it's set. The theme will however overwrite it if it is set there. Fix https://github.com/profanity-im/profanity/issues/1244
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-01 05:07:03 +0000