From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-it0-f46.google.com ([209.85.214.46]) by ur; Thu Jan 18 23:50:11 EST 2018 Received: by mail-it0-f46.google.com with SMTP id x42so745704ita.4 for <9front@9front.org>; Thu, 18 Jan 2018 20:50:08 -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:mime-version :content-transfer-encoding; bh=7QrAx/OZ6LHDh2ugWlOuheJNLPaURGI18uAY05S6mSo=; b=O0DNlbdeTjNAmEfkEdY+oQ3jtNDeZFxgSBrR2fg4fY5Bc2p07sguVsvBVX1keEn3j6 wl+yNxxB0vP1RutmvQ4K8ynFeN6Xp/EALPLfnRbCoADABblBFiLptIYFL1j7QOqYqWDh goPL5Y9Rdh9gpdzGtSoAVFat71MV1I2EgjehVmHCGafI7lCqvkh9h2wv4K0ez/fCKjPl KcgMqmuNO8A4VlY5D8Cm01REVC9lRXz8oz0LfFyWtqXqvxrvcB9eRFjgY07uEdsUGeZT XAgz8VIIkM/pYEHvrcvS5DV7VTyW9pieUky0umVTyywu64TINK//cjnmzlffhITSWBJF IViA== 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:mime-version :content-transfer-encoding; bh=7QrAx/OZ6LHDh2ugWlOuheJNLPaURGI18uAY05S6mSo=; b=q1QH2DH0t+I9Omzr49NSd25L51gXRj/HFILElqok+m3GCzz1GhC+LDsjBn+aj1o1oa gj0RxW5Zc36H5yKP04YI+SzcWZ9ci2WB3e6sr/RehStET10zVwGHCZXiW0gWGcs0r5/W Loeq9ayuyr1BAlKTqrVeax8XgEP/wb2h02Zk8e5mDSrsHwVHZkyR3jeF2PTOkTuADDpB 8DrZVekoWvLDHUjvjm9KUyQIdfVO/lduFiVH/ZUcMcXiiLiufMm8DNP/NyUGtXTdsWJg jnqmeamwXQzxBDLYGEJaNvy6mx3u0aQ9poh8fJrkWozIeEFLKwMR57Z9H3OTvJY7mZPZ UTuw== X-Gm-Message-State: AKwxytfZlWIseGh83DdZGUWrR0mC/4mBxmhdOskJsMIFBzr0MhBEavX1 wrP6XZXx1eHIIQCP6jx+uEOhIgVJ X-Google-Smtp-Source: ACJfBotwZCqkkI4K8JVzp7xhFyhN4UR555v95leBkXenk1C0bNzJYfMGJQnFO0A2/6DNauDcWMrslw== X-Received: by 10.36.76.68 with SMTP id a65mr28062217itb.57.1516337406908; Thu, 18 Jan 2018 20:50:06 -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 r186sm272775itb.13.2018.01.18.20.50.05 for <9front@9front.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 18 Jan 2018 20:50:06 -0800 (PST) From: mycroftiv@sphericalharmony.com X-Google-Original-From: glenda@sphericalharmony.com Message-ID: Date: Fri, 19 Jan 2018 04:50:03 +0000 To: 9front@9front.org Subject: plumb rules for page MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: flexible lossless injection strategy I was playing around with sharing plumber between different machines and found something I don't understand in the default 'basic' plumber ruleset as it relates to 'page'. Relevant excerpt from /sys/lib/plumb/basic follows: # image files go to page type is text data matches '[a-zA-Z¡-￿0-9_\-.,/]+' data matches '([a-zA-Z¡-￿0-9_\-.,/]+)\.(jpe?g|JPE?G|gif|GIF|tiff?|TIFF?|ppm|PPM|bit|BIT|png|PNG|pgm|PGM|bmp|BMP|yuv|YUV)' arg isfile $0 plumb to image plumb client page -wi # page bookmarks type is text data matches '(([a-zA-Z¡-￿0-9_\-.,/]+)\.(ps|PS|eps|EPS|pdf|PDF|dvi|DVI|doc|DOC|epub|EPUB|cb[tz]|CB[TZ]))!(.+)' arg isfile $1 data set $file attr add addr=$4 plumb to image plumb start page -wij $0 $file # postscript/pdf/dvi/doc go to page but not over the a plumb port # the port is here for reference but is unused type is text data matches '[a-zA-Z¡-￿0-9_\-.,/]+' data matches '([a-zA-Z¡-￿0-9_\-.,/]+)\.(ps|PS|eps|EPS|pdf|PDF|dvi|DVI|doc|DOC|epub|EPUB|cb[tz]|CB[TZ])' arg isfile $0 plumb to postscript plumb start page -w $file My question is, why do we send image files to a running page over the plumb port, but not ps/pdf type files? We send page bookmarks to running page via the plumb port, but not standard files. It is clear from the comments that this is a delibrate decision, is there a good reason for it? From my perspective, the "plumb to postscript" in the final ruleset shown here should be "plumb to image" to make all the behavior consistent. It's obviously a trivial point and easy to change if you want to, but if there isn't a justification for this divergence in behavior, perhaps we should just standardize it? -mycroftiv