From:	Robert Neinast <neinast AT worldnet DOT att DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Installed gVim 6.1; filenames screwed up
Message-ID:	<MPG.1821afcbbe2e24619896de@netnews.worldnet.att.net>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1021024081706 DOT 26606H AT is>
X-Newsreader:	MicroPlanet Gravity v2.50
Lines:	64
Date:	Thu, 24 Oct 2002 12:23:45 GMT
NNTP-Posting-Host:	12.87.146.219
X-Complaints-To:	abuse AT worldnet DOT att DOT net
X-Trace:	bgtnsc04-news.ops.worldnet.att.net 1035462225 12.87.146.219 (Thu, 24 Oct 2002 12:23:45 GMT)
NNTP-Posting-Date:	Thu, 24 Oct 2002 12:23:45 GMT
Organization:	AT&T Worldnet
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <Pine DOT SUN DOT 3 DOT 91 DOT 1021024081706 DOT 26606H AT is>,
eliz AT is DOT elta DOT co DOT il says...
> 
> On Thu, 24 Oct 2002, Robert Neinast wrote:
> 
> > I just installed gVim 6.1 after having used gVim 5.7 for a long
> > time.
> > 
> > Before that, my bash window handled long file names just fine.
> > Now they are all screwed up (showing the 8-char versions).
> > I'm figuring gVim must have repointed some important file
> > or something.
> 
> Is it possible that the gVim installation sets LFN=n in the environment?
> That setting disables long file name support in DJGPP programs.

Nope.  LFN=y.

> If this doesn't help, please tell the details: what OS is that, what are 
> your AUTOEXEC.BAT and CONFIG.SYS, and what does "env" print in the Bash 
> window.

It's Windows 98.  From an "ls -l" autoexec.bat was last changed Oct 12,
and config.sys Mar 21.

To answer Sinan's questions:

  I downloaded from <http://vim.sourceforge.net/download.php#pc>.
  First I grabbed the self-installing executable, gvim61.exe, and
  ran it, thus installing gvim.  I next grabbed the 32 bit
  DOS executable, vim61d32.zip, and in a totally separate area,
  unzipped it.  Within the unzipped area was vim.exe, which I
  moved into the vim area, /vim/vim61.  I then added /vim/vim61
  to my /etc/profile PATH.

  At that point I noticed that my new bash window was screwed up.

============================================================

Hold the phone, in writing the above I figured out the problem.

Many thanks for sending me down the right path (actually PATH)
to find the problem.

Now, don't laugh . . .

It turns out that I also have an old MKS-unix installed on my
system.  In changing my /etc/profile PATH, I managed to put
/bin/ls ahead of /djgpp/bin/ls, and of course the old MKS knows
nothing about long file names.

Again, thanks for the help.

Let me also take this opportunity to thank all those involved
in creating/maintaining DJGPP.  As an old Unix guy (from the
early '80s) forced into the PC environment by retiring from
Lucent Technologies, it's a real life-saver for me.

Thanks to all,
Bob
-- 
. . . and shun the Frumious Bandersnatch
Robert A. Neinast
Pickerington, OH

- Raw text -