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
tr
On 06 Jun 2000, Hal Snyder <[EMAIL PROTECTED]> wrote:
> FWIW, I'm still getting the LOCKNAME error reported recently, with
> tramp.el 1.388.
Sorry to have been quiet, I am hoping to soon have access to a machine
where I can debug this issue directly. Do you have enough knowledge of
Lisp to debu
"Daniel Pittman" <[EMAIL PROTECTED]> writes:
> On 06 Jun 2000, Hal Snyder <[EMAIL PROTECTED]> wrote:
>
> > Well, it is now possible to save files edited remotely. Is this asking
> > for trouble? :-0
>
> You should be just fine. I think that you will no longer get clash
> detection, but I doubt
Hal Snyder <[EMAIL PROTECTED]> writes:
> The following seemed like an innocuous enough workaround: in
> tramp-handle-write-region, comment out the three lines that check
> whether lockname is valid - it's not used for anything else in tramp,
> and a non-tramp error should be handled by write-regi