Hi Mike As tools I use ripgrep and fzf for effective fuzzy finding. As plugins, the most important ones I use are: - for LSP support and code completion: neovim/nvim-lspconfig, hrsh7th/nvim-cmp and a bunch of hrsh7th/cmp-* ones - fzf integration: junegunn/fzf, ibhagwan/fzf-lua (way better and faster than telescope for my use case) - for MRU: pbogut/fzf-mru.vim - for file navigation: nvim-tree - and a few classic Tim Pope's one: tpope/vim-abolish, tpope/vim-surround, tpope/vim-unimpaired, tpope/vim-fugitive, tpope/vim-repeat I have a few more but the ones above are the key ones, especially the integration with fzf and ripgrep. I have yet to setup treesitter integration, it's one of the things I keep postponing. On top of that, I have a number of CLI command aliases and scripts that makes interaction with git and TGW and navigating the TDE code a breeze (fzf is once again a dark horse). You will develop your own as you go along, it's a never ending refining process :-) Instead of tmux, I have 2 groups of 10 konsole tabs on two desktops. Ctrl+n switch tab, Ctrl+Fn switch desktop, so changing workspace is again a breeze. Many of those tabs have specific usage, so everything I need is always under my finger. Lastly, I heavily remapped my keyboard, that gives extra speed, but I would say you don't need to bother with that at the beginning. That is really subjective. Issues on TGW and bugs in the older bugzilla can inspire you to try something or provide some ideas, but also may get you lost in troubleshooting an issue which is not very clear. Personally I started with a small GUI enhancement that was important to me, that is middle click on a Kate tab bar button to close the file. So I would suggest you find something that bothers you (a bug, a missing feature...) and work on that. If it is something that you need, it will give you extra motivation when you will inevitably hit some obstacle along the way. Another little piece of advice: don't start with Konqueror. It is a huge beast, you would most likely get lost among all its internals. Start from smaller standalone applications, it will be a smoother experience. Kate is fairly big too, I started on the Kate tabbar plugin. Of course, YMMV depending on current experience and knowledge. Hope it helps :-) Cheers Michele

Hi Mike, I have seen this with vanilly neovim config, I get it every time I fire up a quick VM for testing. It's a matter of config, although I don't recall which option it is. Maybe a quick google search with give you the answer. No worries, when you are ready. Anyway we don't use a lot of C++, just the basic. I like to call it "C with classes" as it used to be called initially :-) A lot of modern stuff is not use. Btw, TDE use c++11 standard, so anything newer than that is not officially supported. Well, there are plenty of ways to help. - translations, but for this task users are probably already doing great thanks to TWTW - documentation updates: either for applications or website/wiki - there is a long standing task that was to get the wiki to use the same color theme as the main website. It is something that was left over when we redesigned the site about 10 years ago. Maybe you can exchange some ideas with E.Liddell, who did the original work. Another good way to contribute "chore" tasks and at the same time get you familiar with the building process, is to hunt for warnings in building logs and fix them. We have quite a bit of them, many are probably simple to fix. This will give you a change to build packages, make small changes and get familiar with the overall dev process. Just an idea, in the end it is still a chore task, but it would help to provide cleaner code. Reach out on the dev IRC chat on libera, easier to discuss there I guess. The chat is logged, so you can leave comments and I can comment back later if I am not online. Cheers Michele