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: [9fans] easier refreshing of acme wins
Date: Thu, 26 Mar 2015 17:02:57 +0100	[thread overview]
Message-ID: <CAHcDtn=E9-G8B4=nm=yXDji17FVD82h8kjCqRnxBx-83C3oupw@mail.gmail.com> (raw)

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



             reply	other threads:[~2015-03-26 16:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:02 Mathieu Lonjaret [this message]
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
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='CAHcDtn=E9-G8B4=nm=yXDji17FVD82h8kjCqRnxBx-83C3oupw@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).