9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] plan9port acme can't load dump file with shell output of "9p read plumb/rules"?
Date: Mon,  8 Jun 2009 17:59:26 -0500	[thread overview]
Message-ID: <d50d7d460906081559u3496f9d7m3df182d016b79425@mail.gmail.com> (raw)

plan9port acme calls it a "bad load file" when I try to load a dump
file in which a shell window contains the output of "9p read
plumb/rules".  Specifically, the error message refers to the line in
the dump file just before a "data matches" line containing one of the
complicated regular expressions with special characters ("i- ") in the
basic rules.

Are there certain characters which acme does not expect to see in the
load file, and fails when it does see them?  Or is there a similar
problem with what's okay to print when reconstructing an +Errors
window (this seems farther-fetched)?  The plumb/basic file itself
comes back fine, probably because its content doesn't go through the
dump-file parser.

I can work around it easily enough, by clearing any buffer in which
I've output the read command before I dump.  I also tried to manually
edit the dump file, which only works if I delete the "bad" +Errors
window's tag and all windows and tags after it.

If this is a known problem, or you would like a bug report, would
someone kindly direct me to (its record in) the appropriate
bug-tracking system?

Jason Catena



             reply	other threads:[~2009-06-08 22:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 22:59 Jason Catena [this message]
2009-06-08 23:52 ` Russ Cox
2009-06-09  3:19 Jason Catena
2009-06-09  4:46 ` Russ Cox
2009-06-09  5:18   ` Jason Catena
2009-06-09  5:34     ` Russ Cox

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=d50d7d460906081559u3496f9d7m3df182d016b79425@mail.gmail.com \
    --to=jason.catena@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).