6.7.2.3p3 - A type specifier of the form enum identifier without an enumerator list shall only appear after the type it specifies is complete.

From what I understand out of this, enum identifier; syntax is only valid when used as type for a variable/field/etc. Using enum identifier; as a declaration makes it incomplete. cproc does catch when such an enum is used as a function argument type or a variable but not when used as return type or struct field. Both GCC and Clang error out when using it in either places.

Example (compiles fine on latest cproc):

/* Incomplete enum */
enum fruit;

struct wrapper {
	/* Does not raise compile error */
	enum fruit f;
};

void
make_fruit(struct wrapper w)
{
	// ...
}

enum fruit {
	FRUIT_APPLE,
	FRUIT_BANANA,
};

I think it would be unnecessary to depend on something like libnotify. What about having an option to specify a shell command that will be executed on time up?

$ minitimer -N 'notify-send minitimer "Time is up"'

It can be as simple as just passing that string to system function (which is what I've been doing) or use exec* function to also provide some information via environment variables.

Broke ground on this in https://git.sr.ht/~taiite/senpai/commit/70d519af I'll implement my-nick soon.

Fixed in https://git.sr.ht/~taiite/senpai/commit/6be7183

I don't think this needs to be implemented, you're mostly not mentioning half of your channel anyway to require this feature, otherwise you can append : manually

ignore, it doesn't

This is an issue of notification daemons that support markup, \o gets understood as "escape 'o'", and loses the backslash. A solution would be to double the backslash so nothing is lost.

Possible implementation:

on-highlight: |
  msg="$(printf "%s" "$MESSAGE" | sed 's#\\#\\\\#g')"
  notify-send "$BUFFER" "<$SENDER> $msg"

Should be fixed by this patch: https://lists.sr.ht/~taiite/public-inbox/patches/22959

Should be fixed by this patch

When sending a message with // which "escapes" a literal / in the beginning, double slash gets sent instead.

The code path affected: https://git.sr.ht/~taiite/senpai/tree/master/item/commands.go#L424 I'm not sure why this ends up as two slashes because the input is sliced before.