Hal Snyder [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] (Kai Großjohann) writes:
Could you try moving the `set +o vi' to the same spot where `set +o
history' is done? Just copy the code for `set +o history' and change
the command. If that worked, that would be great, because it would
"Daniel Pittman" [EMAIL PROTECTED] writes:
Hrm. Could you apply this patch, reproduce the issue, then send the
debug output to me?
Gnus seems to have eaten `this patch' :-/ I thought this only
happened with 5.8.6? Arf.
kai
--
I like BOTH kinds of music.
Daniel Pittman [EMAIL PROTECTED] writes:
Does the filename that you are writing contain a `~` character? I think
that the lockname needs to be `~`-expanded before the comparison. This
is on my todo list.
I have now tried to do this. Hal, does the new version work better?
kai
--
I like
[EMAIL PROTECTED] (Kai Großjohann) writes:
Hal Snyder [EMAIL PROTECTED] writes:
I use pdksh - which is btw the default shell with OpenBSD. If you run
it with command history enabled, either -o vi or -o emacs, it ignores
stty setting of -echo. After expanding the setup string to "set +o
On 04 Jun 2000, Hal Snyder [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Kai Großjohann) writes:
Hal Snyder [EMAIL PROTECTED] writes:
[...]
Still getting the LOCKNAME error on save, but I haven't read thru
emails yet to see if there's a suggested fix.
Kai checked a change into CVS not
On 04 Jun 2000, Hal Snyder [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Kai Großjohann) writes:
Daniel Pittman [EMAIL PROTECTED] writes:
Does the filename that you are writing contain a `~` character? I
think that the lockname needs to be `~`-expanded before the
comparison. This is on
[EMAIL PROTECTED] (Kai Großjohann) writes:
[EMAIL PROTECTED] (Kai Großjohann) writes:
Hal Snyder [EMAIL PROTECTED] writes:
--*tramp/scp hal@megalon*--
/bin/ls@-lnd / /dev/null 21 ; echo $?
0
Why does the shell echo the command? It shouldn't.
More info:
Follow-up to previous email about a LOCKNAME-related error on saving a
remote file
The filename entered after C-x C-f was "/r:substation:ping.pl".
Save command was C-x C-s
Stack trace on error was:
Signaling: (error "tramp-handle-write-region: LOCKNAME must be nil or equal FILENAME")
On 03 Jun 2000, Hal Snyder [EMAIL PROTECTED] wrote:
[...]
2. Now I can load a file from a remote host into a buffer, but when I
try to save it after editing, I get:
tramp-handle-write-region: LOCKNAME must be nil or equal FILENAME
This is with tramp updated from CVS a few minutes before
[EMAIL PROTECTED] (Kai Großjohann) writes:
Hal Snyder [EMAIL PROTECTED] writes:
--*tramp/scp hal@megalon*--
/bin/ls@-lnd / /dev/null 21 ; echo $?
0
Why does the shell echo the command? It shouldn't.
More info: tramp-open-connection-setup-interactive-shell sends `stty
-echo' to the
Hal Snyder [EMAIL PROTECTED] writes:
--*tramp/scp hal@megalon*--
/bin/ls@-lnd / /dev/null 21 ; echo $?
0
Why does the shell echo the command? It shouldn't.
Can you (setq tramp-debug-buffer t), repeat the error and mail me (or
the list) the contents of the *debug rcp/foo* buffer?
kai
--
I
OpenBSD is OS locally and on remote host.
tramp-check-ls-command seems to be looking at wrong place in the scp
buffer on its first use. All I have to do is "C-x C-f /r:megalon:foo"
and I get the error shown in the backtrace below. I can make the
bug go away by inserting
(forward-line 1)
just
12 matches
Mail list logo
