ksh HISTFILE

pfr

Just wondering how to set HISTFILE

in ~/.shrc or in ~/.profile

eg:

export HISTFILE=$HOME/.ksh_history
export HISTSIZE=5000
export SAVEHIST=5000

Is this correct?

I've tried adding those lines to both my my ~/.shrc and ~/.profile and I've created ~/.ksh_history but still no success

oui

pfr Hmm, It seems that I can't generate a history file as well.

If there isn't a specific reason to keep the command history in a file, I use and would recommend:
fc -lr 1 | less which gives a numbered output of your history with the size of env HISTSIZE.

oui

oui Hmm, It seems that I can't generate a history file as well.

(Correct me if I'm wrong) - Apparently it seems that the default NetBSD shell doesn't support writing history to a file.

However, I could generate a HISTFILE with ksh.

pfr Is this correct?

It's correct. You only need to export HISTFILE and HISTSIZE so you can remove the last line.

Double check if your current shell is ksh: echo $SHELL
If it's not, change your shell: usermod -s /bin/ksh username

Export HISTFILE and HISTSIZE in .shrc or create a separate .kshrc.

Source the changes: . ./.shrc

Ksh should now write the command history to HISTFILE upon exit.
Use the fc command as previously described for history in current session:

oui fc -lr 1 | less

Hope this helps.

Cheers 🍻

rvp

oui No issues here either:

$ sudo ls -lA ~bld
total 48
-rw-r--r--  1 bld  bld  1772 Jan 15 17:47 .cshrc
-rw-------  1 bld  bld   280 Jan 27 21:03 .ksh_history
-rw-r--r--  1 bld  bld   431 Jan 15 17:47 .login
-rw-r--r--  1 bld  bld   265 Jan 15 17:47 .logout
-rw-r--r--  1 bld  bld  1498 Jan 15 17:47 .profile
-rw-r--r--  1 bld  bld   257 Jan 27 04:23 .shrc
$ sudo egrep -v '^[[:blank:]]*(#|$)' ~bld/.profile
export EDITOR=vi
PATH=$HOME/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R7/bin:/usr/pkg/bin
PATH=${PATH}:/usr/pkg/sbin:/usr/games:/usr/local/bin:/usr/local/sbin
export PATH
export ENV=$HOME/.shrc
$ sudo egrep -v '^[[:blank:]]*(#|$)' ~bld/.shrc
if [ -f /etc/shrc ]; then
        . /etc/shrc
fi
case "$-" in *i*)
        export PS1='$PWD$ '
        export HISTFILE=$HOME/.ksh_history
        export HISTSIZE=100000
        ;;
esac
umask 022
$

pfr

What I'm trying to achieve here is this.

On my Linux machine my shell is zsh. I use the following alias to sort through my zsh history using fzf

This is really hand to have, however it doesn't work as expected in ksh and the HISTFILE doesn't seem to be formated the same way as it is in zsh

pfr

# pkgin install zsh fzf
# chsh -s /usr/pkg/bin/zsh dave

🤣

rvp

pfr What I'm trying to achieve here is this...

~~What's a sample history output look like in zsh?~~

EDIT: use fc -l 1 as history alone in ksh just prints the last 15 or so entries.
EDIT: add -n to the fc command to omit line numbers; still need to remove the initial blanks on some shells though.

Nevermind--I think this is what you want:

$ alias h='fc -l -n 1 | sed -Ee "s/^[[:blank:]]+//" | ... | tr -d "\n" | ...'

Best not to use absolute positions with cut -c.

pfr

pin
Well yeah, that's an option. But that would be the easy option. I'd like to keep ksh and just learn how it works a little more.

pfr I just couldn't resist, sorry.
While at it, you might want to check-out navi, which I've packaged a few weeks ago.

pfr

rvp Nevermind--I think this is what you want:
$ alias h='history | awk "{ sub(/^ *[0-9]+ +/, \"\"); print }" | sort | uniq | ...'
Best not to use absolute positions with cut -c.

This doesn't cut the line numbers though.

rvp

pfr This doesn't cut the line numbers though.

Of course it doesn't: I only checked it against bash assuming ksh printed its history list the same way. Corrected--should work now for both bash and ksh (and no matter where them wretched blanks are present).

pfr

rvp
That works. Except, because there are double and single quotes in the command, the only thing that doesn't work is cutting the new line with tr -d '\n'

alias h='history | awk "{ sub(/^[[:blank:]]*[0-9]+[[:blank:]]+/, \"\"); print }" | fzf | tr -d '\n' | xclip -selection c'

rvp

pfr Use: tr -d "\n" OR tr -d \\n
And, use fc -l 1 as @oui suggested. Plain history just prints the last 15 or so lines in ksh.

pfr

rvp both of those options work. Thanks!

JuvenalUrbino

rvp I like to see tr(1) as the sort of gem which reminds me why sed is evil.

JuvenalUrbino But sed is not evil, or it may be but, without sed a whole bunch of pkgsrc packages would be loaded with further patches.

rvp

JuvenalUrbino I like to see tr(1) as the sort of gem which reminds me why sed is evil.

sedevil? Nah... Write-only?--Oh yes!

tr is great because it works with binary files, but, I'm curious to know why you think sed is evil.

pin without sed a whole bunch of pkgsrc packages would be loaded with further patches.

Some seds (FreeBSD's, Linux's) can be used on binary files too: before @Jay pointed out in a post that NetBSD had a pkg_alternatives system just like Debian, I used to use sed -i to "fix" the shebang path in binary compressed python files:

$ sed -i '' -e '1s/env python$/&3.7/' ~/bin/youtube-dl

NetBSD's seddoesn't work with binariy files, so I use ed instead:

$ ed ~/bin/youtube-dl <<<$'1s/python$/&3.7/\nw\nq\n'

PS. The one thing I find irritating about sed is the lack of consistency in the handling of the -i flag everywhere. On FreeBSD, one uses sed -i '' ... to omit backup file(s). On NetBSD and Linux, it is sed -i'' ...--ie. without the intervening space.

JuvenalUrbino

Was ironic by the way, but enjoyed your replies nevertheless;

rvp PS. The one thing I find irritating about sed is the lack of consistency in the handling of the -i flag everywhere. On FreeBSD, one uses sed -i '' ... to omit backup file(s). On NetBSD and Linux, it is sed -i'' ...--ie. without the intervening space.

as for this, I can relate to it pretty much. The other day a friend of mine who's into economics was having a hard time while trying to perform some substitutions all over a .tex file, and was googling for utilities capable of automatizing the task; I volunteered to do the job and asked him to lend me his Macbook; forgetting macOS incorporates FreeBSD userspace utilities, I immediately threw a sed -i on the command line without result, since the command has got no in-place editing, and you need to redirect output to a file. GNU sed also uses '-r' for extended regexp as opposed to -E

rvp I know you were refering to binaries in your post but, I would like to make clear that, when working with source code, the correct way to handle such cases is not to use sed directly.

Inside Makefiles these things should be handled using REPLACE_PYTHON, REPLACE_BASH, ... and so on.

rvp

pin Inside Makefiles these things should be handled using REPLACE_PYTHON, REPLACE_BASH, ... and so on.

And, this, presumably, is why the script check stuff in pkgsrc exists...