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: Mon, 6 Aug 2018 07:52:04 -0700 (PDT) Message-ID: <8476cec3-45ab-486b-854b-fe045fbff902@default> 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>> <39939ea5-a7c2-400a-9ac1-4df7cf4fcb42@default> <871sbbrk9m.fsf@gmx.de> 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 1533567549 29592 195.159.176.226 (6 Aug 2018 14:59:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 6 Aug 2018 14:59:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: Michael Albinus , Howard Melman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 06 16:59:05 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 1fmgyP-0007bG-Cn for ged-emacs-devel@m.gmane.org; Mon, 06 Aug 2018 16:59:05 +0200 Original-Received: from localhost ([::1]:34503 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fmh0V-0003Wp-Tf for ged-emacs-devel@m.gmane.org; Mon, 06 Aug 2018 11:01:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40238) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fmgrr-0003pI-R4 for emacs-devel@gnu.org; Mon, 06 Aug 2018 10:52:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fmgrm-00075a-VN for emacs-devel@gnu.org; Mon, 06 Aug 2018 10:52:19 -0400 Original-Received: from aserp2130.oracle.com ([141.146.126.79]:42934) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fmgrm-00074a-KO for emacs-devel@gnu.org; Mon, 06 Aug 2018 10:52:14 -0400 Original-Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w76EmiUV070515; Mon, 6 Aug 2018 14:52:06 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=xD4/6EyK2X69dxq+38GsPOe6s1b1Jb+K2JaZwu/cTbs=; b=pG2HTxrCMBhZlKFNLy5HSsoWLGIsCnJCFrT94cTyVNs4uZy1OzFXnsAkRNcJrrlai7AJ Ofl8As6YNr4bv35MQHC3hfJdp9wpZEOqMqxUU6/SGFCa1NWYsATyToLJuFn8z0wm6I/I cLKxzy+cVWFor8pf91Pdr4UVTnLvij5s4DikUc0SppDSlFC3KHwRLA54MnyEWOj/S/TP 7Jlc/jF76hv/e+Ud8j9R+sXHUCk/xpBlhEQa6dEd0zcphxR4YwdPKDI3tb7QN5ucmflu JLJLeiQX9dCj0iaEsdnO0W1TAUy5yW22l3RTZZnfr043ZHzUNjWkeEE0gVtq3roy685P 1Q== Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp2130.oracle.com with ESMTP id 2kn1ncwcf6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 06 Aug 2018 14:52:06 +0000 Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w76Eq5r7013675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 6 Aug 2018 14:52:05 GMT Original-Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w76Eq4KJ019555; Mon, 6 Aug 2018 14:52:05 GMT In-Reply-To: <871sbbrk9m.fsf@gmx.de> 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=8976 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808060156 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 141.146.126.79 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:228215 Archived-At: > > My sense is that the proposed C-x & is a prefix, because it > > is used before another key sequence. It is not an argument > > because it doesn't affect the functions' argument list the > > way C-u does. >=20 > I'd agree with this. What is it a prefix of? A prefix is part of what it is a prefix of. > > Maybe the term should be "prefix sequence"? Sequence of what? > I like this proposal. "Prefix key sequence" would be more precise, but > it doesn't read fluid. If there isn't any objection over the next week, > I'll apply your wording. Please don't. This is _not_ a prefix key. A key is a key sequence. A prefix key is a key = sequence that is a prefix of a larger key sequence. But in Emacs a prefix k= ey also has the specific meaning of a key sequence that is bound to a keyma= p. `C-x &' is not bound to a keymap, and is thus not a prefix key (sequence= ). Until and unless we really do decide to baptize this and document it, pleas= e just what RMS suggested: don't call it anything. Certainly please do not = call it just a "prefix" or a "prefix key (sequence)". > > Wasn't there are a proposal at one point to do something > > similar for C-x 4 and C-x 5 so that there didn't have to be > > -other-window and -other-frame variants of so many > > commands? >=20 > I'm not aware of such a proposal (which only means that my memory is > bad), but it makes sense. I believe he's thinking of Stefan's wish to have prefix keys `C-x 4' and `C= -x 5' work automatically, without defining separate other-window and other-= frame commands. That's something completely different. Let's please not let= this thread wander farther than it already has.