gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: arch on windows?


From: John Meinel
Subject: Re: [Gnu-arch-users] Re: arch on windows?
Date: Wed, 14 Jul 2004 14:21:44 -0500
User-agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bentley wrote:
| Ron Parker wrote:
|
|> It does lose semantic information when viewing a directory in
|> isolation.  (Think the vi or emacs directory viewers or shell prompts
|> with the last fragment of the current-working-directory displayed.)
|
|
| Vim displays the cwd in its directory navigation, so the benefits of
| repeating path components aren't great.

This has been confirmed, though it might not be true with old versions
of vim. As I don't believe I have any lying around to check. vi proper
doesn't let you navigate directories anyway.

|
| Many of us use the *entire* current-working-directory in our shell
| prompts, and this is the default on major Linux distributions.  Such
| paths are ugly and awkward in this context.

I do as well, and I have to say, a 250 character path that wraps 3 times
is rather ugly. For everything else, it is nicer than just the last dir,
though.

|
| They are also more difficult to navigate than necessary-- they
| more-or-less demand tab completion.
|
| Aaron

Agreed. I think navigation, etc, is actually simplified by not repeating
the components. Imagine you "test--branch" and "test--other", to
navigate with repeat it is:

t<tab> t<tab> b<tab> *
versus
t<tab> b<tab>

* the second 't' is optional, but you need the tab

It's small, but it happens every time. And if you didn't have
autocompletion, typing these paths becomes an exercise in pain.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA9YfIJdeBCYSNAAMRAsgsAJ9oS1Bwhzi1Ar48vowqO5KXTU3JsACfTNLO
z8JhV2mY6Idc8CXFFqevZTU=
=IKvH
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]