> On Dec 3, 2015, at 7:30 AM, Kurtis Rader <kra...@skepticism.us> wrote:
>
> On Thu, Dec 3, 2015 at 5:46 AM, Glenn Jackman <jack...@pythian.com
> <mailto:jack...@pythian.com>> wrote:
> I don't imagine that the history file is really meant for human consumption.
> Also, pretty easy to transform the timestamp, for example:
>
> awk '$1 == "when:" {sub(/[0-9]+/, strftime("%F %T", $2))}1'
> ~/.config/fish/fish_history
>
> Sure I could do that, but my question is why doesn't the builtin history
> command not at least have an option to show the timestamp? Similarly, it
> would be nice if there were another var that shadowed $history which
> contained the timestamp for each command.
>
> The reason is that I sometimes find myself wanting to know not just whether
> or not I ran a specific command but when I did so. For example, I report
> attacks against my web server when they come from cloud providers. It's
> useful to know not only if I already reported a given attack but how far back
> in time I did so.
Yep, you're right, it's just a UI question. We capture the time but nobody has
thought about the right way to present it.
We'd happy to have this feature if you want to do a patch or even just design
the UI for it! A good way to get started is to comment in
https://github.com/fish-shell/fish-shell/issues/677 as to what you would like
the UI to be.
Thanks,
_fish
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
