From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-it0-f45.google.com ([209.85.214.45]) by ur; Fri Jan 19 12:14:37 EST 2018 Received: by mail-it0-f45.google.com with SMTP id c16so2907620itc.5 for <9front@9front.org>; Fri, 19 Jan 2018 09:14:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sphericalharmony-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:to:subject:in-reply-to:mime-version :content-transfer-encoding; bh=3Jr1ogmzN4bUYu4uojD6UTzGM3+jvLtVvgWtjTOcDQ8=; b=DMwSxRwgk+EpKF+xcGaEVFFbyma9EoJUfL8WHJMEqJqaIbE0vzyG4k3cR4JfQEZXiJ Tyb8QELjsreSoHRPJXsITrfhQYXICTAHLXBNdUddyzF95tMkzwqgmQ9zo69SNaRqY3LF xTQJXsChdMC4lDlYMk5qcvkFRhMP0dl0imAoCc+CFhpco6IktzlAiI85sgpMzGr8ZHdN Cc5/+nynjP/x4sqTsPldFkxJhXndnIE6il79r0t0jFwzOCJB0bdBTNqKEwGF1Qu0niWf m5Ffya56u5/FmeetD9VYNW1wqo/ch72mAtPlGs80BDfUg+ap2LPa8nG153RkOTw4954Y 14nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:to:subject:in-reply-to :mime-version:content-transfer-encoding; bh=3Jr1ogmzN4bUYu4uojD6UTzGM3+jvLtVvgWtjTOcDQ8=; b=eu/54IgXA1jThbpym/34XCLvdHLQglHAj8mCLsM3gLdDv0dQboOmaJAZMI4MqHxGF8 H1pQxWAYYC9ExTcagc72CnLL/+yQiSHiXYoxYphhm6OgrhM+XatEHuQ6axDhFZ+WVZG+ 1PNfU0Lv85bk8mX8nbrj+5tLQ10/1zRMo/qtEo5hkulKl7EAiDlkTq4VY/grtZEfj4dy pecuhd9+DapD/COoBjsNtZhYoEb+yuhFHvR2FjywcvEOTXvwfiZLYuJR2Qr2mimf14EL StBbWijeuYGSUQgRzUS4ooGxTXb2xf90SFxhAPWmPg3Q96SJX7k0RtiFRYHQhrt3arth Saww== X-Gm-Message-State: AKwxytfAYy9/VAMSdUinjLKtBtJ/H1sJTZIfI0AwVJG2aslJ6oUStpue XKkBLP+HNfyZ0KX6rt7OBMD4H2RN X-Google-Smtp-Source: ACJfBovOckGp+/RySxjkWmQoD4Vvpg83KHqMdRDMnZmAUAjznwWMakP4QX90aO6M2T28Jdjs50gtYw== X-Received: by 10.36.36.151 with SMTP id f145mr31830555ita.103.1516382073553; Fri, 19 Jan 2018 09:14:33 -0800 (PST) Return-Path: Received: from x240.Home (h184-61-51-222.mdsnwi.dedicated.static.tds.net. [184.61.51.222]) by smtp.gmail.com with ESMTPSA id v190sm1019174itb.3.2018.01.19.09.14.32 for <9front@9front.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 19 Jan 2018 09:14:32 -0800 (PST) From: mycroftiv@sphericalharmony.com X-Google-Original-From: glenda@sphericalharmony.com Message-ID: <73EA2668A02D59E2CE6E40DE756CA9EF@sphericalharmony.com> Date: Fri, 19 Jan 2018 17:14:26 +0000 To: 9front@9front.org Subject: Re: [9front] plumb rules for page In-Reply-To: DC51D4FD-4081-43FE-BA98-AA3146CE23DC@stanleylieber.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: progressive extension cache-based event-scale layer I'm convinced by sl's reasoning, consider the previous suggestion withdrawn. That raises the inverse issue - should we change the rule for images to also always open a new page, and not 'take over' an existing instace? As it is, plumbing an image file will 'take over' a running page showing a /sys/doc (or whatever) ps/pdf file. Perhaps that should be changed to match the ps/pdf behavior, rather than the initial change I suggested? The use case I have for the 'take over' behavior is sharing a single plumber between multiple systems, where only the message-passing function of plumber works, not launching new applications. This is not the common way plumber is used, so I don't think the defaults should be adjusted to favor it, I can always customize my own plumb rules for my own purposes. -mycroftiv