9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Acme questions
Date: Wed, 10 Sep 2008 21:22:50 +0100	[thread overview]
Message-ID: <df49a7370809101322w67f4208dm4f0d83a92cd03b62@mail.gmail.com> (raw)
In-Reply-To: <73888427-D829-45C0-B6B5-2E7E0D0DF505@mac.com>

On Wed, Sep 10, 2008 at 7:48 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> I think double-clicking on the box to the left of the column information
> line thingy should do it.

erm. you really could have tried this first.
it doesn't take much, you know.

for the record, i once had a go at implementing a "hide" command within acme,
but i never got it stable enough to make available. it would be nice if more of
the invariants in the acme code were documented.

what i was really aiming towards was a way to allow acme to take
up multiple rio windows - the idea would be to allow dragging of acme
windows (or columns) between the acme rio windows. that way i could
edit a load of related files in a single rio window but avoid cluttering things
up when i want to digress into another project for a while (but also avoid
the risk of simul-editing a file that you get when starting two acmes at the
same time).

it could also make the X command more useful than it currently is.
in sam, the X command is great because you can edit many
related files at the same time without necessarily cluttering
the screen with them, but in acme it's a bit of a pain to do a global
edit across (say) 100 source files. it's for this sort of thing i end
up firing up sam -d, but it's so easy to waste time with files that i'm
already editing, etc.

at the acme data structure level, i reckoned it shouldn't be too hard - there
are multiple Windows per Column, multiple Columns per Row, but there's
only one Row. if there were multiple rio windows, each would be represented by
a Row, but so far i've always got bogged down in the implementation details,
time restrictions and my own brain limitations...



  reply	other threads:[~2008-09-10 20:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 14:04 hugo rivera
2008-09-10 15:27 ` erik quanstrom
2008-09-10 15:49   ` hugo rivera
2008-09-10 18:48 ` Pietro Gagliardi
2008-09-10 20:22   ` roger peppe [this message]
2008-09-11  7:23   ` hugo rivera
2008-09-11 11:24     ` sqweek
2008-09-11 11:45       ` roger peppe
2008-09-11 12:52       ` hugo rivera
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12 19:10 [9fans] acme questions paurea
2002-06-12 17:45 ` Axel Belinfante
2002-06-12 17:53 ` Fariborz Tavakkolian
2001-01-05  3:15 Quinn Dunkan

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=df49a7370809101322w67f4208dm4f0d83a92cd03b62@mail.gmail.com \
    --to=rogpeppe@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).