From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: taylanbayirli@gmail.com (Taylan Ulrich =?utf-8?Q?Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer?=) Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Add file-dwim. Date: Mon, 19 Oct 2015 10:39:15 +0200 Message-ID: <874mhnp80c.fsf@T420.taylan> References: <87d1wcrzuu.fsf@T420.taylan> <87lhb0ot7m.fsf@T420.taylan> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1445244111 20385 80.91.229.3 (19 Oct 2015 08:41:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 19 Oct 2015 08:41:51 +0000 (UTC) Cc: emacs-devel To: Artur Malabarba Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 19 10:41:51 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zo60s-0005An-Ko for ged-emacs-devel@m.gmane.org; Mon, 19 Oct 2015 10:41:50 +0200 Original-Received: from localhost ([::1]:37400 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zo60r-0005db-Qs for ged-emacs-devel@m.gmane.org; Mon, 19 Oct 2015 04:41:49 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48567) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zo5yR-00028J-84 for emacs-devel@gnu.org; Mon, 19 Oct 2015 04:39:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zo5yQ-00051z-9f for emacs-devel@gnu.org; Mon, 19 Oct 2015 04:39:19 -0400 Original-Received: from mail-wi0-x236.google.com ([2a00:1450:400c:c05::236]:36519) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zo5yQ-00051t-3M for emacs-devel@gnu.org; Mon, 19 Oct 2015 04:39:18 -0400 Original-Received: by wicfx6 with SMTP id fx6so39375166wic.1 for ; Mon, 19 Oct 2015 01:39:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=nOVrqsU7BTjXNCxmSFhBdyUgF7PKJOvZl4iPhm5RHuM=; b=uyWdxmURaMz1qSKE9t/8GfiTg/X2h6jpLSnBzXqlSyBOXGMidHbPcCp/BscjjfLt4+ JcXWy9D/lQv8lVukb+ylOCG0tdGF9O+3S7eGnq5nvXTPGLchnm2hOkZHvgV6m1kVWyT/ T8yF6H7868yp8BQtTRvXY5bINOcD3FsJ4TEUW0baGiOzLXCTA7QRKDgbrQiSjKgqLEOS eo9VAuYsBfuMnm/hYrdplA2gN+4Jqpnn/1BE4dAMb9CdrUUgG5h72V61wh88jbnK71to N3zah/DSiAPdbvhP2hXe7FwY5JDmG400dhtfEfCg/OzSrB7sHatnpI59TyXU0ELW9nGn 2bcg== X-Received: by 10.180.86.165 with SMTP id q5mr19962893wiz.27.1445243957608; Mon, 19 Oct 2015 01:39:17 -0700 (PDT) Original-Received: from T420.taylan ([2a02:908:c32:4740:221:ccff:fe66:68f0]) by smtp.gmail.com with ESMTPSA id jd7sm38736015wjb.19.2015.10.19.01.39.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Oct 2015 01:39:16 -0700 (PDT) In-Reply-To: (Artur Malabarba's message of "Sun, 18 Oct 2015 23:22:21 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::236 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:192050 Archived-At: Artur Malabarba writes: > 2015-10-18 20:46 GMT+01:00 Taylan Ulrich Bay=C4=B1rl=C4=B1/Kammer > : >> >> Hmm, while that's indeed *my* most common use-case, I'm not sure if it >> should be baked into the library. > > Well, it would be mine too, so that's 100% of our 2 subjects test sample.= :-) > And I know I've seen other people implement a sort of > `open-file-externally` command, so I'm sure it's a common need. So is this typically called synchronously or asynchronously? In my *real* config, I actually have exactly one synchronous command (queue audio file for music player), one asynchronous command (run tuxguitar), and one command that ends up being opened in an ansi-term buffer (run mplayer). I'm guessing that calling the process asynchronously, but ignoring its output (instead of creating a buffer for it like async-shell-command) would cover the most use-cases (it would cover the synchronous use-cases too). WDYT? Taylan