From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Introducing thread-safe Tramp Date: Sat, 28 Jul 2018 00:08:58 +0300 Message-ID: <83y3dwqtcl.fsf@gnu.org> References: <8736wa9c5s.fsf@gmx.de> <87wotkn6do.fsf@gmx.de> <874lgn8x6l.fsf@gmx.de> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1532725657 32736 195.159.176.226 (27 Jul 2018 21:07:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 27 Jul 2018 21:07:37 +0000 (UTC) Cc: michael.albinus@gmx.de, drew.adams@oracle.com, emacs-devel@gnu.org To: Filipp Gunbin Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 27 23:07:33 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 1fj9xT-0008P1-Sq for ged-emacs-devel@m.gmane.org; Fri, 27 Jul 2018 23:07:32 +0200 Original-Received: from localhost ([::1]:42993 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fj9za-0005BZ-Mm for ged-emacs-devel@m.gmane.org; Fri, 27 Jul 2018 17:09:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56720) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fj9yu-0005BJ-Is for emacs-devel@gnu.org; Fri, 27 Jul 2018 17:09:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fj9yr-0007do-Du for emacs-devel@gnu.org; Fri, 27 Jul 2018 17:09:00 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38765) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fj9yr-0007dk-B5; Fri, 27 Jul 2018 17:08:57 -0400 Original-Received: from [176.228.60.248] (port=3032 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fj9yq-0002ze-R4; Fri, 27 Jul 2018 17:08:57 -0400 In-reply-to: (message from Filipp Gunbin on Fri, 27 Jul 2018 22:04:04 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:227881 Archived-At: > From: Filipp Gunbin > Date: Fri, 27 Jul 2018 22:04:04 +0300 > Cc: Drew Adams , emacs-devel@gnu.org > > It feels like prefix arg should change the user-visible behaviour of > the command We never restrict the use of prefix argument only to some sort of changes. Besides, running a command asynchronously does change its user-visible behavior, and quite significantly so. > Maybe there could be rules for find-file to use async behavior by > default, like: > > - When a non-local method is explicitly used (that is, not /sudo) > > - When default-directory is on a remote host > > - When a file being visited is greater than some customizable size That's even worse, IMO. We will never be able to second-guess what users want, and they will want a fire escape even if we succeed in most cases. > - When a special command was given before (analogy with `C-x RET c' was > already mentioned here). "C-x RET c" runs universal-coding-system-argument, which is akin to prefix argument, only separate from it. I do agree that using a separate argument similar to "C-x RET c" is better, since it binds a variable to a value, like "C-x RET c" does.