Two very basic questions about readline(3) and indent(1)

[Prevet]

Q1) I'm using rlwrap with ed(1) and want to add tabs while I'm editing. Since tab is used for completions I have altered my .inputrc file, so a tab character is inserted if ctrl-t is pressed, which is not the greatest. So I thought I'd ask if anyone here that uses readline with a CLI editor, can suggest a better alternative keypress, to get around the fact that the tab key is already taken.

Edit:
Forget that question. Maybe I can bind it to left or right alt or ctrl.

Q2) I want to try some C programming the OpenBSD way and have been reading the man for style(9). At the bottom it suggests a program called indent(1) which has a lot of options. So I was wondering if there is an OpenBSD specfic .indent.pro file uploaded somewhere with those settings. I searched and found one for Arch Linux, but could not find anything for OpenBSD. If there isn't an official one, perhaps you have seen one on Github?

[ibara]

Originally Posted by Prevet

Q1) I'm using rlwrap with ed(1) and want to add tabs while I'm editing. Since tab is used for completions I have altered my .inputrc file, so a tab character is inserted if ctrl-t is pressed, which is not the greatest. So I thought I'd ask if anyone here that uses readline with a CLI editor, can suggest a better alternative keypress, to get around the fact that the tab key is already taken.

Tab is ^I

[Prevet]

Thanks. So I could use "\C-i" as well as TAB.

I got it working a bit better. I made these changes to .inputrc to change the function TAB calls to tab-insert, only when ed is running.

# rlwrapped ed
$if rled
# complete with ctrl-t instead of tab
"\C-t": complete
# insert a tab character instead of complete
TAB: tab-insert
$endif

rlwrap is called with the flag
--command-name rled
So readline sees the above $if rled block.

[ip6ix]

According to style(9), the OpenBSD kernel source uses KNF (Kernel Normal Form) coding style, which is also referred to in the source for the indent(1) program in the OpenBSD base install. (See /usr/src/usr.bin/indent/README.)

So it's possible, likely even, that the default state for indent(1) is to reformat to KNF style without needing an ~/.indent.pro file at all.

I tested it on a couple of C source files I had lying around and the results look correct, but I'm not familiar enough with the KNF style to say for definite. Might be worth a shot though.

[Prevet]

Originally Posted by ip6ix

According to style(9), the OpenBSD kernel source uses KNF (Kernel Normal Form) coding style, which is also referred to in the source for the indent(1) program in the OpenBSD base install. (See /usr/src/usr.bin/indent/README.)

So it's possible, likely even, that the default state for indent(1) is to reformat to KNF style without needing an ~/.indent.pro file at all.

I tested it on a couple of C source files I had lying around and the results look correct, but I'm not familiar enough with the KNF style to say for definite. Might be worth a shot though.

I had a go at it and found almost all of the default settings were fine, except the spacing after variable declarations were double tabs, and the case statements weren't right on default.

So these are the settings I ended up changing:
-ci4
-cli0
-di1

You also have to tell it about your typedefs and structs using the -T flag:
-Tnameoftypedef1
-Tnameoftypedef2
...

Other than that, I couldn't see a flag for the way OpenBSD does spacing of variable declarations inside of structs, so that part has to be done by hand.