From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Documenting universal-async-argument Date: Tue, 07 Aug 2018 18:41:14 +0200 Message-ID: <87tvo6t9hx.fsf@gmx.de> References: <87ftzq8jze.fsf@gmx.de> <8336vqqikk.fsf@gnu.org> <87h8k6upoa.fsf@gmx.de> <83wot2p2eu.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1533659965 32111 195.159.176.226 (7 Aug 2018 16:39:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 7 Aug 2018 16:39:25 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 07 18:39: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 1fn50x-0008Es-4k for ged-emacs-devel@m.gmane.org; Tue, 07 Aug 2018 18:39:19 +0200 Original-Received: from localhost ([::1]:40051 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fn532-0003FR-7q for ged-emacs-devel@m.gmane.org; Tue, 07 Aug 2018 12:41:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59776) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fn52v-0003D2-Rx for emacs-devel@gnu.org; Tue, 07 Aug 2018 12:41:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fn52r-0004BN-NP for emacs-devel@gnu.org; Tue, 07 Aug 2018 12:41:21 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:39971) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fn52r-00049k-Br; Tue, 07 Aug 2018 12:41:17 -0400 Original-Received: from detlef.gmx.de ([212.91.242.64]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LufbI-1fvhve48Bs-00zmJc; Tue, 07 Aug 2018 18:41:15 +0200 In-Reply-To: <83wot2p2eu.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Aug 2018 19:27:53 +0300") X-Provags-ID: V03:K1:6b9OLmLi/PomMXvaswqKUHUyr29gd3mVz4l4egDDjssBY7EF9qN cILwQvjTAwnTa8r/4vBvyPL/Q4qac6ko7a7vYHZgMvuiRwPTfcUsBhsNcD3U/L+c3csYkqY N6AsVBCgwTsGTgoXAQE15ms2B9510TfM6m4S3jZQ15psC7l9u5gYcPEIceQWuOY2dP27xtX Uw7rDrPaaEtZ6k471EiDg== X-UI-Out-Filterresults: notjunk:1;V01:K0:j+l7aj+pQPw=:d6wg0strzQcaMIRoL6nr/x NP7WvlV5H8KaKudpMthKlCrVUdY3SNzXs2HvM7M03ohTYI1EhY60GQ1zr1uAh5qdnQkxcq1q7 GQW7OocFTgvPIij5gZKcgGGJw4dT3OlE2VbykwIWeQ2lJ/ZL1Lnt1WIhXQ01yL4m4wVNjG5c+ /a+XlU9Ny6YeZPebxMNPYu+TU2HaG3KiJ+xPHRh1RSGZCmUOQ16gQp5OOhIvGctMn3g/6LwYw C6RSLd8Q6IYIg5WHBDsx6TP6W5atuGD7a9iJEba0u+FvvhY82Ji4YZNEgAFvxFkZv4pfdk0D6 FLWt4/qEG7OmcYrct0IMlzEsJu87vGxN7y9a7JbHyO123se5J4iNsjWfg2EKDcx4dFaRoVM+g a8NUT0OrBcj3deFsERpn992QqIWU6wGR5kKXU4nSEO6Z6m58XG3CQ74M05LIYVxPLxAaXnf9A QiiVAnlQcOmhqXMrmZswCTlbpmfK7v7uBUdoBUU40KEmKfry4NxsXth4dfpWDagSsPqrk5SQJ ZmD3nAQgQQDYJY/DKyKOl7lLA6Uru21mlIu215RBV35NgEExg6KN7RrE4J94bc21HnxkZ5mDw iarLYm73cmuXLGzXNYPqQWMQxrPQBBbJfp8inAYRLt4uJpquTjvXTeub9uMj5RTQNd50gzNyU W7ECIdOmq0/z6sY5W0uyfA9Lpp6pCMdroTlNJQ9+riNfmib7LQCK4TwHyqvMiT6rYGMF5RlL5 I13FEH76KKyZ6yzn5KvNUptrCqbgRHy7oMmUn2LQl6sDuYPCtF0rUKc9ALPb8jwSqsRJ1V6t X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 212.227.17.20 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:228291 Archived-At: Eli Zaretskii writes: >> It is about threads just now. But it could be also for other >> asynchronous command behavior, later on. > Do we really envision any other kind of asynchronicity in Emacs, any > time soon? I'd be surprised. Don't know. But, for example, any make-network-process based command could also feel the challenge to use the "asynchronous" knob, w/o a thread implementation. I've took this general interpretation from your meessage <838t5mt9wb.fsf@gnu.org>, where you have said --8<---------------cut here---------------start------------->8--- I was actually thinking about something like universal-async-argument, entirely unrelated to files etc. --8<---------------cut here---------------end--------------->8--- You haven't restricted this command to files, so I took it as general as possible. >> It is just a knob ("prefix command"), which tells the following command >> "If you know something about asynchronity, and if you care, be informed >> that the user wants you to run asynchronous". > > universal-coding-system-argument is also "just a knob", and yet it is > described where coding-systems are. Indeed, I was thinking of describing (or at least mentioning) that knob as well in the new "prefix command" section. > But feel free to find a different place, mine is just one opinion, and > not a very strong one in this case. I'm trying. But the essence of this thread is to find a good place; I didn't succeed so far. Best regards, Michael.