Age | Commit message (Collapse) | Author |
|
items
bugfix: use cache table of roster (created on every refresh) to get selected row object,
fixing bad row selecting when jumping over group (was changing pos variable and
not selected_row while moving to next contact after group)
|
|
fix #2170
|
|
|
|
- Disable the history when searching
- → allow moving the cursor around to select a contact when searching
- fix refresh issues
|
|
the <history/> element had a xmlns="" instead of the proper namespace.
|
|
- New option load_log defaulting to 200 to indicate the number of lines
to be loaded
- It’s still very raw, and the format of the message does not match the
format of the normal room history, for example
- Works in the Private chat, MUC, and Conversation tabs
Thanks to labedz <github@labedz.org> for the original code
|
|
fix #2150
|
|
|
|
|
|
|
|
|
|
(and fix one more issue with the refresh in the roster)
|
|
|
|
|
|
- Also fixes arefresh issue (up&down keys didn’t refresh the win)
- Rework the style of the Columns a bit (was 2-spaces indent & trailing
spaces)
|
|
- Also make Core.focus_tab_named take an optional type, and return a boolean
|
|
|
|
|
|
|
|
|
|
This reverts commit c66ec81c4530a806b0aacc2933f6493cdcbbfc82.
|
|
- The documentation is included in the commit
|
|
- Now the tab number is computed instead of assigned and fixed
- Added tabs.GapTab to keep the old behaviour
- Added a create_gaps option, defaults to true (may change in the
future)
- If there are gaps before using /set to change the option to false,
they will be removed.
(this is a preparation for the move_tab command)
|
|
(force every file opening to be with the utf-8 encoding)
|
|
Because not having that element is not allowed by the xhtml-im XEP, poezio
should put that by default.
|
|
(notably, the /message one)
All JID calls in poezio’s code were already covered, but sleekxmpp does
that, too, so each jid given to sleek must be validated, otherwise an
unwanted exception may occur.
|
|
- get rid of the ugly blacklist thing that didn’t work sometimes
|
|
|
|
(sleekxmpp added JID validation, which means that JID(something) now
raises an exception if the jid is invalid, instead of failing silently and
having JID('') as a default)
|
|
- Add a /activity command
- Load xep_0012 on start
- Add a 'l' shortcut in the roster to get the last activity
- Using "/activity" in a direct conversation will add a message in the
conversation, and not in the info buffer.
|
|
- Add /block, /unblock, and /list_blocks commands
- Enable the commands only if the server advertises the feature
- http://xmpp.org/extensions/xep-0191.html#example-9 was not tested, but
should work (could not find a server to test with)
- Add documentation for the commands
|
|
- Previously it was from lowest to highest
- Add the “Priority:” info to the “i” key in the roster
|
|
|
|
- document it
- works in per-tab config too
|
|
- All functions involved return a boolean, and the core function use
that value to determine if a refresh is needed or not. (avoids useless
refreshs)
- Scrolling with PGUP/DOWN on the roster now only does _one_ action, an
not a range corresponding to the screen size (should be way faster)
|
|
- Write the config with “option = value” instead of “option= value”
- Docstring for sighup_handler
- Optimize a join() in the main loop
- Rename the verbose get_error_message_from_error_stanza() with
get_error_message()
- Remove the unused Tab.just_before_refresh() which is litterally used
nowhere in poezio
|
|
|
|
|
|
And improve the completion in the roster (go to the resources)
|
|
|
|
(instead of the normal completion)
|
|
This commits adds a “words” variable to the configuration file. This
variable must contain a list of words, separated by colons (:).
Those words will then be completed upon tab completion in the chatrooms,
private conversations, and direct conversations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now we have to pass the textbuffer object when we want to add a line
separator.
|
|
This new features is available with M-p and M-n (previous/next).
It saves the last highlight viewed, meaning that if you scroll in the
buffer, M-n or M-p will take you to the next or previous hl compared to
the one before you started scrolling.
For convenience, going to the previous highlight of the first highlight
will take you to the bottom of the buffer, and going to the next
highlight of the last highlight will do *the same*.
If there are several highlights in one message, only the first line will
be considered a highlight.
|