From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: New Package for NonGNU-ELPA: clojure-ts-mode Date: Fri, 1 Sep 2023 17:21:50 +0300 Message-ID: References: <87il9kksqz.fsf@dfreeman.email> <87o7j99304.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> <50c351cf-4c7b-5497-a561-ba1b9f63d1c8@gutov.dev> <83ledqatmt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13083"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: yantar92@posteo.net, jschmidt4gnu@vodafonemail.de, philipk@posteo.net, luangruo@yahoo.com, stefankangas@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 01 16:22:44 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 1qc52p-00039v-MU for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Sep 2023 16:22:44 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qc52B-0007uK-NA; Fri, 01 Sep 2023 10:22:03 -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 1qc528-0007pn-JH for emacs-devel@gnu.org; Fri, 01 Sep 2023 10:22:01 -0400 Original-Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qc525-0002pT-KK; Fri, 01 Sep 2023 10:22:00 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 5F29432005BC; Fri, 1 Sep 2023 10:21:55 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 01 Sep 2023 10:21:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1693578114; x=1693664514; bh=aeZam3D0sEy6egK9D9YLEoS5EW2N5m+KwnM HvnfyORk=; b=djbQLVMNk2BkqGcqrEZnncc2Q8BqRVM7iLcySEqRwStzymsfU8e JyJSVfWRNG+Hc3Vorng7U3eIgE+VtYBh1tSOWp3mzTt43crXVBXzQQG5mLeN93mw W3xLX/Hycsu9WsMZjD29shpUhNc7u8L4gJbPLee3TeIlkBq9bOsW5H7jEQicDWW1 b5Rm/jyYBqk9EAq21Md/oe8dF7kMyqG3ARNetopriJjZFJVxk0omjsA3WCniqm+9 3sTCEOQOpZzzC04EsKCwh5v7mCYaHEnXWTMWt5ieASYGcy9YOCpxM4hFlA2o2QTQ 4DfN2KxBUGxhjOfwS6WkwohmVHQrlkH2+rA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1693578114; x=1693664514; bh=aeZam3D0sEy6egK9D9YLEoS5EW2N5m+KwnM HvnfyORk=; b=xLqLrVsE80/9a3HzDmCM3AfYmYAekhZXJ7lMr9pfCPkJFtRhzLf OmsUG9q0yPDhaW81jjHVbRgiMLroFBvATy9sNfgseOCXZybefB3TLqw9vC7PflA8 y/rIXkerYuxxRwaEM3vy6VhUKkfGlAVxTHQt/JlaH2dTY74EMj63EThlN+VDBtpS wgb5Igl4JIVY9cn6Rh0fuwkSG+03cYtVhKdq5U+JtlmjT2j8ayPlhvLi0wqEB5oh IkQJ3MFDQOUgExJZfZ519H5BUWZSsiZRUOqzD+A6y5RDrZYb3KmPTEwcbpI4UB7L i7YtapMgD6fd7L1NtQpScISyLcvmOEdLUdw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudegvddgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhepvdeuvddtteeiffeijedtfeduvefgveehfedtiefftdeuhfetieeuueejleej ieevnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpghhithhlrggsrdgtohhmnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepughmihhtrhih sehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 1 Sep 2023 10:21:52 -0400 (EDT) Content-Language: en-US In-Reply-To: <83ledqatmt.fsf@gnu.org> Received-SPF: pass client-ip=64.147.123.24; envelope-from=dmitry@gutov.dev; helo=wout1-smtp.messagingengine.com X-Spam_score_int: -62 X-Spam_score: -6.3 X-Spam_bar: ------ X-Spam_report: (-6.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-3.478, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:309800 Archived-At: On 01/09/2023 16:51, Eli Zaretskii wrote: >> Date: Fri, 1 Sep 2023 16:44:35 +0300 >> Cc:jschmidt4gnu@vodafonemail.de,philipk@posteo.net,luangruo@yahoo.com, >> stefankangas@gmail.com,emacs-devel@gnu.org >> From: Dmitry Gutov >> >> On 01/09/2023 16:16, Eli Zaretskii wrote: >>>> 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? >> Very consistent: people who find using a MUA in complex ways difficult >> don't set up additional filtering and usually don't complain about it >> (the default volume of notifications usually seems fine for me, for >> example). >> >> What's odd is when people who know how to set up MUA filters and >> everything produce such complaints. > Such responses make me wish I never participated in this discussion. No need to be rude. You judged some other people's workflows by your own standards and got an answer that when participating in those workflows it's entirely feasible to improve them to your liking using the tools you are certainly familiar with (and not just you, but every old-timer with a customizable MUA). I got that answer every time when pointing difficulty managing the email-driven workflow here (I only have a moderately-customizable MUA, however). And that those other people (ones with web-based workflows) are largely unbothered by their experience, possibly due to not knowing better alternatives (but that very debatable). But they can also customize their notification a little if they're using Github, and a lot, if they're using Gitlab. There is a dedicated section in Github's docs about filtering on the level of MUA: https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#filtering-email-notifications, though for some reasons they don't mention the available headers X-Github-Reason and X-Github-Sender. What is missing here? Re. using Gitlab I already said I'd try to look into settings for filtering emails, if we ever reach the stage of experimenting with it when it becomes relevant. There existing controls listed are here, and there are a lot (perhaps they extended that feature over the several years since we last looked): https://docs.gitlab.com/ee/user/profile/notifications.html#notification-events-on-issues-merge-requests-and-epics