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] easier refreshing of acme wins
Date: Fri,  3 Apr 2015 15:16:30 +0200	[thread overview]
Message-ID: <CAHcDtnkb5TkjG=c2tQRW4LqQd5EA_o1XX=rKyLESApExss5uhQ@mail.gmail.com> (raw)
In-Reply-To: <CACW8ZS_Nb9nFtXQVSyCEV6PcvVU+4QeyurWZ7qnSVMs1SdqKpQ@mail.gmail.com>

Yes, I had seen that thread, but I explained I don't want the same
thing as what you're asking for. I do not want to refresh them all in
one command. I want to selectively refresh some of them, but in an
easier fashion than having to type Get for each of them.


On 28 March 2015 at 08:19, Aram Santogidis <gnubuntux@gmail.com> wrote:
> Hi,
>
> I posted a similar question in the list few days back
> http://marc.info/?l=9fans&m=142721596630272&w=1
>
> and one solution that was suggested by Antons and works fine for me is the
> following.
>
> Edit X:^... [^+].*[^\/]$: e
>
> Cheers,
> Aram
>
> On Thu, Mar 26, 2015 at 11:05 PM, Bakul Shah <bakul@bitblocks.com> wrote:
>>
>>
>> On Thu, 26 Mar 2015 18:49:51 -0000 Paul Lalonde <paul.a.lalonde@gmail.com>
>> wrote:
>> > 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.
>>
>> Not sure what you mean. If you git {pull,checkout,merge,...},
>> files you have been editing (but not yet saved) may already
>> require merging. You may be better off using some client side
>> git hook that checks the state of acme edited files and tries
>> to do the right thing (not that I have ever used these hooks).
>>
>> > 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+'
>>
>> Nice!
>>
>



  reply	other threads:[~2015-04-03 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:02 Mathieu Lonjaret
2015-03-26 16:34 ` Bakul Shah
2015-03-26 18:49   ` Paul Lalonde
2015-03-26 22:05     ` Bakul Shah
2015-03-28  7:19       ` Aram Santogidis
2015-04-03 13:16         ` Mathieu Lonjaret [this message]
2015-04-03 16:24           ` Skip Tavakkolian
2015-04-08 15:24             ` Mathieu Lonjaret
2015-04-09  8:02 ` yy
2015-04-09 13:28   ` Mathieu Lonjaret
2015-04-15 15:44     ` Mathieu Lonjaret

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='CAHcDtnkb5TkjG=c2tQRW4LqQd5EA_o1XX=rKyLESApExss5uhQ@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).