> Check out HISTCONTROL[1] and ignorespace in particular. Adding something
> along the lines to your ~/.kshrc should do the trick:
>
> HISTCONTROL=ignorespace
> bind -m '^L'='^U clear^J^Y' # note the intentional space before clear
>
> [1] https://man.openbsd.org/ksh#HISTCONTROL
Actually
Thanks all for not making me feel like I opened a flame war can of worms.
I think the ignore dups solution is probably the most sensible for my purposes
from what I have read from all the responses.
Thank you.
Ken
On July 31, 2018 9:09:05 AM GMT+02:00, Solene Rapenne wrote:
>Ken M wrote:
>> OK, so confession 1, I am a long time bash user
>> confession 2 all of my ksh experience is on solaris
>>
>> However in a when in Rome moment I am realizing how much I like ksh
>in openbsd,
>> but one minor thing.
Ken M wrote:
># I wish this worked
># bind -m '^L'=clear'^J';sed -i '$d' $HISTFILE
You need to make sure that the sed command is inside the argument of bind.
Something like this:
bind -m '^L=^Uclear;sed -i \$d "$HISTFILE"^J^Y'
The ^Y is just there to paste back the current line content when you
Ken M wrote:
> OK, so confession 1, I am a long time bash user
> confession 2 all of my ksh experience is on solaris
>
> However in a when in Rome moment I am realizing how much I like ksh in
> openbsd,
> but one minor thing. I don't like how much clear ends up in my history file.
> So
> I am
On Mon, Jul 30, 2018 at 08:11:44PM -0400, Ken M wrote:
> OK, so confession 1, I am a long time bash user
> confession 2 all of my ksh experience is on solaris
>
> However in a when in Rome moment I am realizing how much I like ksh in
> openbsd,
> but one minor thing. I don't like how much clear
6 matches
Mail list logo
