From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Newsgroups: gmane.emacs.help Subject: Re: try-this-for ? Date: Thu, 18 Jan 2018 14:16:40 +0100 Message-ID: <20180118131640.GD29536@tuxteam.de> References: <86lggw6vtn.fsf@zoho.com> <86d1277u37.fsf@zoho.com> <86r2qn5qby.fsf@zoho.com> <86vafz4922.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1516281340 28612 195.159.176.226 (18 Jan 2018 13:15:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 18 Jan 2018 13:15:40 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jan 18 14:15:35 2018 Return-path: Envelope-to: geh-help-gnu-emacs@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 1ecA2Q-0006gM-8W for geh-help-gnu-emacs@m.gmane.org; Thu, 18 Jan 2018 14:15:26 +0100 Original-Received: from localhost ([::1]:58758 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ecA4Q-00061V-AJ for geh-help-gnu-emacs@m.gmane.org; Thu, 18 Jan 2018 08:17:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ecA3i-00060a-RR for help-gnu-emacs@gnu.org; Thu, 18 Jan 2018 08:16:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ecA3d-000412-Q1 for help-gnu-emacs@gnu.org; Thu, 18 Jan 2018 08:16:46 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]:35409) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ecA3d-000406-Fl for help-gnu-emacs@gnu.org; Thu, 18 Jan 2018 08:16:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=20171004; h=From:In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID:Subject:To:Date; bh=uqnwSCUR0mK2O30+wtTj+83VE9aXUR54xYAWkLREWSI=; b=tZJw5fFu9SFdHu074HMZ4H2Z6UKNNM5K8zGwC40RwQWzv+MquHOPKIu3rqA3GzdUdBMi7xfoWaGGbjGp7wgevUaYY0zxMJogKnv/GUJB54rFGgESSCLE6f/AIUyW1S9xGFK52rAsRB2rJwKiMcbhn0PZ54x1R9GZB+ZR/g3PpIiAG7N1Cfj4BLUR8KgjJ9Ln1VdiUzKxXiTz+akaqdzOpdXzqT6AC6r4e6xPmSLgxx6aGXUfI4aM6w+rPeLAaj1LebLHFnyLr2B2nT5CsuaYYigDf/5cPACvlGWQmKcn04hMLZ55KRmDFl+dpGucZKeB/Lx+lf7IqMH5MkH/NPnvOg==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1ecA3c-0001WP-61 for help-gnu-emacs@gnu.org; Thu, 18 Jan 2018 14:16:40 +0100 In-Reply-To: <86vafz4922.fsf@zoho.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 5.199.139.25 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:115776 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jan 18, 2018 at 01:59:17PM +0100, Emanuel Berg wrote: > tomas wrote: > > >> True concurrency isn't possible even for > >> multicore architectures IIUC. > > > > To a certain extent yes: the processors/cores > > have to cooperate to access common resources > > (e.g. memory), but as long as they are > > operating e.g. from local cache they do run > > in parallel. > > Yes, but I meant with respect to Emacs, can one > have, for example > > (let*((value-one (compute it)) ; on CPU1 > (value-two (compute it)) )) ; on CPU2 > > execute in parallel? No, but see threads: they *can* execute on different CPUs (whether Emacs will give you control over that is another question; moreover it's a pretty new feature anyway). > > central event loop > > Is this the KERNEL? No, I was talkint about Emacs input queue. > > to "keep running", you have to explicitly [...] > The problem with yielding is it won't work to > interrupt something that has put Emacs into > a hanged state... That's true about most programs out there. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlpgnjgACgkQBcgs9XrR2ka8RgCdFeu2XIJvDaOMwyIGsUWD2Tn+ H50An3aXGw2SOr1o1mk6/uUbsUwwdEu7 =I0xt -----END PGP SIGNATURE-----