| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
This and the following commits should make a couple of more configs
allow utf8 chars so people can use their weird icons :-)
We did the same for the otr/omemo/pgp indicators at:
https://github.com/profanity-im/profanity/commit/1f8b1eb740391941e79e1004ad041f8178a2b674
https://github.com/profanity-im/profanity/commit/5cf6ee1bc6d0b99b01891bc455a657bf022a72b0
|
| |
|
|\
| |
| |
| | |
Add in-band account registration
Fix https://github.com/profanity-im/profanity/issues/199
|
| | |
|
| |
| |
| |
| |
| |
| | |
doesnt segfault on register, but aborts when you type after registering
need to find a way to disconnect later
|
| |
| |
| |
| | |
very bad and spaghetti will fix later
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Added JABBER_RAW_CONNECT[ING/ED] connection states
- Added cl_ev_connect_raw and session_connect_raw to conform to normal
connection functions
- Fixed SIGABRT during registration
- Added a check in cmd_register to ensure it's actually connected before
registering--but this will always fail atm
|
| |
| |
| |
| | |
add auth param, switch host and username params, rename host param to server
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`/plugins install` installs a plugin to
`.local/share/profanity/plugins`.
And also loads it.
When a plugin is loaded it will automatically be added to the `profrc`
file like this:
```
[plugins]
load=my.py;
```
On the next start Profanity will try to load this plugin again unless
`/plugin unload my.py` is called.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
|/
|
|
|
|
| |
alt+f is the default readline shortcut for forward one word.
Regards https://github.com/profanity-im/profanity/issues/1580
|
|\
| |
| | |
OMEMO autocomplete untrust
|
| |
| |
| |
| | |
Just a copy-past of autocomplete trust implementation.
|
| | |
|
| | |
|
| |
| |
| |
| | |
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
|
|/ |
|
|
|
|
| |
Changed in a5a0dd6c919a2b4f12ef2b4f57a0d9a2a9cabf34
|
|
|
|
| |
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
|
|
|
|
|
| |
See
https://github.com/profanity-im/profanity/issues/1521#issuecomment-854110973
|
|
|
|
|
|
|
| |
`/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/.
|