From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.devel Subject: Re: bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus Date: Thu, 02 Apr 2020 14:48:05 +0200 Message-ID: References: <86bloi1zrj.fsf@csic.es> <83lfnm8b30.fsf@gnu.org> <83ftdt9b1d.fsf@gnu.org> <86sght3h1s.fsf@csic.es> <834ku89anf.fsf@gnu.org> <87a740ub2r.fsf@gnus.org> <83tv287s9j.fsf@gnu.org> <874ku7txho.fsf@gnus.org> <83imin5l0w.fsf@gnu.org> <87blocrgtb.fsf@igel.home> <877dz0rf2v.fsf@igel.home> <871rp6nnwy.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="78341"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Andreas Schwab , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 02 14:49:02 2020 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 1jJzHK-000KHp-12 for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Apr 2020 14:49:02 +0200 Original-Received: from localhost ([::1]:38120 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJzHJ-0007MO-2R for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Apr 2020 08:49:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34161) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJzGV-0006ch-22 for emacs-devel@gnu.org; Thu, 02 Apr 2020 08:48:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJzGT-0005JL-Rt for emacs-devel@gnu.org; Thu, 02 Apr 2020 08:48:10 -0400 Original-Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]:35859) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jJzGT-0005Il-K3; Thu, 02 Apr 2020 08:48:09 -0400 Original-Received: by mail-wm1-x32d.google.com with SMTP id d202so3536961wmd.1; Thu, 02 Apr 2020 05:48:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:gmane-reply-to-list:date:in-reply-to :message-id:mime-version:content-transfer-encoding; bh=JX4dDAvnmTfa7Rn5vCxgI3lW9XRkzS+mtx23dbMjOA0=; b=swJJuAQ29qSK+zILZTcdwaVnMGuZiUtWxG7SuNW6Su+6JyPhx1v07iBCU1QYo7Y021 7mq5B/QT4cn91oeAIZ3xT0+eBnyEUB+VUrvodffa/cj4xewKhtECUEPi8YxwiWAomRaL auHbSMeSSeAQzeUYxkP9BvKqiMdNRPdBH0wC4CfFfcAJirQjuHel+KkGAT5DxFWgPqEF +ozvzLf8JcJuxO+FMOqMMqMO+m5FOW383fVJYWgSFF9OPNtcB8359BkBPrWm4DRXRD6x 3+hHGxSK52DyZ0FMyyhrK0QmVzfmkr1M4amqxrCD5iOCdYmha3/TXT/Psl7KOsMcF0ID Hiww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references :gmane-reply-to-list:date:in-reply-to:message-id:mime-version :content-transfer-encoding; bh=JX4dDAvnmTfa7Rn5vCxgI3lW9XRkzS+mtx23dbMjOA0=; b=pOinwFtW+WuWVXEgdH5MRzyfYdNjyxe0N/4KYwogVaxbONR6Q78otguyuuD6IQfSF7 9MHmllDMyOe5oEzQ2pfzw0nc0GnsnG7lJaobnDGRenpoSTrEV9zlXdrd5kK9hsSFLGKI Aitb1y9nLa22waHfFJNKlJ30EMDPbWs8Yn2KWKc/GVfjPB11pgOYIz8g5HH2vJeLBqpx 6qY6KaYRWz+dh1R2iw7Nc2l+nsvxu+AihzZNvAl5j/BdzWIghpFag4eRsV5eT5vIgoie 3hSEUBsO/eFaWcX3CaEMz3Qu4xu2b2qNzqqBCzQ0ouzJL76mLbeC5UYK43yjF/lhVOno q38A== X-Gm-Message-State: AGi0PuZKxDD7gj6M/F8ejFW5TEVsHzhOBTEsTLLB/TXB+LtoicKo4sw7 yKPQIMi6VuPrAGh0s+RXCrSpRsM4 X-Google-Smtp-Source: APiQypIBVw7CO8CXmkemDDb32SCYPFNier0aM2D2y9r9I5C71otAud4/L8O7961ho9x3kwpacfi7mw== X-Received: by 2002:a1c:7308:: with SMTP id d8mr3467568wmb.31.1585831687775; Thu, 02 Apr 2020 05:48:07 -0700 (PDT) Original-Received: from rpluim-mac ([2a01:e34:ecfc:a860:30c1:b817:7653:c738]) by smtp.gmail.com with ESMTPSA id q13sm7777956wrg.21.2020.04.02.05.48.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Apr 2020 05:48:06 -0700 (PDT) Gmane-Reply-To-List: yes In-Reply-To: <871rp6nnwy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 02 Apr 2020 13:10:37 +0200") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::32d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:246253 Archived-At: >>>>> On Thu, 02 Apr 2020 13:10:37 +0200, Lars Ingebrigtsen said: Lars> Robert Pluim writes: >> Now that I=CA=BCve actually tested it, the change looks like this, m= aking >> make-network-process and make-serial process behave the same as >> make-process and make-pipe-process. I=CA=BCve looked at all uses of = those >> two functions in Emacs' sources, and none of them depend on the chan= ge >> in semantics, in fact only a couple of them actually pass a :coding >> keyword. >>=20 >> Having said all that, this does go back a looooong way (2002 at >> least), so maybe we want to let sleeping dogs lie. Lars> Yeah, it does sound slightly scary, but I think the current nil Lars> behaviour for :coding is probably not something any code would re= ly Lars> on... I'm not quite sure what `nil' semantics for :coding here w= ould Lars> signify? No code in Emacs that I could find relies on it. The new semantics would be 'use coding-system-for-read', which I think is defensible. Lars> On the other hand, I generally think that functions should respec= t their Lars> parameters, so if you say :coding nil, it might then be somewhat Lars> surprising that `coding-system-for-{read,write}' are used instead? Lars> So I'm not quite sure that the current make-network-process behav= iour Lars> here is a bug. It=CA=BCs different from make-process and make-pipe-process, it=CA=BCs undocumented, and it was surprising to both me and Andreas. If it turns out that in some obscure case somebody really needs the old behaviour, then binding coding-system-for-{read,write} will still be available, as will set-process-coding-sytem (or even passing :coding '(nil nil), but that=CA=BCs just evil :-) ) Robert