From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <95A35504-71C5-4D0E-ABEB-5B545B689F35@bitblocks.com> In-Reply-To: <95A35504-71C5-4D0E-ABEB-5B545B689F35@bitblocks.com> From: Paul Lalonde Date: Thu, 26 Mar 2015 18:49:51 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a1147a89c2797330512357bb4 Subject: Re: [9fans] easier refreshing of acme wins Topicbox-Message-UUID: 4b08f0fc-ead9-11e9-9d60-3106f5b1d025 --001a1147a89c2797330512357bb4 Content-Type: text/plain; charset=UTF-8 The feature direction I'd like when working with Git is for the window of a git-changed file to become un-editable. This would require adding the idea of a un-editable window, which is probably a bad idea. Meanwhile I use the script below to generate X commands to reload changed windows. If I had a little more gumption (and less fear) I'd pipe the last output to make acme execute the Edits. #!/bin/bash cd `git rev-parse --git-dir`/.. git diff --name-only HEAD~ | sed s+^+`pwd`/+ | sort > /tmp/foobar 9p read acme/index | awk '{print $6}' | sort | comm -12 - /tmp/foobar | sed 's+\(.*\)+Edit X=\1=,r+' On Thu, Mar 26, 2015 at 9:36 AM Bakul Shah wrote: > What if you watch all tag lines and when a git controlled file is opened > in a window, you the watch file for changes and when it changes put > something in a new window that you can just select and middle click? > > > On Mar 26, 2015, at 9:02 AM, Mathieu Lonjaret < > mathieu.lonjaret@gmail.com> wrote: > > > > Hi, > > > > I work with many git branches, often affecting the same files. And I > > also happen to jump from one to the other quite frequently. There > > could be a problem with my workflow, but let's pretend there isn't. > > > > When one of said files is already open in acme, the win won't > > automatically refresh it and that's ok, I certainly wouldn't want that > > anyway, because I don't always to refresh them all. > > > > However, I find it a bit tedious that I have to write (or paste) > > myself the Get tag for each of the wins I want to refresh. To the > > point that I'm thinking of hardcoding the Get tag as one of the > > "permanent" tags for a win. > > > > Before I do that, does anyone have a better solution to suggest? The > > best would be that the Get tag gets automatically added to the tag bar > > whenever the files are changed (by git checkout, or other). > > > > p9p acme btw. > > > > Thanks, > > Mathieu > > > > --001a1147a89c2797330512357bb4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The feature direction I'd like when working with Git i= s for the window of a git-changed file to become un-editable.=C2=A0 This wo= uld require adding the idea of a un-editable window, which is probably a ba= d idea.

Meanwhile I use the script below to generate X c= ommands to reload changed windows.=C2=A0 If I had a little more gumption (a= nd less fear) I'd pipe the last output to make acme execute the Edits.<= /div>

#!/bin/bash
cd `git rev-parse = --git-dir`/..
git diff --name-only HEAD~ | sed s+^+`pwd`/+ | sort= > /tmp/foobar
9p read acme/index | awk '{print $6}' |= sort | comm -12 - /tmp/foobar =C2=A0| sed 's+\(.*\)+Edit X=3D\1=3D,r+&= #39;=C2=A0


On Thu,= Mar 26, 2015 at 9:36 AM Bakul Shah <bakul@bitblocks.com> wrote:
What if you watch all tag lines and when a git controlled f= ile is opened in a window, you the watch file for changes and when it chang= es put something in a new window that you can just select and middle click?=

> On Mar 26, 2015, at 9:02 AM, Mathieu Lonjaret <mathieu.lonjaret@gmail.com&= gt; wrote:
>
> Hi,
>
> I work with many git branches, often affecting the same files. And I > also happen to jump from one to the other quite frequently. There
> could be a problem with my workflow, but let's pretend there isn&#= 39;t.
>
> When one of said files is already open in acme, the win won't
> automatically refresh it and that's ok, I certainly wouldn't w= ant that
> anyway, because I don't always to refresh them all.
>
> However, I find it a bit tedious that I have to write (or paste)
> myself the Get tag for each of the wins I want to refresh. To the
> point that I'm thinking of hardcoding the Get tag as one of the > "permanent" tags for a win.
>
> Before I do that, does anyone have a better solution to suggest? The > best would be that the Get tag gets automatically added to the tag bar=
> whenever the files are changed (by git checkout, or other).
>
> p9p acme btw.
>
> Thanks,
> Mathieu
>

--001a1147a89c2797330512357bb4--