From: Mathieu Lonjaret <mathieu.lonjaret@gmail.com>
To: Russ Cox <rsc@swtch.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
plan9port-dev@googlegroups.com
Subject: Re: git and (p9p) acme
Date: Fri, 27 Apr 2012 00:20:49 +0200 [thread overview]
Message-ID: <CAHcDtnnVF+JD4w0jMjD_0y-x8ZNCcWb2HWWHa08-VjA-bhuAaA@mail.gmail.com> (raw)
In-Reply-To: <CADSkJJX_iAx-oQedV8DwYDMmwvfy_3WHToozSdrc3D_Amb4zZA@mail.gmail.com>
I've just retried on the machine where I had the problem and it now
just works. No need even for awd indeed.
I'll try and reproduce the behavior, but I just don't see what I may
have done different the previous times...
thanks,
Mathieu
On Thu, Apr 26, 2012 at 5:32 AM, Russ Cox <rsc@swtch.com> wrote:
> On Wed, Apr 25, 2012 at 5:35 PM, Mathieu Lonjaret
> <mathieu.lonjaret@gmail.com> wrote:
>> So, are you saying E just works out of the box for you as the $EDITOR
>> for git/hg?
>
> Yes. Note that E waits for the file to change by running
> ls -l on the file in a loop. If for some reason doing the Put
> does not change the ls -l output (date+size, primarily) then
> E will not exit. If you are having trouble I would suggest
> putting some echo statements in the script or just doing
> 'set -e' at the top so that it echoes each statement as it
> executes (including the all-important comparison).
>
> I cannot imagine why using awd would change the behavior
> of the E script.
>
> Russ
next prev parent reply other threads:[~2012-04-26 22:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 11:51 Mathieu Lonjaret
2012-04-19 12:10 ` [9fans] " dexen deVries
2012-04-19 12:16 ` Aram Hăvărneanu
2012-04-19 12:12 ` Aram Hăvărneanu
2012-04-20 16:04 ` sqweek
2012-04-20 17:07 ` Mathieu Lonjaret
2012-04-20 19:39 ` Mark van Atten
2012-04-20 20:48 ` Mathieu Lonjaret
2012-04-25 20:21 ` Russ Cox
2012-04-25 20:30 ` [9fans] " Lyndon Nerenberg
2012-04-25 20:36 ` Russ Cox
2012-04-25 20:46 ` Lyndon Nerenberg
2012-04-25 20:51 ` John Floren
2012-04-25 20:57 ` Lyndon Nerenberg
2012-04-25 20:58 ` Russ Cox
2012-04-25 21:01 ` Lyndon Nerenberg
2012-04-25 20:56 ` Russ Cox
2012-04-25 20:59 ` Lyndon Nerenberg
2012-04-25 21:02 ` Russ Cox
2012-04-25 21:04 ` Lyndon Nerenberg
2012-04-25 21:05 ` Lyndon Nerenberg
2012-04-25 21:06 ` Russ Cox
2012-04-25 21:35 ` Mathieu Lonjaret
2012-04-25 21:44 ` [9fans] " Aram Hăvărneanu
2012-04-25 21:49 ` Aram Hăvărneanu
2012-04-25 22:35 ` Mathieu Lonjaret
2012-04-26 3:32 ` Russ Cox
2012-04-26 8:05 ` [9fans] " Rob Pike
2012-04-26 22:20 ` Mathieu Lonjaret [this message]
2012-04-27 11:48 ` Ethan Burns
2012-04-27 11:52 ` Ethan Burns
2012-06-14 12:51 ` Mathieu Lonjaret
2012-04-26 8:43 ` [9fans] " dexen deVries
2012-04-27 16:15 ` Christian Neukirchen
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=CAHcDtnnVF+JD4w0jMjD_0y-x8ZNCcWb2HWWHa08-VjA-bhuAaA@mail.gmail.com \
--to=mathieu.lonjaret@gmail.com \
--cc=9fans@9fans.net \
--cc=plan9port-dev@googlegroups.com \
--cc=rsc@swtch.com \
/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).