From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Mon, 13 May 2019 17:48:42 +0300 Message-ID: <835zqebeb9.fsf@gnu.org> References: <1552789070.5272.1@yandex.ru> <87imwhmmt8.fsf@gmail.com> <87y347g1l3.fsf@iotcl.com> <9ac21e82-8e47-f9b5-f88d-23c0c56946d1@yandex.ru> <87pnpc1lby.fsf@iotcl.com> <83zhoezdqc.fsf@gnu.org> <87imuivfcr.fsf@iotcl.com> <83k1eyfxls.fsf@gnu.org> <3b8e2195-07c0-a240-6164-8d34bcca344f@yandex.ru> <83ftpmfp0y.fsf@gnu.org> <838svefl3p.fsf@gnu.org> <658fcd11-dfad-2060-c84b-5da938d506b7@yandex.ru> <83woiydorm.fsf@gnu.org> <245d6dae-847a-3d9e-869b-5f8a2d9a74f0@yandex.ru> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="179460"; mail-complaints-to="usenet@blaine.gmane.org" Cc: toon@iotcl.com, monnier@iro.umontreal.ca, agrambot@gmail.com, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 13 16:59:34 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQCQO-000kVn-9G for ged-emacs-devel@m.gmane.org; Mon, 13 May 2019 16:59:32 +0200 Original-Received: from localhost ([127.0.0.1]:58714 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQCQN-0001RZ-9p for ged-emacs-devel@m.gmane.org; Mon, 13 May 2019 10:59:31 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:45420) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQCQ7-0001Fn-7T for emacs-devel@gnu.org; Mon, 13 May 2019 10:59:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45873) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQCGC-0001M1-PL; Mon, 13 May 2019 10:49:00 -0400 Original-Received: from [176.228.60.248] (port=3836 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hQCGB-0007Db-To; Mon, 13 May 2019 10:49:00 -0400 In-reply-to: <245d6dae-847a-3d9e-869b-5f8a2d9a74f0@yandex.ru> (message from Dmitry Gutov on Mon, 13 May 2019 04:43:00 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236464 Archived-At: > Cc: toon@iotcl.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, > agrambot@gmail.com > From: Dmitry Gutov > Date: Mon, 13 May 2019 04:43:00 +0300 > > On 10.05.2019 23:43, Eli Zaretskii wrote: > > >>> Yes, my point was that having to work via a Web browser will need to > >>> switch frequently between it and Emacs. Which is an annoyance, to say > >>> the least. > >> > >> I can believe that, even if I don't really understand it. > > > > Let me try to explain. > > Before I reply to the rest, I'd like to clarify: my surprise was at the > declared difficulty of switching between the web browser and Emacs. Not "difficulty", "annoyance". Quite a different thing, I'd say. You want me to copy/paste the text to Emacs, edit there, then copy/paste back? The switch itself is the least of the problems. > Out of these, I still use Emacs for more or less everything but abbrevs > and word completion. IOW, for everything except writing prose, and I > still might copy-paste some snippets of code or text between it and the > web browser or the email client. > > Writing text in something other than Emacs is not particularly > enjoyable, but turns out, certain kinds of text are > fetched/rendered/displayed better in other tools. And you generally have > to edit the said kinds of text in the same tools that you're reading > them in. In particular, after a few years of trying Gnus for email, I > went back to Thunderbird, losing with that all the benefits of > everything-inside-Emacs email workflow. So the use of web browser > doesn't make it worse (and makes certain other things better). That's you, not me. (And I don't use Gnus, either; Emacs has more than a single email client to offer.) > > Instead, GitLab wants me to use the Web browser for most of these. > > As per above, I disagree. So for you the Emacs solution will not be needed. But there are enough of those who'd want it. > > This means the Web browser now becomes a very important program for > > me, I need to start learning it much more than I bothered until now, I > > need to keep it updated at all times, I need to customize it (more > > things to learn and try), etc. > > That is true, of course. Alas, the contemporary Internet makes browsers > quite indispensable. Not in my workflows. I use it quite rarely, and generally not for working on code (except when I need to consult documentation, or find a solution to some problem I bump into). > >> Here's also the same information on the API level: > >> https://docs.gitlab.com/ee/api/notification_settings.html > > > > Where is each value described? The names are not descriptive enough, > > and I couldn't find any details about them. Did I miss something? > > You can search the documentation Granted, I already did. And came up empty-handed. > or ask. I think (as a person familiar with GitLab) that all names > are quite descriptive. Well, perhaps then you could explain these to me: . the "mention" level . the "global" level . from the "custom" level: - issue_due - push_to_merge_request and merge_merge_request > > I never needed to set up any filters. Never. It sounds very wrong to > > me that I need to set up a filter to defend myself against my own > > project. > > Well, I routinely get duplicate emails because I'm both subscribed to > emacs-devel and the bug tracker, and also get Cc'd. I ignore that, but > some people suggested technical solutions. This is standard in almost all mailing lists, and easy to ignore.