From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: New Package for NonGNU-ELPA: clojure-ts-mode Date: Fri, 01 Sep 2023 16:48:24 +0300 Message-ID: <83o7imatsn.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <97224c4f-fad4-ae01-46c1-5755d97d9a92@gutov.dev> <87fs3ztq38.fsf@localhost> <87cyz3qwba.fsf@posteo.net> <8734zztmiz.fsf@localhost> <87sf7zqs3l.fsf@yahoo.com> <87il8vs6e7.fsf@localhost> <87jztbqrc9.fsf@yahoo.com> <877cpbs5a0.fsf@localhost> <87fs3zqqgj.fsf@yahoo.com> <874jkfs4o0.fsf@localhost> <87y1hroz47.fsf@posteo.net> <83cyz2ctp0.fsf@gnu.org> <87msy6rzeg.fsf@localhost> <83wmxab0ym.fsf@gnu.org> <87v8cuqg8d.fsf@localhost> <83ttseava1.fsf@gnu.org> <87zg26hvfq.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2421"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dmitry@gutov.dev, jschmidt4gnu@vodafonemail.de, philipk@posteo.net, luangruo@yahoo.com, stefankangas@gmail.com, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 01 15:49:32 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qc4Wi-0000Ol-DP for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Sep 2023 15:49:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qc4Vy-00030E-KV; Fri, 01 Sep 2023 09:48:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qc4Vv-0002yV-3U for emacs-devel@gnu.org; Fri, 01 Sep 2023 09:48:43 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qc4Vs-000372-SZ; Fri, 01 Sep 2023 09:48:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Ufqc6DHOrx4ptUatBJcWkiR8FKxLWYMdL+TgW5vlypw=; b=WdTwZ8sJk1uu QuiPuLKWVkPrOxk3k80sIMaEM+Axj9h85rUAosVfgskiHsH8TuJYKhC6xeAhaZlFfo3iBAIxCE8iQ hcW9jZpxKGIyK1aiJWjDU5zoaMRJle44qHQxpOKOtytlScOZGmpgB8z6Z9Zc1WbJeVmYjI8FsxBQj lseY+r4xjewEWc2cZc1oln/DIdgTvazYp0J4imZI7YCZVqaPTiTTYXehdcJTltmV+B49O9mGckUJd l6C8Ekksqa+vsvraY4BoPgfI7w8t8NLoCe9PmHN0/LVKqc5WgEZFEjh01RMZU32lQf/ZrAoIpYp2C ne+8In4lnGZeVw3IrKWzzw==; In-Reply-To: <87zg26hvfq.fsf@localhost> (message from Ihor Radchenko on Fri, 01 Sep 2023 13:31:05 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309790 Archived-At: > From: Ihor Radchenko > Cc: dmitry@gutov.dev, jschmidt4gnu@vodafonemail.de, philipk@posteo.net, > luangruo@yahoo.com, stefankangas@gmail.com, emacs-devel@gnu.org > Date: Fri, 01 Sep 2023 13:31:05 +0000 > > Eli Zaretskii writes: > > >> I can turn them off selectively in my MUA. > >> IMHO, this is not any different from how I approach mailing lists - most > >> of the discussions on ML are not interesting to me and I simply filter > >> them out. I think Gnus scoring is relevant (although I use different > >> approach). > > > > How is this consistent with complaints about the difficulties of using > > a MUA in sophisticated ways? > > This branch started from your claim that in order to use GitHub one > needs to check each repo manually: > > > What I'm trying to say here is: Email might look like it's easy to use, > > but in the context of a mailing list it's not necessarily so, even from > > the technical side. These text entry boxes on Github et al. definitely > > feel easier and more inviting to use. > Yes, but the cost is that you need to proactively to visit each and > every GitHub repository to see whether something new was posted in the > > But it is not, and email workflow (if one wants to use that kind of > workflow) is still viable. Are you actually using that with GitHub repositories? Because I do, and my comments about that are based on several years of doing it. It's extremely tedious, to say the least, and following a discussion is without visiting the corresponding issue in a Web browser is quite hard, IME. So please believe me when I say this is very annoying. > > Really? Just look at this discussion: each message clearly shows to > > what it responds by quoting that text. > > Check out https://github.com/radian-software/straight.el/issues/1107, > for example. Do you find it confusing? That's a Web page, not an email inbox. And yes, I'd find it hard to read due to very few quotes. And that discussion is unusual in how much people quote one another. But still, take a random message there: https://github.com/radian-software/straight.el/issues/1107#issuecomment-1670440497 It says "Should be fixed by #1109" without saying what is fixed. Or this post: https://github.com/radian-software/straight.el/issues/1107#issuecomment-1668343604 It begins with "The function in question is" and goes on to discussing code, without saying to which part of the discussion this refers. Imagine that you receive an email like that -- how do you know what is this about without re-reading the entire discussion? Of course, people can refrain from quoting in email messages as well. But my point is that when people use the Web UI, they can easily forget that someone might be reading their responses via email, without seeing the previous posts.