From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id YPQOLm2fPWQIHgAASxT56A (envelope-from ) for ; Mon, 17 Apr 2023 21:35:09 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id ICIdLW2fPWRFgwAAG6o9tA (envelope-from ) for ; Mon, 17 Apr 2023 21:35:09 +0200 Received: from mail.notmuchmail.org (yantan.tethera.net [135.181.149.255]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 00E9A3B548 for ; Mon, 17 Apr 2023 21:35:09 +0200 (CEST) Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 2FE545F386; Mon, 17 Apr 2023 19:35:06 +0000 (UTC) X-Greylist: delayed 59824 seconds by postgrey-1.36 at yantan; Mon, 17 Apr 2023 19:35:02 UTC Received: from ra.horus-it.com (ra.horus-it.com [IPv6:2a01:4f9:6a:528d::a]) by mail.notmuchmail.org (Postfix) with ESMTPS id C27865F35B for ; Mon, 17 Apr 2023 19:35:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by ra.horus-it.com (Postfix) with ESMTP id 7169FBE0060 for ; Mon, 17 Apr 2023 21:35:01 +0200 (CEST) X-Virus-Scanned: at horus-it.com Received: from ra (ra.horus-it.com [IPv6:2a01:4f9:6a:528d::a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) by ra.horus-it.com (Postfix) with ESMTPS id 42B14BE0028 for ; Mon, 17 Apr 2023 21:35:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ml.seichter.de; s=k22; t=1681760101; bh=0IcyRE2SoKBpoUViufpghCIoQOiQESqLrp7VJW6bLHI=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: Content-Type; b=VYYXYK1l5exrAPcJYEsnYrp6X69eH+8MvJRhK6ej3d+KzfBEGREuevMV18A/jOGRH guk6EtG38/0eZBHXi0YydTPBhhjTW8G0c6X1BkTv7sJwLRg02/K9Nd58EUR0ALB5V4 oWkf3VC6TiGfeaYyTthZWeNiZaenUvIQPzu0HCwGw1V/GNGeCsPVsZJSdNDkelsP0S 5Xv46YcyXTAn7TELMQ/+d5kGq8QDxGCxsy7hPO5WQNyTUSBavHLlphK6X/7u4C9QPQ cousYjC/AQLX9lC4SoSTqHhahDKEcvjZOvpY2VdlOMwjDv23l5BGI0cwQmYIC4Thzw O9ctugR5ecznQ== From: Ralph Seichter To: notmuch@notmuchmail.org Subject: Re: Recommended method to pair Notmuch with Neovim? In-Reply-To: <643d3e7389719_751a294db@chronos.notmuch> References: <87h6tfjjuy.fsf@ra.horus-it.com> <643d3e7389719_751a294db@chronos.notmuch> Mail-Followup-To: notmuch@notmuchmail.org Date: Mon, 17 Apr 2023 21:35:01 +0200 Message-ID: <87jzyab8uy.fsf@ra.horus-it.com> MIME-Version: 1.0 Message-ID-Hash: KBITPZPM2BMADOKOIV2OL33F6WJG6DQC X-Message-ID-Hash: KBITPZPM2BMADOKOIV2OL33F6WJG6DQC X-MailFrom: ralph@ml.seichter.de X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Country: DE X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1681760109; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=vdLy1R8M5TW22NiEj2tH9hNKOYpPojRULhT2YXHVbW4=; b=oXZ45OV0yw16AwVvHr8WBr0MBw480s0A+J2hifB40IjbdBwoR5E8o1rgGyr+Mo6FUjg7yD JhGYLuRhgmDKxZwfYDiNYdVGZTN1qezskwqqBORTouFsnbcib7zEFkrbnM41VQAw9LM6Bi Xp5PeELZwccrRuSHSi/ilbiNx6oRV3EwhsHUmlZ/Es6HXHqGTUdheuTz+xwQnX+K6xoENB /z+NDTvfD20yNQkmTKDkP5yNlha2grNXv1lM2wFBUyrawGmyvGO2dm8vkyHqXrv98bPRfJ Lo5JVrqwviws0xiReRCGrxVm/hP7SQMu/mIfGCqAArS3psF+xD5F0HCkAxPJuA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=ml.seichter.de header.s=k22 header.b=VYYXYK1l; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org; dmarc=fail reason="SPF not aligned (relaxed)" header.from=ml.seichter.de (policy=none) ARC-Seal: i=1; s=key1; d=yhetil.org; t=1681760109; a=rsa-sha256; cv=none; b=q5Mx7CK6nU3Sbmr3yUcdztxA7czJCV4jBS0aSUpICew0JcxxiXr1Sqp5ZdSShBPps/J9P8 ozZJy06C01CM62Bj9hunnoRwbqJ/oleQtYXQ7juW91DhL5QBRkoE5Vcb1+kBV5O6w36RT5 L5QVKjwsCytEfrJn+16NnfNpc0Qj/o7MY1rRJHH3uLIexBHDmxD9hYOVuU3DuoptlmdzOn bIFd3jVVCQP8Itzvc7qD1ZPZ0chv4aYCZXAossCbbQSU3mEOmmx7WyAC3bzkLKX72NyQ6G xQEmPZuBVGChLXB2eGuQK1GZX6rb94zMxqXJDQaYBu/UskTmdZw/+116HG691w== Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=ml.seichter.de header.s=k22 header.b=VYYXYK1l; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org; dmarc=fail reason="SPF not aligned (relaxed)" header.from=ml.seichter.de (policy=none) X-Migadu-Spam-Score: -0.21 X-Spam-Score: -0.21 X-Migadu-Queue-Id: 00E9A3B548 X-Migadu-Scanner: scn1.migadu.com X-TUID: msUzxXHfjvcN * Felipe Contreras: > There hasn't been any development because to be frank it just works. I did not mean to imply that "no repository changes" is necessarily a bad thing. However, Neovim being quite volatile, I intuitively expected some form of development for notmuch-vim being necessary to keep things working. > I've also started to rewrite it from scratch because a lot of it I > think can be done in a much simpler way, but that doesn't really > affect the users, it's just the maintenance of the code. That tells me you are still invested in the subject, which is a welcome thing to read. > I tried notmuch-vim on neovim with ruby support some time ago and it > worked fine. I think there was some issue with slowness, but they > fixed it. I don't really remember. I set up a virtual Ubuntu 22.04 Server with Notmuch for testing, and managed to get Ruby 3 support for Neovim [1] working. I then used your plugin via the "Lazy" package manager for Neovim. Some of the basics work. Navigating and searching look OK, but I have yet to manage to send email. So far, message bodies are always missing, so it is not usable yet. Neovim keeps reporting tons of errors when I try to compose and send email, and I have not yet delved deeper. [1] https://github.com/neovim/neovim-ruby > One alternative that I considered is to rewrite notmuch-vim in lua, > but that would probably require some libnotmuch bindings for lua, > which would take considerable amount of time to write. And that would > only work for neovim, not vim. >From what I understand, Vim 9 introduces a new, proprietary scripting language, while Neovim uses LUA? That seems to foreshadow lots of work if one wishes to provide plugins that work with both editors. > It might be better to just keep using ruby. It's a fantastic language, > there's already pretty good bindings for libnotmuch, and it works for > both vim and neovim. Ruby may be a worthwhile language, but in this particular scenario of Neovim and Notmuch, I see the end user's perspective: I don't need Ruby to run anything but notmuch-vim, so I don't want to install Ruby on various systems if it can be avoided. I'll do it if there is no alternative, but LUA sure sounds better than Ruby to me. Selfish, I know. ;-) > I think you should just give it a try. I began my experiments, but as stated above, I ran into issues that I have yet to figure out. Thank you for your response and for your plugin, Felipe. -Ralph