9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mathieu Lonjaret <mathieu.lonjaret@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acmetags
Date: Sun, 30 Nov 2014 18:39:49 +0100	[thread overview]
Message-ID: <CAHcDtnnV-dSu_GiM428B6HyjhMgQsFwmtOPSQ59AOenU7vJh5Q@mail.gmail.com> (raw)
In-Reply-To: <a7e5fd80fc09ee67da61394f5b9dc71d@lilly.quanstro.net>

On 30 November 2014 at 18:19, erik quanstrom <quanstro@quanstro.net> wrote:
> On Sun Nov 30 09:03:42 PST 2014, mathieu.lonjaret@gmail.com wrote:
>> Hi,
>>
>> I usually keep most of my build/run/test workflow as tags on my acme
>> "win" windows. But acme dumps do not save tags, and I sometimes don't
>> save them in a guide file (because I forget when I reboot, or I close
>> acme inadvertently, or in rare occasions because acme dies). So I've
>> finally written a little tool to cope with that, and it's here
>> https://github.com/mpl/acmetags in case anyone is interested. I'll
>> probably run it in a cron or something.
>>
>> As usual, kudos to the acme authors and to Russ for the acme pkg which
>> made this so easy to write.
>
> the 9atom version of acme does do this.

Ah yeah, forgot to precise it was for p9p, thanks.

> it's pretty easy code to copy,
> i just haven't done it yet.  the other thing missing from p9p acme that
> i notice is the ability to middle click on the column blue square and have
> the column resize in width, as frames already do in height.  (only in
> 9atom, not labs.)

Wow, yes. I often wish I could do something like that and I didn't
even know it existed in any of the acme "versions". You have my thanks
in advance if that makes it into p9p. :-)

> - erik
>



  reply	other threads:[~2014-11-30 17:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 17:06 Mathieu Lonjaret
2014-11-30 17:19 ` erik quanstrom
2014-11-30 17:39   ` Mathieu Lonjaret [this message]
2014-11-30 17:45     ` erik quanstrom
2014-12-03 13:22     ` yy
2014-12-01 10:01 ` Kostarev Ilya

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=CAHcDtnnV-dSu_GiM428B6HyjhMgQsFwmtOPSQ59AOenU7vJh5Q@mail.gmail.com \
    --to=mathieu.lonjaret@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).