From: Chris Gorman <chrisjohgorman@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] use of plumber for new rule
Date: Thu, 20 Oct 2022 13:52:38 -0400 [thread overview]
Message-ID: <CAHVeOW9jknoVrzxKsQTPWJr1CSArwjuukKMt-h9W5=tg6vQXeQ@mail.gmail.com> (raw)
In-Reply-To: <7C4D0FA1A17C3D1DE4AE0B00B16A958E@prosimetrum.com>
Hello again Umbraticus,
Thanks for your email.
On Thu, Oct 20, 2022 at 1:01 PM <umbraticus@prosimetrum.com> wrote:
>
> I think you probably want:
>
> plumb start rc -c 'kertex/divps '$wdir'/'$0' | page -w'
This solution has acme load up the dvi file to edit. I want to
display the image rendered by page, but after it has been passed
through dvips. So either
plumb start window kertex/dvips $wdir/$0 '|' page
or
plumb start window kertex/dvips $wdir/$0 '|' page -w
or
plumb start window kertex/dvips $wdir/$0 '|' plumb -id image
have this work for me. The first one opens a small window, rather
than the full page that is loaded once I have converted the file to a
postscript file. This can be adjusted to the full window rendering
with the use of page -w, but I can see the initial window that dvips
loaded in the background. The plumb -id image solution loads up the
initial window, runs dvips and then resizes the window with the output
from the repiping. Not too sure which solution is the ideal one, but
it's currently working with the pipe to plumb -id. I'm probably not
explaining myself well enough. I ideally want the result from
running.
kertex/dvips <filename.dvi> | page -w
which I think I should get running 'plumb start rc -c 'kertex/dvips
'$wdir'/'$0' | page -w', but for some reason it doesn't work. :(
Best,
Chris
>
> umbraticus
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tce7385fe52c532d6-Mcd186ac9d272297cc3db913f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-10-20 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 13:24 Chris Gorman
2022-10-20 8:56 ` umbraticus
2022-10-20 13:18 ` Chris Gorman
2022-10-20 16:52 ` Chris Gorman
2022-10-20 17:00 ` umbraticus
2022-10-20 17:52 ` Chris Gorman [this message]
2022-10-21 1:10 ` Chris Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHVeOW9jknoVrzxKsQTPWJr1CSArwjuukKMt-h9W5=tg6vQXeQ@mail.gmail.com' \
--to=chrisjohgorman@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).