From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: What is the most useful potential feature which Emacs lacks? Date: Tue, 02 Jun 2020 09:42:02 -0400 Message-ID: References: <87a71mm86d.fsf@red-bean.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="21119"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: excalamus@tutanota.com, van.ly+2020@sdf.org, Richard Stallman , emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 02 15:43:06 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jg7C5-0005NX-Cz for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Jun 2020 15:43:05 +0200 Original-Received: from localhost ([::1]:34630 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jg7C4-00079y-Fh for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Jun 2020 09:43:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60036) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jg7BB-0005wI-1h for emacs-devel@gnu.org; Tue, 02 Jun 2020 09:42:09 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:56017) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jg7B9-0006Ja-Jx; Tue, 02 Jun 2020 09:42:08 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 41F4F44128D; Tue, 2 Jun 2020 09:42:05 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id A059544120A; Tue, 2 Jun 2020 09:42:03 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1591105323; bh=56+o7jG8/Mn1RUG3N2dYImT66adiI+wJl6l/kRsfyUs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=jaDMlJdoAliez8OftBc7Ij6QlLB3XUCvjzR3tx/OE0bUQdxa0tTtAf2jG8sqg6ygL b1jxsN8D4uKiXU9KbSGrmTWgDlAfaC70tltXCwEc01JAcNiGjaPiE9o1NUJdAOjfPz wGpzrJ01UBwFbLGHdU4il06dRFnO/FPahSAwVapJccvGRqZSdAJRPBwasR29xklDdC 4oM37ZaYVTiyanP+2YI0hJ8NPibJHjgnE75DkTfmxvqFb9aSOLrt+A5a9JWxFpzoj1 Bi7X0ZpTLQgkcQMm69DcSE90b3ncQBCtV9F/wRVKWFlaOhenGucZUaVn6D4inUXH2Q A6iwERhAIy0og== Original-Received: from alfajor (76-10-137-254.dsl.teksavvy.com [76.10.137.254]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 5C952120AA3; Tue, 2 Jun 2020 09:42:03 -0400 (EDT) In-Reply-To: <87a71mm86d.fsf@red-bean.com> (Karl Fogel's message of "Mon, 01 Jun 2020 22:57:14 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/02 09:42:05 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:251755 Archived-At: > Having separate Emacs processes that communicate with each other is best, I think. It's the only option, as far as I'm concerned. Sharing an Emacs process with some other user simply doesn't work at all (as anyone who has tried it will know, I think). > As Yuri Khan pointed out, experienced users have customized their Emacsen in > distinctive ways, such that having to edit inside someone else's Emacs setup > would be annoying. Back when I tried it, those issues didn't even have time to show up. Instead we quickly bumped into issues with the "single keyboard mode", and other similar "modal" problems. Or the unexpected sharing of the kill-ring, ... It's just hopeless. > Furthermore, there are privacy concerns with sharing an Emacs process. Indeed, the first thing I did when someone tried `make-frame-on-display` to display their Emacs session on my display (back when we tried out this new feature), was `M-x shell`. Stefan