about summary refs log tree commit diff stats
path: root/src/command
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix typoMichael Vetter2020-02-171-1/+1
|
* Mention how to enable unencrypted file transerMichael Vetter2020-02-171-2/+2
| | | | Regards https://github.com/profanity-im/profanity/pull/1270
* Make /sendfile in PGP session configurableMichael Vetter2020-02-173-3/+23
| | | | | | `/pgp sendfile on` allows unencrypted file transfer in an PGP session. Regards https://github.com/profanity-im/profanity/pull/1270
* Make /sendfile in OTR session configurableMichael Vetter2020-02-174-6/+37
| | | | | | `/otr sendfile on` allows unencrypted file transfer in an OMEMO session. Regards https://github.com/profanity-im/profanity/pull/1270
* Make /sendfile in OMEMO session configurableMichael Vetter2020-02-174-10/+44
| | | | | | | `/omemo sendfile on` allows unencrypted file transfer in an OMEMO session. Regards https://github.com/profanity-im/profanity/pull/1270
* Disallow sendfile in e2ee chat sessionsmoppman2020-02-171-0/+35
|
* xep-0308: Add note about tab completionMichael Vetter2020-02-141-1/+2
|
* xep-0308: add note about where corrections are possibleMichael Vetter2020-02-141-1/+2
|
* xep-0308: only allow /correct when corrections are enabledMichael Vetter2020-02-141-0/+5
|
* xep-0308: add caution noteMichael Vetter2020-02-141-1/+1
| | | | | We need to change the buffer structure first, so that we save the from field there.
* xep-0308: Make /correct work without quotation marksMichael Vetter2020-02-143-9/+12
| | | | | | Now we can specify an unlimited amount of arguments for commands. Maybe this is also helpful for other commands that use quotation marks so far.
* xep-0308: Fix sending corrections for multiple wordsMichael Vetter2020-02-143-4/+7
|
* xep-0308: Add autocompletion of last message for /correctMichael Vetter2020-02-141-4/+29
|
* xep-0308: Implement LMC for outgoing MUC messagesMichael Vetter2020-02-141-0/+12
| | | | | | Including OMEMO encrypted ones. Also rename `win_println_me_message()` to `win_print_outgoing_muc_msg() as I think it's a more descriptive name.
* xep-0308: Don't check whether receiving clients supports this featureMichael Vetter2020-02-121-16/+1
| | | | | | | | | | | | | | | | | | | | | | | | | XEP-0308 Version 1.1.0 (2019-05-15) states "It is expected that clients will not send message corrections to clients that do not support them, as non-supporting clients will render these as duplicate (corrected) messages" ``` 10:12:47 - jubalh: Do clients actually check whether other clients support xep0308 (LMC) before sending? 10:13:13 - pep.: not poezio, and I doubt anybody does. it's the "but carbons/MAM" argument 10:13:49 - jubalh: Profanity doesnt support this yet. So I always get the message twice. One time the message, and then the corrected ones. And I think that's right. But I understood xep0308 correctly it sais a client shouldnt sent a message with 'replace' if the client doesnt support it? I don't see why 10:14:50 - Ge0rG: jubalh: because you might also use Conversations and read the backlog from MAM on conversations 10:15:51 - jubalh: Ge0rG: sorry? 10:16:36 - Ge0rG: jubalh: when I'm sending you a message, I don't know which client you'll use to read it. So it doesn't make sense to limit the features I use 10:27:57 - jubalh: Yes. That's why I'm confused by thestatement in the XEP 10:28:13 - jubalh: "It is expected that clients will not send message corrections to clients that do not support them, as non-supporting clients will render these as duplicate (corrected) messages. " 10:28:37 - Holger: Yes, you're both saying the same thing. And yes I agree, that part of the XEP is nonsense. We have that "check whether the peer's client supports it" stuff in various XEPs that depend on recipient's features and it never makes sense as it doesn't cope with multi-device, MAM, groupchat. 10:28:53 - jubalh: First: You don't know if he is connected with several clients. Some supporting it and some not. Second: Why not just resend the new corrected message? Then he has both messages and no information is lost. If he only gets the first one information is lost 10:29:20 - jubalh: Okay 10:29:30 - jubalh: Then I won't implement it this way. Thanks guys! 10:29:34 - Holger: Well UX is a bit meh if the recipient doesn't support it (I'm an MCabber user and know what I'm talking about) but I see no better solution, yes. ``` So it makes more sense to just always send it. Non supporting clients will then get the message and the corrected message. So they get it "twice". Which is the right thing to do in my opinion.
* xep-0308: enable corrections for outgoing encrypted messagesMichael Vetter2020-02-121-2/+3
|
* xep-0308: update the UI upon sending a corrected messageMichael Vetter2020-02-111-0/+1
| | | | | So far we don't do this for encrypted messages. Still needs to be done. And MUC also needs to be done.
* xep-0308: Implement `/correct` to correct the last send messageMichael Vetter2020-02-104-0/+70
| | | | | | | | So far the correction is sent. But the UI in Profanity itself is not updated. Also autocompletion for `/correct` with the last sent message is missing.
* xep-0308: create setting to toggle lmcMichael Vetter2020-02-102-4/+6
| | | | and print settings if only `/correction` is run.
* xep-0308: set correction char in configMichael Vetter2020-02-103-1/+29
|
* xep-0308: add `correction` autocompletionMichael Vetter2020-02-102-0/+41
|
* 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-311-80/+92
| | | | Fix #1068
* Change theme handlingMichael Vetter2020-01-293-12/+44
| | | | | | | | | | | | | | | | 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
* XEP-0092: Add configuration option to choose whether to send OS nameMichael Vetter2020-01-244-1/+25
| | | | | `/os on|off` now let's one choose whether to include the OS name once `/software` (XEP-0092) is ran on us.
* Fix titlebar and rosterbar descriptionMichael Vetter2020-01-231-3/+2
|
* Add option to display MUC name or JID in titlebarMichael Vetter2020-01-234-4/+49
| | | | Add `/titlebar use [name|jid]`.
* Add `/roster room use` autocompletionMichael Vetter2020-01-231-0/+12
|
* Add `/roster room use` commandMichael Vetter2020-01-232-0/+23
| | | | | | | `/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.
* Use OMEMO for offline MUC members (#1242)Paul Fariello2020-01-201-7/+11
|
* Refactor /roster show/hide (#1251)Daniel Lublin2020-01-121-133/+44
| | | Refactor /roster show/hide
* Make `/roster color` configurable when offlineMichael Vetter2019-12-201-4/+4
|
* Refactor _cmd_set_boolean_preferenceMichael Vetter2019-12-191-9/+10
| | | | Only compute string if necessary.
* Add /occupants color commandMichael Vetter2019-12-193-0/+15
| | | | | | | | `/occupants color on|off` to enable or disable XEP-0392 also for the MUC occupants. Regards https://github.com/profanity-im/profanity/issues/1191
* Add /roster color commandMichael Vetter2019-12-193-0/+13
| | | | | | | `/roster color on|off` to enable or disable XEP-0392 also for the roster. Regards https://github.com/profanity-im/profanity/issues/1191
* xep-0084: Improve helpMichael Vetter2019-12-181-1/+3
|
* xep-0084: add /avatar help and autocompletionMichael Vetter2019-12-182-3/+21
|
* xep-0084: Look for specific user and print IDMichael Vetter2019-12-183-1/+25
| | | | Add a `/avatar` command.
* Implement Color Vision Deficiencies settingMichael Vetter2019-12-123-6/+60
| | | | | | Implement settings for redgreen and blue blindness. Regards https://github.com/profanity-im/profanity/issues/1191
* Add initial support for XEP-0392Michael Vetter2019-12-094-1/+25
| | | | | | | | | | | | | | The last 3 commits added basic support. Thanks @aaptel! This commit adds basic settings interface to use it. See `/color on|off`. We still have to enable settings for color blindness. And maybe another setting to decide whether to color the occupantslist/roster with the same algo. Regards https://github.com/profanity-im/profanity/issues/1191
* Merge /group command into /rosterMichael Vetter2019-11-253-146/+118
| | | | | Fix https://github.com/profanity-im/profanity/issues/1229 Regards https://github.com/profanity-im/profanity/issues/1116
* Add vim modelineMichael Vetter2019-11-136-0/+6
|
* Merge /chlog and /grlog commands into /loggingMichael Vetter2019-11-124-43/+60
| | | | | | | Instead of `/chlog on` we now have `/logging chat on`. Instead of `/grlog on` we now have `/logging group on`. Fix https://github.com/profanity-im/profanity/issues/1224
* cmd_room: don't check arguments twiceMichael Vetter2019-11-081-13/+4
|
* Fix setting of status messageMichael Vetter2019-11-072-2/+6
| | | | | | | | | Seems this actually never worked. Now it does. `/status set online "This is my text"` `/status set away bye` `/status set away`
* Merge state commands (online, away) into statusMichael Vetter2019-11-064-141/+113
| | | | | | | | | | | | Before we had `/online`, `/away`, `/dnd`, `/chat`, `/xa`. These commands are no longer available. We have `/status set online` etc now. Before `/status` was used to get the status of a contact. This now moved to `/status get`. Regards https://github.com/profanity-im/profanity/issues/1116
* Fix formatting for invite command helpMichael Vetter2019-11-051-1/+1
|
* Merge /invite, /invites and /decline commandsMichael Vetter2019-11-054-85/+85
| | | | | | | | | | `/invite <contact>` became `/invite send <contact>. `/invites` became `/invite list`. `/decline` became `/invite decline`. Accept is still done via `/join`. Regards https://github.com/profanity-im/profanity/issues/1116
* Add `/titlebar show presence` commandMichael Vetter2019-11-052-0/+7
| | | | | | | Additionally to `/presence titlebar on` we now allow the setting via /titlebar show|hide presence` since it's about the titlebar. Regards https://github.com/profanity-im/profanity/issues/1116
* Add `/titlebar show resource` commandMichael Vetter2019-11-053-3/+10
| | | | | | | | | | | Additionally to `/resource titlebar on` we now allow the setting via /titlebar show|hide resource` since it's about the titlebar. But makes sense to have it in `/resource` too because there is `/resource message on|off` too. And this one doesnt have an setting of it's own. Regards https://github.com/profanity-im/profanity/issues/1116