CD directory => immediate addition on directory history

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Jun 7, 2008
121
0
#1
Hi

Did the act of

CD directory

=> immediate addition as part of directory history

get into v11 beta?

I have been looking around OPTIONS, configuration, Whats New to see if you enable this, somehow. So far, cant see it.

Thanks

Stephen Howe
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#2
> Did the act of
>
> CD directory
>
> => immediate addition as part of directory history
>
> get into v11 beta?
No -- it would have required a complete rewrite of the CD / CDD code, as
well as part of the parser. It's on the suggestion list for v12, but it's
much more difficult to implement than you suspect.

Rex Conn
JP Software
 
#3
On Fri, 02 Oct 2009 19:28:21 -0500, rconn <> wrote:

|---Quote---
|> Did the act of
|>
|> CD directory
|>
|> => immediate addition as part of directory history
|>
|> get into v11 beta?
|---End Quote---
|No -- it would have required a complete rewrite of the CD / CDD code, as
|well as part of the parser. It's on the suggestion list for v12, but it's
|much more difficult to implement than you suspect.

I'd like it too, but only because I often want to start a new TCC and go where I
was when I closed some earlier instance. Could you stuff the CWD into the
history when a non-pipe, non-transient instance terminated. [Sure, I could do
that in tcexit, and I could accomplish the OP's goal with one of the special
aliases.]
--
- Vince
 
#4
vefatica wrote:
| rconn wrote:
|| Steve Howe
||| Did the act of
|||
||| CD directory
|||
||| => immediate addition as part of directory history
|||
||| get into v11 beta?
||
|| No -- it would have required a complete rewrite of the CD / CDD
|| code, as well as part of the parser. It's on the suggestion list
|| for v12, but it's much more difficult to implement than you suspect.
|
| I'd like it too, but only because I often want to start a new TCC
| and go where I was when I closed some earlier instance. Could you
| stuff the CWD into the history when a non-pipe, non-transient
| instance terminated. [Sure, I could do that in tcexit, and I could
| accomplish the OP's goal with one of the special aliases.]

I just updated my POST_EXEC alias to include the command "dirhistory /a
%_cwd". It does exactly what Steve Howe (and I) always desired. Along the
way I discovered that the DIRHISTORY command option /T does not work in
either 11.0.21 or 10.0.76. I achieved the same result, but much slower,
piping to TAIL.

A function @DIRHISTORY (similar to @DIRSTACK) might be useful.

It would be useful to be able to examine the current attributes of the
HISTORY and DIRHISTORY tables (order, duplicates, etc.).

REX:
I am too lazy to search HELP. Please verify my understanding that PRE_INPUT,
PRE_EXEC and POST_EXEC are never executed for the right side of a pipe.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#5
vefatica wrote:
| rconn wrote:
|| Steve Howe
||| Did the act of
|||
||| CD directory
|||
||| => immediate addition as part of directory history
|||
||| get into v11 beta?
||
|| No -- it would have required a complete rewrite of the CD / CDD
|| code, as well as part of the parser. It's on the suggestion list
|| for v12, but it's much more difficult to implement than you suspect.
|
| I'd like it too, but only because I often want to start a new TCC
| and go where I was when I closed some earlier instance. Could you
| stuff the CWD into the history when a non-pipe, non-transient
| instance terminated. [Sure, I could do that in tcexit, and I could
| accomplish the OP's goal with one of the special aliases.]

I just updated my POST_EXEC alias to include the command "dirhistory /a
%_cwd". It does exactly what Steve Howe (and I) always desired. Along the
way I discovered that the DIRHISTORY command option /T does not work in
either 11.0.21 or 10.0.76. I achieved the same result, but much slower,
piping to TAIL.

A function @DIRHISTORY (similar to @DIRSTACK) might be useful.

It would be useful to be able to examine the current attributes of the
HISTORY and DIRHISTORY tables (order, duplicates, etc.).

REX:
I am too lazy to search HELP. Please verify my understanding that PRE_INPUT,
PRE_EXEC and POST_EXEC are never executed for the right side of a pipe.
--
Steve
DIRHISTORY /T has been fixed for build 23.

Features that "might be useful" get put at the bottom (the very, very bottom) of the suggestion list. If you actually have a use (and an example) for it, it'll get bumped up.

I have no idea what you want for the "current attributes" of the history lists. (IMO that is definitely a job either for a custom filter or a plugin..)

The PRE_INPUT, PRE_EXEC, and POST_EXEC behavior is documented in the help for ALIAS.
 
#6
On Sun, 04 Oct 2009 22:03:14 -0500, rconn <> wrote:

|I discovered that the DIRHISTORY command option /T does not work in
|either 11.0.21 or 10.0.76.

And it's not mentioned in the quick help (/?).

And in the CHM help, its entry should probably say "/Tn" in a couple places.
--
- Vince
 
#7
rconn wrote:
| S. Fabian:
|| A function @DIRHISTORY (similar to @DIRSTACK) might be useful.
||
|| It would be useful to be able to examine the current attributes of
|| the HISTORY and DIRHISTORY tables (order, duplicates, etc.).

| Features that "might be useful" get put at the bottom (the very,
| very bottom) of the suggestion list. If you actually have a use
| (and an example) for it, it'll get bumped up.
|
| I have no idea what you want for the "current attributes" of the
| history lists. (IMO that is definitely a job either for a custom
| filter or a plugin..)

Dynamic information: current size, free space, entry count; the choices
made in the OPTION dialog: in the "Command History" section of the Command
Line page for (command) HISTORY, and their equivalents for DIRHISTORY.
Since HELP no longer includes the names of the directives set by OPTION,
users without access to the V8 help file cannot programmatically obtain
these settings. Using the OPTION dialog is not possible in batch files
imported from other users.

|| I am too lazy to search HELP. Please verify my understanding that
PRE_INPUT,
}} PRE_EXEC and POST_EXEC are never executed for the right side of a pipe.
|
| The PRE_INPUT, PRE_EXEC, and POST_EXEC behavior is documented in the
| help for ALIAS.

