[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: to - Bookmark file system locations in bash on POSIX-like systems
From: |
Mara Kim |
Subject: |
Fwd: to - Bookmark file system locations in bash on POSIX-like systems |
Date: |
Thu, 4 Apr 2013 04:35:27 -0500 |
---------- Forwarded message ----------
From: Mara Kim <hacker.root@gmail.com>
Date: Thu, Apr 4, 2013 at 4:34 AM
Subject: Re: to - Bookmark file system locations in bash on POSIX-like
systems
To: Pierre Gaston <pierre.gaston@gmail.com>
Hi Pierre,
I read it, but maybe I missed something. There didn't seem to be much info.
I'm not really a fan. It's a bit unintuitive, and it's less obvious what is
happening when you look at a command history. I seriously have not met a
single person IRL that knows about CDPATH. I have gotten the suggestion to
use CDPATH in 'to' before, but I'm not really sure there is a compelling
reason.
--
Mara
On Apr 4, 2013 4:18 AM, "Pierre Gaston" <pierre.gaston@gmail.com> wrote:
>
>
>
> On Thu, Apr 4, 2013 at 11:58 AM, Mara Kim <hacker.root@gmail.com> wrote:
>
>> Hi Chris!
>>
>> Actually, this is great! Style critique, plus runtime analysis. Am I
>> dreaming? :D
>>
>> I see your point regarding the use of variables to hold commands. Using
>> PATH is a much better method of handling that functionality. And with the
>> magic of vim and git *POOF* it's gone...
>>
>> What is do you mean specifically by function vs [? Do you mean parens?
>> Is
>> function a bash-ism?
>>
>> I am really only enthusiastic about the interface of 'to'. While 'jump'
>> has a faster running time, 'to' lets you move directly to subdirectories
>> of
>> your bookmark. For example, '$ to foo/bar' moves you to the bar directory
>> under the foo bookmark, with tab completion!
>>
>> Just to be sure: have you read the documentation of CDPATH in the manual?
> (ok it's not posix but then your script is bash only)
>
--
M
RE: to - Bookmark file system locations in bash on POSIX-like systems, dnade.ext, 2013/04/10