From stefan.kropp at posteo.de Fri Feb 11 14:44:40 2022 From: stefan.kropp at posteo.de (Stefan Kropp) Date: Fri, 11 Feb 2022 13:44:40 +0000 Subject: [profanity] Keybinding Message-ID: <20220211134440.a5g2fdyiy4jlboef@posteo.de> Hello, there are some issues with the keybinding in profanity. Some keybindings are not working for me. I think there are also some things which can be improved, just to be more "power full" on the way how profanity can be used. Example: The key binding of win 1-0 and q-p is nice, but for my daily workflow not really helpful. Maybe we can introduce ESC--Keybindings. # ESC W - Jump to window * Use ESC W 1 to ESC W 0 for Window 1 to 10 * Use ESC W Q to ESC W P for Window 11 to 20 This is the same how it's working now, but with the W-Key just after the ESC. # ESC N - Navigation keys * Use ESC N b - back * Use ESC N n - next * Use ESC N f - flag window # ESC B - JIDs based on configuration * Use ESC B 1 for profanity-muc * Use ESC B 2 for mama * Use ESC B 3 for wife We can add a configuration to let the user choose his own keybindings for JIDs / MUCs. # ESC M - message keys * Use ESC M a - unread message * Use ESC M f - unread flagged message # ESC R - Roster / SubWindow * Use ESC R k - Roster up * Use ESC R j - Roster down # ESC S - Scroll * Use ESC S k - Scroll up * Use ESC S j - Scroll down # Shortcuts - ESC * ESC 1 * ESC 2 * ESC 3 * .... Maybe we can make those ESC-Keys a little bit easier, but it would be very power full, because we are able to bind a lot of keys to functions. Example, Scrolling can be bind for scroll per line, page and in 10 line steps, We may are able to bind keys for status (online, away, xa,..) There is a small patch file included to try those kind of changes. -- Stefan Kropp -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-New-key-binding.patch Type: text/x-diff Size: 6574 bytes Desc: not available URL: From stefan.kropp at posteo.de Mon Feb 14 07:04:06 2022 From: stefan.kropp at posteo.de (Stefan Kropp) Date: Mon, 14 Feb 2022 06:04:06 +0000 Subject: [profanity] XEP-0453: DOAP usage in XMPP Message-ID: <20220214060406.vg2c44ywupv44wfw@posteo.de> Hello, find attached a first version of a doap file. Is there somebody how can check and maintain this file for profanity? For the most XEPs I added 'partial' as status. We should check the status and add a note. -- Stefan Kropp -------------- next part -------------- profanity 2012-02-02 Free console XMPP client written in C Freier XMPP Client f?r die Console geschrieben in C Profanity is a console based XMPP client written in C using ncurses and libstrophe, inspired by Irssi Profanity ist ein Konsolen basierter XMPP Client. Geschrieben in C mit Verwendung von ncurses und libstrophe, inspiriert von Irssi en C Linux macOS FreeBSD OpenBSD Android (Termux) complete 2.0 unkown complete 1.4 unkown complete 2.5rc3 unkown Use /disco items and /disco info partial ? ? partial 1.2 ? partial 1.3.0 0.6.0 No multi-step yet. partial 1.15.8 0.7.0 Used for OMEMO partial 2.4 0.11.0 Only password change partial 2.1 ? partial 1.4 ? partial 1.1 ? partial ? ? partial 1.1.1 0.11.0 partial 1.0.1 ? partial 1.2 ? partial 1.3 ? partial 2.0.1 ? partial 2.0 ? partial 1.0 ? partial 1.0 ? partial 1.1 ? partial 0.12.1 ? partial 1.2.0 0.9.0 partial 0.6.1 0.8.0 Only origin-id, no stanza-id yet. partial 1.0.0 ? partial 0.3.2 ? partial 0.2.0 0.11.0 partial 0.3 0.11.0 partial 0.3.0 0.7.0 partial 0.7.0 0.8.0 partial 0.1.0 0.10.0 0.11.1 2021-09-28 From jubalh at iodoru.org Mon Feb 14 11:26:19 2022 From: jubalh at iodoru.org (jubalh at iodoru.org) Date: Mon, 14 Feb 2022 11:26:19 +0100 Subject: [profanity] XEP-0453: DOAP usage in XMPP In-Reply-To: <20220214060406.vg2c44ywupv44wfw@posteo.de> References: <20220214060406.vg2c44ywupv44wfw@posteo.de> Message-ID: <5bd859e236a3df55c29d996411bc85a4@iodoru.org> > find attached a first version of a doap file. Is there somebody > how can check and maintain this file for profanity? Since I maintain already the xeps.hml I'll update the information as well. PRs and a second pair of eyes always welcome. > For the most XEPs I added 'partial' as status. We should check > the status and add a note. I am tracking the status of the XEPs at: https://profanity-im.github.io/xeps.html For myself and the users. Georg told me several months ago about the doap file but I didn't get around to creating one. So I'm happy that you did this! Did you take the information from the page I linked or will I have to double check? Also you forgot to mention: - Why you add this (explanation for what the doap file does, in the commit) - Where you want to add this (how it works, where it is expected to be hosted so that people find it. afaik root of website?) As always: easiest is a pull request so future generations could see all of this. From mwuttke97 at posteo.de Fri Apr 1 21:21:27 2022 From: mwuttke97 at posteo.de (Maxi Wuttke) Date: Fri, 1 Apr 2022 19:21:27 +0000 Subject: [profanity] [PATCH] Fix segfault in /upload and /download Message-ID: Please find attached a patch that fixes a segfault introduced in 3a86b8c29b1ccff7383478e980a7edf3aec3979a. How to reproduce the bug: - Upload a file or download a file using the /upload or /download commands The patch also includes a commit that includes a missing header. -------------- next part -------------- A non-text attachment was scrubbed... Name: fix_http_tls_segfault.patch Type: text/x-patch Size: 2250 bytes Desc: not available URL: From mwuttke97 at posteo.de Sat Apr 2 10:43:36 2022 From: mwuttke97 at posteo.de (Maxi Wuttke) Date: Sat, 2 Apr 2022 08:43:36 +0000 Subject: [profanity] [PATCH] Fix segfault in /upload and /download Message-ID: <35aa61d6-a92b-e621-908f-73f5937049b2@posteo.de> Please find attached a patch that fixes a segfault introduced in 3a86b8c29b1ccff7383478e980a7edf3aec3979a. How to reproduce the bug: - Download or upload a file using the `/url save` or `/sendfile` commands - Segfault happens: `strcmp` called with `null` parameter The patch also includes a commit that includes a missing header. -------------- next part -------------- A non-text attachment was scrubbed... Name: fix_http_tls_segfault.patch Type: text/x-patch Size: 2250 bytes Desc: not available URL: From toogley at nixnet.email Fri Apr 15 13:31:10 2022 From: toogley at nixnet.email (toogley at nixnet.email) Date: Fri, 15 Apr 2022 07:31:10 -0400 Subject: [profanity] OMEMO and disco In-Reply-To: <20210912121939.agohv3kqh35lcv5r@debxwoody.de> Message-ID: Hello, please, when you send patches can you send them inline and add PATCH to your subject so that we know your email contains a patch? Ideally, you would use standard tools for that, for instance git send-email. See for instance: https://git-send-email.io/ Much easier to work with compared to attachments. Thanks.