What may be implied but not explicitly stated in alias.htm is that
PRE_EXEC is performed before any pipes required by the new command line are
opened, and POST_EXEC is performed after such pipes, if any, have already
been closed. Obviously, at least now after I reread that section, PRE_INPUT
would need to be an oracle to know about pipes in a command not yet entered.
Nest year? Next century?
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#9
> | I have no idea what you want for the "current attributes" of the
> | history lists. (IMO that is definitely a job either for a custom
> | filter or a plugin..)
>
> Dynamic information: current size, free space, entry count; the
> choices made in the OPTION dialog: in the "Command History" section
> of the Command Line page for (command) HISTORY, and their equivalents
> for DIRHISTORY.
Why would any of that be of use?

Nobody's ever asked for any of those, so at best it seems to be of very
limited interest. A plugin could do it, if any plugin author wants to try.

Rex Conn
JP Software
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#10
How about this?

function DIRHISTORY=`%@EXECSTR[%1,dirhistory]`

echo %@DIRHISTORY[0]

-Scott

Steve F$BaC(Bi$BaO(B <> wrote on 10/03/2009 07:14:16 AM:


> vefatica wrote:
> | rconn wrote:
> || Steve Howe
> ||| Did the act of
> |||
> ||| CD directory
> |||
> ||| => immediate addition as part of directory history
> |||
> ||| get into v11 beta?
> ||
> || No -- it would have required a complete rewrite of the CD / CDD
> || code, as well as part of the parser. It's on the suggestion list
> || for v12, but it's much more difficult to implement than you suspect.
> |
> | I'd like it too, but only because I often want to start a new TCC
> | and go where I was when I closed some earlier instance. Could you
> | stuff the CWD into the history when a non-pipe, non-transient
> | instance terminated. [Sure, I could do that in tcexit, and I could
> | accomplish the OP's goal with one of the special aliases.]
>
> I just updated my POST_EXEC alias to include the command "dirhistory /a
> %_cwd". It does exactly what Steve Howe (and I) always desired. Along
the

> way I discovered that the DIRHISTORY command option /T does not work in
> either 11.0.21 or 10.0.76. I achieved the same result, but much slower,
> piping to TAIL.
>
> A function @DIRHISTORY (similar to @DIRSTACK) might be useful.
>
> It would be useful to be able to examine the current attributes of the
> HISTORY and DIRHISTORY tables (order, duplicates, etc.).
>
> REX:
> I am too lazy to search HELP. Please verify my understanding that
PRE_INPUT,

> PRE_EXEC and POST_EXEC are never executed for the right side of a pipe.
> --
> Steve
>
>
>
>