@fbfortune Great tip!

In #ksh / #ksh93, you can just type ‘r + Enter’ and it also immediately pulls up the last command and runs it. It’s an alias for ‘hist - s’ or ‘fc -s’

In #bash or #zsh, if ‘!! + Enter’ is only expanding the previous command but not executing, it’s because histverify is on. To turn it off, add this to your ~/.bashrc:

shopt -u histverify

——————

shopt = shell options command
-u = unset

#FreeBSD #OpenBSD #NetBSD #UNIX #Linux #Shell #Terminal #CLI #Commandline

Really!? A python3 venv deactivate caused a core dump of #ksh93 on #illumos? Repeatably?

And I really wanted not to fall down a rabbit hole tonight.

My muscle memory really wishes someone would get around to adding #helix mode to #ksh93.

#unix

Nice to start a day with two small contributions to free software:

https://reviews.freebsd.org/D19343?id=55482 fixing #ksh93 on #FreeBSD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229496#c8 let's get Python SOAP library zeep included in #FreeBSD

⚙ D19343 shells/ksh93: Update to 93v 2014-12-24

{ route get -inet6 default | grep -A1 gateway; } | while read line; do awk {'print $2'}; done

why does that only print one line?

just when I think I get #ksh93 I find out no, no I don't and it's all just (mostly wrong) educated guesses.

I have a sorted list of strings in one file (abbreviations).

I have a sorted list of csv, where the first position is the abbreviation of the full word in position two.

how do I loop through that (#ksh93 + #awk), outputting only the full word?

to be clear, there are multiple ("abv2 abv3 abv4") matching abbreviations + number in the first file.

this is trivial but my "foo" is so weak...

@rocx

The manual says:

> Note: The vi command-line editing mode is orphaned, yet still functional.

and this was subject to an SO investigation:

https://unix.stackexchange.com/questions/420388/arrow-keys-in-openbsds-ksh-command-line-editing-vi-mode

@calvin

#ksh93 #mksh
Arrow keys in OpenBSD's ksh, command line editing, Vi-mode

I'm using the default ksh on OpenBSD 6.2 (based on pdksh) with Vi command line editing mode enabled. I'm trying to get the arrow keys to work properly as a complement to h, l, j and k (as I'm on a

@rocx Ok, two immediate issues with #mksh (as opposed to #ksh93):

- it does not switch to vi mode if EDITOR/VISUAL is explicitly set to something that ends with "vi"

- in vi mode arrows do not work (they should work the same way as in emacs mode).

@calvin
Mister Jackpots (@[email protected])

10.3K Toots, 338 Following, 509 Followers · HelllloooOOOOOOOOOOOOOOOO United Empire Loyalist, computer person, learning to appreciate art & philosophy GitHub: NattyNarwhal XMPP: [email protected]

@rocx @calvin


# chsh -s /usr/local/bin/mksh saper
chsh: user information updated


we'll see

(but I was using #ksh93 a lot, so...)
Mister Jackpots (@[email protected])

10.3K Toots, 338 Following, 509 Followers · HelllloooOOOOOOOOOOOOOOOO United Empire Loyalist, computer person, learning to appreciate art & philosophy GitHub: NattyNarwhal XMPP: [email protected]