It happened again. and I've just realized it's simply what you had
warned about: since it was an --amend and I didn't change anything in
the message there was no change to the ls -l output, hence E did
nothing when I Put.
On Fri, Apr 27, 2012 at 12:20 AM, Mathieu Lonjaret
lyn...@orthanc.ca (Lyndon Nerenberg) writes:
On 2012-04-25, at 2:02 PM, Russ Cox wrote:
Are you sure you are running 'sam foo' and not 'sam foo '?
Sam 'blocks' until you quit out of it, just like acme or vi or ed.
It doesn't load the file for the user to edit.
It does, but it doesnt show
set -x
-rob
On Wednesday 25 of April 2012 23:35:59 Mathieu Lonjaret wrote:
So, are you saying E just works out of the box for you as the $EDITOR
for git/hg?
Or did you have to tweak a few things like what Aram and Dexen describe?
worked out-of-box; I only add plumbing for PHP stuff -- and start plumber in
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 r...@swtch.com
I guess it depends on what you expect to break.
I like using the E script because (once you learn not
to click Put, which doesn't take too long) after I click
Put the window is still there with my work in it in case
the tool I just sent it to chooses to blow up and
discard my efforts.
Russ
Indeed.
On Fri, Apr 20, 2012 at 9:39 PM, Mark van Atten
mark.vanat...@univ-paris1.fr wrote:
Mathieu Lonjaret mathieu.lonja...@gmail.com a écrit :
http://sqweek.net/plan9/acmeedit
Nice, it almost works out of the box.
I got a 9p error message when using it:
9p: write error: ill-formed
On 2012-04-25, at 1:21 PM, Russ Cox wrote:
I like using the E script because (once you learn not
to click Put, which doesn't take too long) after I click
Put the window is still there with my work in it in case
the tool I just sent it to chooses to blow up and
discard my efforts.
If 'sam
On Wed, Apr 25, 2012 at 4:30 PM, Lyndon Nerenberg lyn...@orthanc.ca wrote:
If 'sam file' did the obvious thing this would be much less of a problem.
What is not obvious about what 'sam file' does?
On 2012-04-25, at 1:36 PM, Russ Cox wrote:
What is not obvious about what 'sam file' does?
Plugging 'sam file' into a script does not launch the editor with the specified
file in a window for the user to edit, and then save out.
People are clamouring for a (visual) 'ed foo' replacement.
On Wed, Apr 25, 2012 at 1:46 PM, Lyndon Nerenberg lyn...@orthanc.ca wrote:
On 2012-04-25, at 1:36 PM, Russ Cox wrote:
What is not obvious about what 'sam file' does?
Plugging 'sam file' into a script does not launch the editor with the
specified file in a window for the user to edit, and
On Wed, Apr 25, 2012 at 4:46 PM, Lyndon Nerenberg lyn...@orthanc.ca wrote:
Plugging 'sam file' into a script does not launch the editor with the
specified file in a window for the user to edit, and then save
out.
Sure it does. And so does 'acme file', if you are on Plan 9 or
if you are on
On 2012-04-25, at 1:51 PM, John Floren wrote:
What behavior are you seeing?
A lack of expectation. I.e. I expect 'sam foo' to, well, edit 'foo'. 'acme
foo' does that, as does 'ed foo.' From a UI perspective, the 'sam foo'
behaviour is as non-intuitive as it gets.
If 'sam foo' (i.e. with
On 2012-04-25, at 1:56 PM, Russ Cox wrote:
The point of the E script is to let you edit in the editor you're
already using instead of opening a new one.
But none of those commands will block until the file is saved, and that's the
issue.
On Wed, Apr 25, 2012 at 4:57 PM, Lyndon Nerenberg lyn...@orthanc.ca wrote:
A lack of expectation. I.e. I expect 'sam foo' to, well, edit 'foo'. 'acme
foo' does that, as does 'ed foo.' From a UI perspective, the 'sam foo'
behaviour is as non-intuitive as it gets.
If 'sam foo' (i.e. with a
On 2012-04-25, at 1:58 PM, Russ Cox wrote:
Otherwise, I don't know what you're talking about.
Yes you do.
On Wed, Apr 25, 2012 at 4:59 PM, Lyndon Nerenberg lyn...@orthanc.ca wrote:
But none of those commands will block until the file is saved, and that's the
issue.
Are you sure you are running 'sam foo' and not 'sam foo '?
Sam 'blocks' until you quit out of it, just like acme or vi or ed.
Russ
On 2012-04-25, at 2:02 PM, Russ Cox wrote:
Are you sure you are running 'sam foo' and not 'sam foo '?
Sam 'blocks' until you quit out of it, just like acme or vi or ed.
It doesn't load the file for the user to edit. Given a single file on the
command line, the obvious behaviour should be to
On 2012-04-25, at 2:02 PM, Russ Cox wrote:
Are you sure you are running 'sam foo' and not 'sam foo '?
Sam 'blocks' until you quit out of it, just like acme or vi or ed.
And you're right -- blocking behaviour isn't the problem with sam.
It doesn't load the file for the user to edit.
You must be running a different sam than I am.
I would make a video and post it on YouTube
but I am too lazy.
Russ
So, are you saying E just works out of the box for you as the $EDITOR
for git/hg?
Or did you have to tweak a few things like what Aram and Dexen describe?
I wouldn't mind using E as it is, with Put being the trigger to the
tool (git in that case), but it does not seem to be working here.
On Wed,
So, are you saying E just works out of the box for you as the $EDITOR
for git/hg?
Or did you have to tweak a few things like what Aram and Dexen describe?
I guess all you need to run up awd in your cd alias. I think I stole
my cd function from Russ.
--
Aram Hăvărneanu
I guess all you need to run up awd in your cd alias. I think I stole
my cd function from Russ.
Actually, the way one does this is documented in label(1). Beware that
this requires X, hence the $DISPLAY check in my profile.
--
Aram Hăvărneanu
Indeed, it seems like awd was all that was needed.
Thanks!
On Wed, Apr 25, 2012 at 11:49 PM, Aram Hăvărneanu ara...@mgk.ro wrote:
I guess all you need to run up awd in your cd alias. I think I stole
my cd function from Russ.
Actually, the way one does this is documented in label(1). Beware
On Wed, Apr 25, 2012 at 5:35 PM, Mathieu Lonjaret
mathieu.lonja...@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
Thanks Dexen and Aram for the explanation.
On Fri, Apr 20, 2012 at 6:04 PM, sqweek sqw...@gmail.com wrote:
On 19 April 2012 19:51, Mathieu Lonjaret mathieu.lonja...@gmail.com wrote:
Is anyone using git with p9p acme set as the editor?
snip
I use E instead (which I thought was meant for that),
hi list,
On Thursday 19 of April 2012 13:51:40 Mathieu Lonjaret wrote:
Is anyone using git with p9p acme set as the editor?
i have the following in ~dexen/.profile
export VISUAL=E
if [ $DISPLAY ]; then
nohup plumber /dev/null /dev/null 2/dev/null
fi
plus a few custom rules in
Is anyone using git with p9p acme set as the editor?
Most things here work fine (as long as the pager is set to cat or
something like that), but I've been having problems with 'git commit
--amend'. If I use B as the $EDITOR, git considers the log file edited
as soon as it is opened in acme
dexen deVries wrote:
caveat:
using VISUAL=E with git, be wary of saving the file several times; the first
Put
will cause git to go ahead and subsequent changes to file will most likely be
ignored.
Great caveat, it bit me once.
--
Aram Hăvărneanu
29 matches
Mail list logo
