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] New internal command for acme proposal (with implementations)
Date: Wed,  5 Feb 2014 06:36:21 -0500	[thread overview]
Message-ID: <9031696b55153f1092b3e564463f31fd@mikro.quanstro.net> (raw)
In-Reply-To: <CAPavXpCd=ev6j9MwgwQM6NQWNKJwC8igLtjaFyafOUVbSbfDvg@mail.gmail.com>

> I believe Acme should not be extended such way. There already were a lot of
> proposals of commands to add in Acme.
> If all of them were added we would have Acme with a size like LibreOffice
> and a tag on half of screen.

the parent said:
> >	I can't implement cmd as external, so I did little changes in
> >	original

i don't believe anyone has proposed adding all of them, and it's not
necessary to put every command that could be in the tag, in the tag.
Edit, for exampl,e is omitted.

> So let's extend Acme not by internal commands but filesystem extentions,
> may be new files, may be new messages for "ctl" files.
> For example, for pointer it can be a message "pointer=addr" for "ctl" file.

in spirit i agree with this.  but a few more points.

i've experimented with a few similer modifications, and have found that
the fs interface isn't fiat—it reflects the structure of the code.  changes
to the fs interface tend to spill out.

once one thinks about major modifications, i think it becomes attractive
to think about a new editor.  i miss having graphics.

- erik



  reply	other threads:[~2014-02-05 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 10:44 Uvelichitel
2014-01-24 10:59 ` Uvelichitel
2014-01-24 11:15 ` dexen deVries
2014-02-05 10:49 ` Alexander Sychev
2014-02-05 11:36   ` erik quanstrom [this message]
2014-02-05 16:04     ` Bakul Shah
2014-02-05 16:10       ` erik quanstrom
2014-02-05 16:26         ` Bakul Shah
2014-02-05 16:39       ` dexen deVries
2014-02-05 17:04         ` Bakul Shah
2014-01-24 12:49 Uvelichitel
2014-01-24 17:32 ` Bence Fábián

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=9031696b55153f1092b3e564463f31fd@mikro.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).