| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| | |
If `~/dir` exists profanity exits for me.
Whole code for updating plugins from a dir isn't even implemented. Even
though some messgages suggest otherwise.
Remove this and only allow updating of one file.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Packagers can package https://github.com/profanity-im/profanity-plugins
or another collection of plugins to `/usr/local/share/profanity/plugins`
(python) and `/usr/local/lib64/profanity` (c).
`/plugins` will list these globally available plugins now along with the
ones thare are installed (`~/.local/share/profanity/plugins`) and loaded.
Regards https://github.com/profanity-im/profanity/issues/945
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Two options to install plugins.
Mention the whole path:
`/plugins install ~/src/profanity-plugins/my.py`
Mention only the plugin name:
`/plugins install my.py`
The latter will look in `/usr/local/share/profanity/plugins/` for the
file and copy it over to `~/.local/share/profanity/plugins`.
At first I was thinking about loading the plugins from the global
location. But users most likely don't want to have all plugins activated
that an admin installs on a system.
Regards https://github.com/profanity-im/profanity/issues/945
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I feel like this mostly is confusing people.
Also don't see much value for it.
To me it looks like a regular workflow is like:
```
/plugin install ~/src/profanity-plugins/my.py
```
The whole thing with sourcepath, install (which also loads without
having that described anywhere), load etc is confusing.
Also each plugin file that is present in
`.local/share/profanity/plugins` will then be auto loaded. Which means
after installation.
|
|/ |
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1575
|
| |
|
| |
|
| |
|
|\
| |
| | |
Bugfixes for OX implementation
|
| |
| |
| |
| |
| | |
* Help / message description
* C-Code format
|
| |
| |
| |
| |
| |
| |
| | |
* autocomplete for /ox discover
* fixed help description
* Implemented /ox char command
* Validated KeyID length
|
| |
| |
| |
| |
| |
| |
| | |
`/silence on` will throw away all messages (type: chat, normal) that
come from jids that are not in the roster.
Implement https://github.com/profanity-im/profanity/issues/955
|
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of `/blocked add [<jid>] [report-abuse|report-spam [<message>]`
have:
* /blocked add [<jid>] [<message>] (like before)
* /blocked report-abuse [<jid>] [<message>]
* /blocked report-spam [<jid>] [<message>]
|
| |
| |
| |
| | |
So that we will get aware of a version mismatch.
|
|/
|
|
|
|
|
|
|
|
|
| |
Report and block:
`/blocked add someone@domain.org report-abuse This is not nice`
`/blocked add someone@domain.org report-spam This is not nice`
Regular block:
`/blocked add someone@domain.org`
Implement https://github.com/profanity-im/profanity/issues/1434
|
|
|
|
| |
See https://github.com/profanity-im/profanity/issues/1521#issue-860017824
|
|
|
|
|
| |
No need to check anymore since we are now saving per account.
Like this we also could reopen the same file again.
|
| |
|
|
|
|
|
| |
See
https://github.com/profanity-im/profanity/issues/1521#issue-860017824
|
|
|
|
|
|
|
| |
`/bookmark list` lists all bookmarks with its details.
`/bookmark list <jid>` shows the details of a single bookmark.
Implement https://github.com/profanity-im/profanity/issues/1558
|
|\
| |
| | |
Feature - attention flag
|
| |
| |
| |
| | |
Attention flag for groupchat and display the windows via "/wins attention"
|
| |
| |
| |
| |
| |
| |
| | |
User is able to toggle a flag for chat windows. This flag should be used to mark
the window for "Attention".
Use Ctrl+f to mark the window.
|
|/ |
|
|
|
|
|
| |
Display the OMEMO device ID which has been generated, when the user generated
OMEMO crytographic materials via /omemo gen.
|
| |
|
|
|
|
| |
So users don't get surprised if they don't know the barejid of the nick.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In https://github.com/profanity-im/profanity/issues/1070 we have:
`OMEMO encryption for MUC PM (OMEMO MUCs are not anonymous, so we should
start a regular 1:1 in this case instead of MUC PM. A discussion started
to make this a general feature #1531)`
In https://github.com/profanity-im/profanity/issues/1531 we have the
general issue to start regular 1:1 messages instead of MUC PMs if the
room is non-anonymous.
This is like suggested in https://docs.modernxmpp.org/client/groupchat/.
|
|
|
|
|
|
|
|
|
|
| |
Old: `/intype on|of`
Typing information is printed in console and titlebar.
New: `/intype titlebar|console on|off`
Typing information can be configured in more detail.
Regards https://github.com/profanity-im/profanity/issues/1516
|
|
|
|
|
|
|
| |
Add OMEMO trust mode capabilities.
* ToFu / first usage
* blind trust
* manual
|
|
|
|
|
|
| |
`/executable set editor /full/path/to/edit`.
Regards https://github.com/profanity-im/profanity/issues/1521
|
|
|
|
|
| |
Probably many people render text in their head to markdown
automatically.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
compose.editor is the path to the executable ( default /usr/bin/vim )
|
|
|
|
|
|
|
|
| |
* Generating a unique file name in tmp_dir folder
* Changed exec of vim to exec of sensible-editor
* Test file exists and create file with "private" rights
* Send a preview of the message in the window
* Delete temp file
|
|
|
|
| |
Goal is to launch an external editor (eg vim) to edit the text there.
|
|
|
|
|
|
|
|
|
| |
If the message (key) can't be encrypted for any device, sending the
message is refused and an informative error message is presented to the
user.
Also, don't encrypt for the same device, since the OMEMO XEP disallows
this.
|
|
|
|
|
|
| |
The function `omemo_start_session` was effectively called twice in the
`/msg` command: Once in `chatwin_new` and afterwards in `cmd_msg`. I've
removed the second call.
|
|
|
|
|
|
|
| |
_GNU_SOURCE was even in some files where it was not needed at all
(http*).
Let's replace asprintf() with g_strdup_printf().
|
|
|
|
|
|
|
|
|
| |
Two mistakes were here:
* `/autoaway time away` without a time argument segfaulted
* `/autoaway message away` without a mesage set to (null). We have
`/autoaway message off to set it off.
Also use g_strcmp0() instead of strcmp().
|
|
|
|
|
|
|
|
|
|
| |
`/affiliation register` can now be used to register a nickname with a
MUC.
Tested with a server without forms. Couldn't find a server which
supports forms yet.
Implements https://github.com/profanity-im/profanity/issues/1210
|
|
|
|
| |
closes https://github.com/profanity-im/profanity/issues/1211
|
|
|
|
|
| |
Some time ago we introduced get_expanded_path().
No need to build paths manually anymore to get ~.
|
| |
|
|
|
|
|
| |
Just prints a different string to console.
Useful for changing passwords or account registration.
|