Re: [BUG] File name completion in v1.178

2000-02-25 Thread Kai Großjohann
Pete Forman [EMAIL PROTECTED] writes: My mistake. I had been confusing "login" and "interactive". A login shell will read .profile or similar prior to reading commands which is what was worrying me. An interactive, non-login shell generally will not read any file. It may read .bashrc,

Re: [BUG] File name completion in v1.178

2000-02-25 Thread Kai Großjohann
Daniel Pittman [EMAIL PROTECTED] writes: For me, adding the '-1' switch to the two ls(1) calls in the mentioned function fixed the problem and file name completion works again. I don't know if this is portable to any ls but the GNU one however and so have not supplied a patch. All the ls

Re: [BUG] File name completion in v1.178

2000-02-25 Thread Kai Großjohann
Pete Forman [EMAIL PROTECTED] writes: Kai Großjohann writes: Pete Forman [EMAIL PROTECTED] writes: Most versons of ls work for me, but I do have an older machine running ISC 4.0 (Interactive Unix) which does not handle -1. How much of a problem is it to parse the results of

[BUG] File name completion in v1.178

2000-02-25 Thread Daniel Pittman
I am using (stock): ;; Version: $Id: rcp.el,v 1.178 1999/10/24 17:06:42 kai Exp $ File name completion no longer seems to work. This seems to be caused by ls(1) at the far end (GNU ls from fileutils 3.16) returning several columns of names while 'rcp-handle-file-name-all-completions' expects to

Re: [BUG] File name completion in v1.178

2000-02-25 Thread Pete Forman
Kai Großjohann writes: Daniel Pittman [EMAIL PROTECTED] writes: For me, adding the '-1' switch to the two ls(1) calls in the mentioned function fixed the problem and file name completion works again. I don't know if this is portable to any ls but the GNU one however and so have