From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Introducing thread-safe Tramp Date: Sat, 4 Aug 2018 09:27:32 -0700 (PDT) Message-ID: References: <<8736wa9c5s.fsf@gmx.de> <87wotkn6do.fsf@gmx.de> > <<874lgn8x6l.fsf@gmx.de> > <<87sh44pisz.fsf@gmx.de> <87a7qbitc7.fsf@gmx.de>> < <878t5tdsfc.fsf@gmx.de>> <<83wotcpzub.fsf@gnu.org> <87bmaiuwml.fsf@gmx.de> <877el6uwio.fsf@gmx.de>> <<7c28f9d8-e2bb-4778-ab92-92707f12718f@default>> <<837el6t8r3.fsf@gnu.org>> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1533399984 4171 195.159.176.226 (4 Aug 2018 16:26:24 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 4 Aug 2018 16:26:24 +0000 (UTC) Cc: michael.albinus@gmx.de, fgunbin@fastmail.fm, emacs-devel@gnu.org To: Eli Zaretskii , Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 04 18:26:20 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1flzNh-0000uk-5d for ged-emacs-devel@m.gmane.org; Sat, 04 Aug 2018 18:26:18 +0200 Original-Received: from localhost ([::1]:55623 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1flzPn-0002b4-NN for ged-emacs-devel@m.gmane.org; Sat, 04 Aug 2018 12:28:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37814) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1flzPA-0002az-SU for emacs-devel@gnu.org; Sat, 04 Aug 2018 12:27:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1flzP9-00049V-UJ for emacs-devel@gnu.org; Sat, 04 Aug 2018 12:27:48 -0400 Original-Received: from userp2130.oracle.com ([156.151.31.86]:42034) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1flzP5-000449-AK; Sat, 04 Aug 2018 12:27:43 -0400 Original-Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w74GOvmq120485; Sat, 4 Aug 2018 16:27:36 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=87IvjCDJAtpcjTmA0DtBLnABu2siLKaJlkdWy3ZEfUQ=; b=0Ynz4xjYLglkWHnP8adUMen3EK4EFklzQvLDD/C0IkvhVbL5vg9OZytA3QKxb1hjdEwX 9jTIrEHKNDXr88bidRa6jbydy+5Gw65UdWKcc4+3Y2VWL4ZCO+T7m08lrKytjwMZBDhe sxRWr+G1GXUuKWgckHUFveZBQ2l3iXBPno72girIWfsNpcxkAlnVxXfZ4/q5WG/HNXCw hxriRRilzGZiU6CxOYZ3Kv6Gdm7fBFkIJF+fW8dF/hRJk0o6ZlD0K3KHrQXELgPKh0XG oXdV5HHVfEXHuR9DlqA6d114PdgFzOutdjaf2USEte9krI1nT2chVbNh0jczKwm0/C0t rg== Original-Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp2130.oracle.com with ESMTP id 2kn3jss21t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 04 Aug 2018 16:27:36 +0000 Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w74GRZK2008281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 4 Aug 2018 16:27:35 GMT Original-Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w74GRYNW031357; Sat, 4 Aug 2018 16:27:34 GMT In-Reply-To: <<837el6t8r3.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4717.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8975 signatures=668707 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=18 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=817 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808040181 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 156.151.31.86 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:228167 Archived-At: > > I don't really think we should call `C-x &' here a "prefix argument", i= n any > case. >=20 > It follows the example of "C-x RET c", which runs > universal-coding-system-argument. So I see nothing wrong with the > name: we have precedence. >=20 > Or is that the "prefix" part that bothers you? I see nothing in any of the doc (doc string, Emacs manual, Elisp manual) wh= ere we talk about `C-x RET c' being a "prefix argument". And we should not,= IMO. It has nothing to do with a prefix argument, except that it reads a k= ey sequence and handles reading a prefix argument in doing that. It certain= ly is not a prefix argument for the command it is bound to, nor does it pro= vide a prefix arg for the command it is bound to. Even `C-u' (`universal-argument') is not a prefix argument. It is a command= that begins reading a prefix argument and that, possibly together with oth= er commands (such as `digit-argument') provides that prefix argument to a f= ollowup command.