LOCKNAME workaround

2000-06-05 Thread Hal Snyder
FWIW, I'm still getting the LOCKNAME error reported recently, with tramp.el 1.388. Note the backtraces previously sent indicate a bad lockfile name passed from the innards of XEmacs to the parameter list of tramp-handle-write-region. The following seemed like an innocuous enough workaround: in

Re: tramp ($Id: tramp.el,v 1.368 2000/05/31 22:24:21 grossjoh Exp $); tramp-check-ls-command error

2000-06-04 Thread Hal Snyder
[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 "s

Re: tramp ($Id: tramp.el,v 1.368 2000/05/31 22:24:21 grossjoh Exp $); tramp-check-ls-command error

2000-06-03 Thread Hal Snyder
[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: tramp-open

Re: tramp ($Id: tramp.el,v 1.368 2000/05/31 22:24:21 grossjoh Exp $); tramp-check-ls-command error

2000-06-03 Thread Hal Snyder
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")

tramp ($Id: tramp.el,v 1.368 2000/05/31 22:24:21 grossjoh Exp $); tramp-check-ls-command error

2000-05-31 Thread Hal Snyder
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