From edsanj...@gmail.com on December 20, 2013 13:05:01

just read https://code.google.com/p/clink/issues/detail?id=119&can=1&q=history and unfortunately isnt possible :-(

From martin.r...@gmail.com on December 22, 2013 03:39:47

This request has come up quite a few times now so I do plan on implementing Bash's "history" command, probably fairly soon.

From edsanj...@gmail.com on January 07, 2014 07:42:31

Looking forward to it!
Thanks

From martin.r...@gmail.com on January 21, 2014 12:19:24

Status: Accepted
Owner: martin.r...@gmail.com

From martin.r...@gmail.com on February 04, 2014 16:45:11

Issue 182 has been merged into this issue.

👍

You will not have actual session avaliable until you exit, but here is my to cents:

doskey history=cat C:\Users\X53526FA\AppData\Local/clink/.history $*
doskey lhg=cat C:\Users\X53526FA\AppData\Local/clink/.history $B grep $*

lhg stands for ls history grep, and it's a handy alias

If you enable the history_io setting (available from v0.4.3) then the .history file will be written to every line entered. Native support for the history command is under way, albeit slowly.

That's a long time wanted feature. It's my default config on *nix systems.

Can you share some clues about your plans? Over all I miss !!$ and !!:x. I use it all the time with

> mkdir blablabla
> cd !!$

or

> super-complex-command
> echo !!:x > %userprofile%/bin/handy-script.cmd

Readline's history expansion works fine in Clink as per the manual at least.

As for plans, I'm working on detailed parsing of the entered line so Clink can condition it, expose it to Lua before it's returned to cmd.exe, etc. Part of that will be support for "history", and perhaps Bash-style backtick expansion.

Hello Martin. Last comment on this issue is almost a year old. Do you have an ETA for the implementation of the bash-like history command? Is it still on your radar?

I've given it some though, but not a lot to be honest. Clink's not got many new features simply because most of my time gets spent addressing issues. I do have a working parser for entered lines but haven't been able to get it to the point where it can be used to offer solid post-processing of a line before it's handed back to cmd.exe.

Bash's built-in 'history' command does quite a lot. Is there a common use-case that's particulary important? I wonder if this is it;

C:\>history | grep dir
  5  dir c:\foobar
 21  dir c:\windows
C:\>!21

Personally I think this is huge oversight. I just installed Clink with sole purpose to have a history and turns out I can't have it? Real disappointment for me

Create a bat file called history in windows folder.
Put the command in this answer:
https://superuser.com/questions/1019441/getting-the-list-of-command-history-using-clink

type "%LOCALAPPDATA%\clink\.history"

But by default clink writes history only on exit, to change it: clink set history_io 1 or modify history_io value in %LOCALAPPDATA%\clink\settings
Done.

@mridgers So you finally made it. Awesome

You can put the .bat file into the C:\Users\<USER> folder.