all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Andreas Schwab <schwab@linux-m68k.org>,
	emacs-devel@gnu.org
Subject: Re: bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus
Date: Thu, 02 Apr 2020 13:10:37 +0200	[thread overview]
Message-ID: <871rp6nnwy.fsf@gnus.org> (raw)
In-Reply-To: <m2d08s1p0p.fsf@gmail.com> (Robert Pluim's message of "Tue, 31 Mar 2020 18:13:10 +0200")

Robert Pluim <rpluim@gmail.com> writes:

> Now that Iʼve actually tested it, the change looks like this, making
> make-network-process and make-serial process behave the same as
> make-process and make-pipe-process. Iʼve looked at all uses of those
> two functions in Emacs' sources, and none of them depend on the change
> in semantics, in fact only a couple of them actually pass a :coding
> keyword.
>
> Having said all that, this does go back a looooong way (2002 at
> least), so maybe we want to let sleeping dogs lie.

Yeah, it does sound slightly scary, but I think the current nil
behaviour for :coding is probably not something any code would rely
on...  I'm not quite sure what `nil' semantics for :coding here would
signify?

On the other hand, I generally think that functions should respect their
parameters, so if you say :coding nil, it might then be somewhat
surprising that `coding-system-for-{read,write}' are used instead?

So I'm not quite sure that the current make-network-process behaviour
here is a bug.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  parent reply	other threads:[~2020-04-02 11:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 23:07 bug#40248: 27.0.90; Failure open .authinfo.gpg from Gnus Juan José García Ripoll
2020-03-27  8:18 ` Eli Zaretskii
2020-03-27 13:34   ` Eli Zaretskii
2020-03-27 16:21     ` Juan José García-Ripoll
2020-03-28  7:55       ` Eli Zaretskii
2020-03-28  8:40         ` Lars Ingebrigtsen
2020-03-28  9:17           ` Eli Zaretskii
2020-03-29  7:45             ` Lars Ingebrigtsen
2020-03-29 13:49               ` Eli Zaretskii
2020-03-31  9:20                 ` Robert Pluim
2020-03-31  9:53                   ` Andreas Schwab
2020-03-31 10:16                     ` Robert Pluim
2020-03-31 10:31                       ` Andreas Schwab
2020-03-31 11:09                         ` Robert Pluim
2020-03-31 16:13                           ` Robert Pluim
2020-03-31 17:59                             ` Eli Zaretskii
2020-03-31 19:53                               ` Robert Pluim
2020-04-02 11:10                             ` Lars Ingebrigtsen [this message]
2020-04-02 12:48                               ` Robert Pluim
2020-04-03 11:52                                 ` Lars Ingebrigtsen
2020-04-03 12:50                                   ` Robert Pluim
2020-03-28 14:03         ` Juan Jose Garcia Ripoll
2020-03-28 14:36           ` Eli Zaretskii
2020-03-29  7:48         ` Lars Ingebrigtsen
2020-03-29 13:52           ` Eli Zaretskii
2020-03-30  9:37             ` Robert Pluim
2020-03-30 13:10               ` Eli Zaretskii
2020-03-30 14:10                 ` Robert Pluim
2020-03-30 14:33                   ` Eli Zaretskii
2020-04-02 11:11                     ` Lars Ingebrigtsen
2020-04-03 11:31                       ` Eli Zaretskii
2020-04-03 11:43                         ` Robert Pluim
2020-07-19  2:45                           ` Lars Ingebrigtsen
2020-07-19 14:23                             ` Eli Zaretskii
2020-07-19 14:29                               ` Lars Ingebrigtsen
2020-07-19 14:43                                 ` Eli Zaretskii
2020-07-19 14:45                                   ` Lars Ingebrigtsen
2020-07-23  0:20                                   ` Juri Linkov
2020-07-23 13:36                                     ` Dmitry Gutov
2020-07-20  8:42                               ` Robert Pluim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rp6nnwy.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.