9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Two Acme questions
Date: Wed, 16 Jul 2014 13:28:36 -0400	[thread overview]
Message-ID: <943bb936a14ffe9e31f97450b2d34268@ladd.quanstro.net> (raw)
In-Reply-To: <CAGMcHPoR47jc3W8sg1GYJd4kBjgH4tvWJo0s4n3H-KpDt8WE3A@mail.gmail.com>

> First, after using plan9 and plan9port I've noticed that on plan9port
> (from Arch Linux's repository) the tagline seems to have the ability
> to wrap onto multiple lines. I quite like it because I end up with
> some (unfortunately unavoidable) long paths in them.
> Plan9's acme (I'm using 9atom) doesn't seem to do this and just gets
> cut off the end. Is there a way to let it wrap? I could not find any
> related comments in the manual.

you'd need to backport p9p acme to plan 9.

> Secondly, I'm trying to make a little "guide" script for acme so I can
> write "Guide" in the tagline and whenever I run it a +Errors window
> shows a quick jump-to list for the functions in the file.
> I've got a small awk script ready and working and generating output in
> the right format but I can't seem to get it to plug in to acme in
> plan9port.
> I've attempted to do "9p read /acme/$winid/body" but I keep getting
> "connect: /tmp/ns.riddler.:0/: Connection refused"
> I found a few references to this error in context with factotum but
> not any fixes. Any suggestions as to what I'm missing?

are you running plumber?

- erik



  reply	other threads:[~2014-07-16 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 17:04 Riddler
2014-07-16 17:28 ` erik quanstrom [this message]
2014-07-16 17:31   ` Lee Fallat
2014-07-16 17:56     ` sl
2014-07-16 19:14     ` Aram Hăvărneanu
2014-07-16 19:31       ` Lee Fallat
2014-07-17  9:39         ` Riddler
2014-07-23  5:22           ` Bence Fábián
2014-07-23  9:25             ` Riddler

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=943bb936a14ffe9e31f97450b2d34268@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).